From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
9134@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#9134: don't force mystery on user trying to find out what is completing after the word "ssh" in *shell*
Date: Mon, 14 Oct 2019 08:26:23 -0400 [thread overview]
Message-ID: <jwv36fvzfbu.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <d2941119-be4e-682c-275b-d9cd526f138d@orcon.net.nz> (Phil Sainty's message of "Mon, 14 Oct 2019 23:49:58 +1300")
> As a side note, has it always been the case that, when asking
> about a variable with a buffer-local value, if you follow links
> in that *Help* buffer to other variables which also have
> buffer-local values in the original buffer, you'll only see the
> global values (because you're now local to the *Help* buffer)?
Yes.
> I feel like it would be nice if the *Help* remained local to the
> same buffer for as long as you remained in the *Help* window.
I think I agree.
> What would perhaps be nice is for the *actual* sequence of events
> to be tracked internally, and reported on request, so that the
> user could ask "where did the completion(s) actually come from?"
> and be told the answer.
I don't think the "sequence of events" is really necessary, but maybe
just the "last bit" (i.e. pcmpl-ssh-hosts in your example), but yes,
reporting upon request after-the-fact could be good, tho it's probably
going to be hard to make it sufficiently discoverable.
Stefan
next prev parent reply other threads:[~2019-10-14 12:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 23:49 bug#9134: don't force mystery on user trying to find out what is completing after the word "ssh" in *shell* jidanni
2019-10-14 1:48 ` Lars Ingebrigtsen
2019-10-14 3:32 ` Phil Sainty
2019-10-14 4:46 ` Drew Adams
2019-10-14 10:49 ` Phil Sainty
2019-10-14 12:26 ` Stefan Monnier [this message]
2019-10-14 14:37 ` Drew Adams
2019-10-14 4:50 ` Lars Ingebrigtsen
2019-10-14 5:08 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv36fvzfbu.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=9134@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=larsi@gnus.org \
--cc=psainty@orcon.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.