From: Gregory Heytings <gregory@heytings.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Michael Albinus <michael.albinus@gmx.de>, 50387@debbugs.gnu.org
Subject: bug#50387: Possible bug in Tramp or in completions
Date: Mon, 06 Sep 2021 21:39:06 +0000 [thread overview]
Message-ID: <75d560562c5746180cb6@heytings.org> (raw)
In-Reply-To: <jwvfsuh5tlb.fsf-monnier+emacs@gnu.org>
>
> The completion tables's API only directly support prefix completion. So
> in order to implement `substring` style, when the minibuffer.el code
> sees a request for completion of "/a" it will request all the possible
> prefix-completions for "/" and then filter them based on the presence of
> "a" in there.
>
Thank you. Now I understand the bug better: when the user types / TAB,
Tramp returns the default methods (scp: scpx:), when the user types /sc
TAB, Tramp returns the methods starting with 'sc', i.e. scp: scpx:, and
when the user types /scp: TAB, Tramp again returns the default methods
scp: scpx:, because it is again at '/', and the substring completion
backend concludes that "scp:" cannot be completed further, which is wrong.
With my patch, when the user types / TAB, Tramp does not return the
default methods anymore, and therefore they are not returned after /scp:
TAB either. So IMO the patch does TRT, and fixes both the behavior with
substring and flex completion styles.
next prev parent reply other threads:[~2021-09-06 21:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 0:43 bug#50387: Possible bug in Tramp or in completions Gregory Heytings
2021-09-05 12:49 ` Gregory Heytings
2021-09-06 8:18 ` Michael Albinus
2021-09-06 16:34 ` Gregory Heytings
2021-09-06 16:59 ` Michael Albinus
2021-09-06 17:26 ` Gregory Heytings
2021-09-06 17:41 ` Michael Albinus
2021-09-06 18:22 ` Gregory Heytings
2021-09-06 19:39 ` Michael Albinus
2021-09-06 20:00 ` Gregory Heytings
2021-09-06 20:31 ` Michael Albinus
2021-09-06 20:55 ` Gregory Heytings
2021-09-07 12:58 ` Michael Albinus
2021-09-07 13:23 ` Gregory Heytings
2021-09-07 13:30 ` Gregory Heytings
2021-09-07 14:23 ` Michael Albinus
2021-09-07 16:46 ` Gregory Heytings
2021-09-07 17:31 ` Michael Albinus
2021-09-07 17:51 ` Gregory Heytings
2021-09-07 18:04 ` Michael Albinus
2021-09-07 19:02 ` Gregory Heytings
2021-09-07 19:41 ` Gregory Heytings
2021-09-08 7:28 ` Michael Albinus
2021-09-08 7:26 ` Michael Albinus
2021-09-08 7:57 ` Gregory Heytings
2021-09-08 14:25 ` Michael Albinus
2021-09-07 13:37 ` Lars Ingebrigtsen
2021-09-07 14:31 ` Michael Albinus
2021-09-06 20:41 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-06 20:49 ` Michael Albinus
2021-09-06 21:39 ` Gregory Heytings [this message]
2021-09-07 5:42 ` Eli Zaretskii
2021-09-07 11:29 ` Michael Albinus
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=75d560562c5746180cb6@heytings.org \
--to=gregory@heytings.org \
--cc=50387@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--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 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).