GNU bug report logs - #9134
don't force mystery on user trying to find out what is completing after the word "ssh" in *shell*

Previous Next

Full log

Message #11 received at 9134 <at> debbugs.gnu.org (full text, mbox):

From: Phil Sainty <psainty <at> orcon.net.nz>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 9134 <at> debbugs.gnu.org, monnier <at> iro.umontreal.ca, jidanni <at> jidanni.org
Subject: Re: 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

On 2019-10-14 14:48, Lars Ingebrigtsen wrote:
> jidanni <at> 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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.