From: Phil Sainty <psainty@orcon.net.nz>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: jidanni@jidanni.org, 9134@debbugs.gnu.org, monnier@iro.umontreal.ca
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 16:32:03 +1300 [thread overview]
Message-ID: <0449ae1f85bbc0076cbfde9b61996660@webmail.orcon.net.nz> (raw)
In-Reply-To: <874l0ct7vh.fsf@gnus.org>
On 2019-10-14 14:48, Lars Ingebrigtsen wrote:
> jidanni@jidanni.org writes:
>
>> When we hit TAB in *shell* after the word "ssh",
>>
>> * there are no messages about where in the world it is getting its
>> completions. Unlike dabbrev-expand.
>
> That is pretty mysterious behaviour; yes. Would flashing a message
> saying "Looking for host names in ~/.ssh/known_hosts and ~/.ssh/config"
> be helpful?
I think it would be nicer if the *Completions* buffer text explained it.
i.e. additional information added to this:
"Click on a completion to select it.
In this buffer, type RET to select the completion near point.
Possible completions are:"
That's mostly from `completion-setup-function'. Perhaps that could be
made to incorporate text from a new var, which could then be bound
dynamically in cases where extra context was desirable?
-Phil
next prev parent reply other threads:[~2019-10-14 3:32 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 [this message]
2019-10-14 4:46 ` Drew Adams
2019-10-14 10:49 ` Phil Sainty
2019-10-14 12:26 ` Stefan Monnier
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=0449ae1f85bbc0076cbfde9b61996660@webmail.orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=9134@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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.