From: Lars Ingebrigtsen <larsi@gnus.org>
To: Tassilo Horn <tsdh@gnu.org>
Cc: Michael Albinus <michael.albinus@gmx.de>, 37954@debbugs.gnu.org
Subject: bug#37954: 27.0.50; No Tramp completion if completion-styles doesn't include basic, emacs22, or emacs21
Date: Fri, 20 May 2022 13:00:18 +0200 [thread overview]
Message-ID: <87a6bc4gfx.fsf@gnus.org> (raw)
In-Reply-To: <87zhhls7uo.fsf@gnu.org> (Tassilo Horn's message of "Mon, 28 Oct 2019 07:27:11 +0100")
Tassilo Horn <tsdh@gnu.org> writes:
> With
>
> emacs -Q --eval "(setq completion-styles '(partial-completion
> substring initials flex) completion-category-overrides nil)"
>
> Tramp file name completion does not work. E.g., C-x C-f /ssh:<tab> will
> not suggest usernames and hostnames. Currently, it is mandatory to have
> one of the completion styles basic, emacs22, or emacs21 enabled.
>
> Stefan Monnier explained why that's currently the way it is and possible
> solutions to the problem in
>
> https://lists.gnu.org/archive/html/help-gnu-emacs/2019-10/msg00148.html
>
> For the time being, I'd suggest to adapt the completion styles
> documentation so that it explititly mentions keeping a basic style
> (basic, emacs22, or emacs21) in completion-styles.
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
Adding that to the doc string of `completion-styles' sounds OK to me,
but perhaps Michael has some comments about why/whether this is
necessary; added to the CCs.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-20 11:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 6:27 bug#37954: 27.0.50; No Tramp completion if completion-styles doesn't include basic, emacs22, or emacs21 Tassilo Horn
2022-05-20 11:00 ` Lars Ingebrigtsen [this message]
2022-05-20 13:54 ` Michael Albinus
2022-05-21 12:47 ` Lars Ingebrigtsen
2023-02-13 9:33 ` Michael Albinus
2023-02-13 11:55 ` Gregory Heytings
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=87a6bc4gfx.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=37954@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=tsdh@gnu.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).