From: Michael Albinus <michael.albinus@gmx.de>
To: Gregory Heytings <gregory@heytings.org>
Cc: 51386@debbugs.gnu.org, Manuel Uberti <manuel.uberti@inventati.org>
Subject: bug#51386: 29.0.50; fido-vertical-mode: ssh host completion
Date: Wed, 27 Oct 2021 11:05:54 +0200 [thread overview]
Message-ID: <878ryeet1p.fsf@gmx.de> (raw)
In-Reply-To: <e2898e04cf2eae3a0efd@heytings.org> (Gregory Heytings's message of "Wed, 27 Oct 2021 08:05:31 +0000")
Gregory Heytings <gregory@heytings.org> writes:
Hi Gregory,
>>> The second condition could perhaps be reworded as "Some completion
>>> styles, like 'substring' or 'flex', require to type at least one
>>> character after the trailing ':' *when they come first in the
>>> completion-styles list*."
>>
>> Just wondering: wouldn't be enough to change
>> icomplete--fido-mode-setup to use:
>>
>> (setq-local completion-styles '(flex basic))
>>
>> Instead of:
>>
>> (setq-local completion-styles '(flex))
>>
>> As it is doing currently?
>
> It depends what you mean by "being enough". That setting would be
> better, but you would still have to type the first character of the
> hostname. With that setting and my patch, everything would work as you
> would expect, namely, you wouldn't have to type the first character of
> the hostname anymore.
The better setting is '(basic flex). With that setting, there is no
problem at all. Try
emacs -Q -l tramp --eval "(setq completion-styles '(basic flex))"
This works out-of-the box, w/o any further patch (as you have said above).
If I do instead
emacs -Q -l tramp --eval "(setq completion-styles '(basic flex))" -f fido-vertical-mode
it doesn't work. Debugging of fido-vertical-mode is needed, I suppose.
Best regards, Michael.
next prev parent reply other threads:[~2021-10-27 9:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 14:37 bug#51386: 29.0.50; fido-vertical-mode: ssh host completion Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-25 14:54 ` Gregory Heytings
2021-10-25 15:08 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-25 16:13 ` Gregory Heytings
2021-10-26 4:47 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-26 7:13 ` Gregory Heytings
2021-10-26 15:30 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-26 16:00 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-26 18:12 ` Michael Albinus
2021-10-26 18:24 ` Gregory Heytings
2021-10-26 18:53 ` Michael Albinus
2021-10-26 19:06 ` Gregory Heytings
2021-10-27 5:50 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-27 7:51 ` Gregory Heytings
2021-10-27 7:55 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-27 8:05 ` Gregory Heytings
2021-10-27 8:07 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-27 9:05 ` Michael Albinus [this message]
2021-10-27 9:08 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-27 9:12 ` Gregory Heytings
2021-10-27 11:10 ` Michael Albinus
2021-10-27 11:19 ` Dmitry Gutov
2021-10-27 11:22 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-27 11:39 ` Gregory Heytings
2021-10-27 11:55 ` Michael Albinus
2021-10-27 11:23 ` Gregory Heytings
2021-10-27 11:42 ` Michael Albinus
2021-10-27 12:04 ` Gregory Heytings
2021-10-27 12:12 ` Michael Albinus
2021-10-27 10:15 ` Dmitry Gutov
2021-10-27 10:23 ` Gregory Heytings
2021-10-27 10:25 ` Dmitry Gutov
2021-10-27 11:35 ` Michael Albinus
2021-10-27 12:02 ` Gregory Heytings
2021-10-31 18:13 ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878ryeet1p.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=51386@debbugs.gnu.org \
--cc=gregory@heytings.org \
--cc=manuel.uberti@inventati.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).