From: Gregory Heytings <gregory@heytings.org>
To: 50387@debbugs.gnu.org
Subject: bug#50387: Possible bug in Tramp or in completions
Date: Sun, 05 Sep 2021 00:43:59 +0000 [thread overview]
Message-ID: <79cd87e590549c0d916d@heytings.org> (raw)
With a ~/.ssh/config file containing two entries:
Host foo
...
Host bar
...
emacs -Q
M-: (setq tramp-default-method "ssh")
M-: (add-to-list 'completion-styles 'substring)
C-x C-x /ssh: TAB
displays "Sole completion". If, instead of having completion-styles set
to:
(substring basic partial-completion emacs22)
it is set to:
(basic substring partial-completion emacs22)
then two completion candidates are shown (as expected): "ssh:foo:" and
"ssh:bar:".
This happens because the "substring" completion mechanism is tried first
by completion--some in completion--nth-completion, and returns (t .
substring), because
(completion-substring-try-completion "/ssh:" #'completion-file-name-table
#'file-exists-p 5)
returns t, because
(completion-substring--all-completions "/ssh:"
#'completion-file-name-table #'file-exists-p 5) returns (("ssh:")
returns (prefix "ssh:") "/" "" 1), because
(completion-boundaries "/ssh:" #'completion-file-name-table
#'file-exists-p "")
returns (1 . 0).
When the "basic" completion mechanism is tried first,
(completion-basic-try-completion "/ssh:" #'completion-file-name-table
#'file-exists-p 5)
returns ("/ssh:" . 5).
It is not clear to me whether this is a bug (I always thought that the
order of completion mechanisms in completion-styles did not matter, and in
this case it does indeed make no difference with (setq
tramp-default-method "scp")), and if so if it is a bug in Tramp, or in the
completion functions.
next reply other threads:[~2021-09-05 0:43 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 0:43 Gregory Heytings [this message]
2021-09-05 12:49 ` bug#50387: Possible bug in Tramp or in completions 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
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=79cd87e590549c0d916d@heytings.org \
--to=gregory@heytings.org \
--cc=50387@debbugs.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).