From: Gregory Heytings <gregory@heytings.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 60505@debbugs.gnu.org, Julien Roy <julien@jroy.ca>
Subject: bug#60505: 29.0.60; Fido Mode and Tramp Completion
Date: Thu, 05 Jan 2023 14:14:35 +0000 [thread overview]
Message-ID: <8dea9f3e0eb47ac9e4ab@heytings.org> (raw)
In-Reply-To: <87tu15m6g7.fsf@gmx.de>
>> 2. Doing that is not enough, because of an incompatibility between
>> Tramp and the 'flex' and 'substring' mechanisms. The Tramp manual has
>> a footnote which mentions that incompatibility: "Some completion
>> styles, like `substring' or `flex', require to type at least one
>> character after the trailing `:'." A one-line patch to fix it was
>> proposed, but rejected, a year and a half ago. It is attached to this
>> email, and you can use it locally. As I said in the bug thread in
>> which that patch was proposed: "I expect other bug reports from
>> confused users".
>
> I don't deny that there is a problem, and it isn't a surprise that
> people report about. But I don't think that Tramp misbehaves, it does
> exactly what it is specified to do.
>
You may remind that we disagreed on that point. When a connection method
has already been fully specified by the user, such as "/ssh:", there is no
reason Tramp should tell the user that there are two other connection
methods "/sshfs:" and "/sshx:". IOW, after
C-x C-f /ssh TAB
it makes sense to tell the user that there are three possible methods:
"/ssh:", "/sshfs:" and "/sshx:". But after
C-x C-f /ssh: TAB
there is no reason to do that again. What the user expects at that point
is a list of hostnames.
>
> I guess that flex and friends use completion out of the specification.
> But I have no knowledge about the completion machinery; otherwise I
> would have tried to find the root of the problem. I'm also not opposed
> to extend the completion API for use in Tramp. What I'm opposed to is to
> apply just an ad-hoc patch, which could have collateral damages.
>
> I still hope that somebody with more knowledge about the completion
> machinery could take a stab at it.
>
Why could we not use the ad-hoc patch, with a FIXME note, until somebody
has the time to find a better solution, instead of letting bug reports
about that problem accumulate? Sure, it could possibly have a collateral
damage, but it could as well have no collateral damage at all.
next prev parent reply other threads:[~2023-01-05 14:14 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 19:37 bug#60505: 29.0.60; Fido Mode and Tramp Completion Julien Roy
2023-01-03 8:56 ` Michael Albinus
2023-01-05 13:07 ` Gregory Heytings
2023-01-05 13:55 ` Michael Albinus
2023-01-05 14:14 ` Gregory Heytings [this message]
2023-01-06 9:51 ` Gregory Heytings
2023-01-14 21:37 ` Gregory Heytings
2023-01-15 19:23 ` Michael Albinus
2023-01-15 22:38 ` Gregory Heytings
2023-01-18 12:30 ` Michael Albinus
2023-02-01 18:12 ` Gregory Heytings
2023-02-01 20:15 ` Michael Albinus
2023-02-01 21:27 ` Gregory Heytings
2023-02-02 6:37 ` Eli Zaretskii
2023-02-02 8:25 ` Michael Albinus
2023-02-02 9:15 ` Eli Zaretskii
2023-02-02 15:39 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-03 15:40 ` Michael Albinus
2023-02-03 18:43 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-03 19:23 ` Michael Albinus
2023-02-03 20:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-04 16:04 ` Michael Albinus
2023-02-04 16:48 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-03 22:33 ` Gregory Heytings
2023-02-04 9:54 ` Michael Albinus
2023-02-06 17:26 ` Michael Albinus
2023-02-06 17:41 ` Gregory Heytings
2023-02-07 0:35 ` Michael Heerdegen
2023-02-07 8:54 ` Michael Albinus
2023-02-07 18:20 ` Michael Heerdegen
2023-02-07 18:30 ` Michael Albinus
2023-02-07 20:39 ` Michael Heerdegen
[not found] ` <87357h19qj.fsf@dick>
2023-02-08 8:05 ` Michael Albinus
2023-02-08 11:27 ` dick
2023-02-08 13:08 ` Michael Albinus
2023-02-08 13:20 ` Eli Zaretskii
2023-02-08 14:13 ` dick
2023-02-08 14:42 ` Michael Albinus
2023-02-08 13:30 ` dick
2023-02-08 15:04 ` Michael Albinus
2023-02-07 22:22 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-08 15:11 ` Michael Albinus
2023-02-08 16:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-08 17:59 ` Michael Albinus
2023-02-08 19:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-10 16:55 ` Michael Albinus
2023-02-12 19:26 ` Michael Albinus
2023-02-07 19:18 ` Michael Heerdegen
2023-02-08 15:09 ` Michael Albinus
2023-02-09 0:38 ` Michael Heerdegen
2023-02-03 0:23 ` Gregory Heytings
2023-02-03 7:43 ` Juri Linkov
2023-02-03 8:39 ` Michael Albinus
2023-02-03 12:01 ` Eli Zaretskii
2023-02-02 15:16 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-02 15:05 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-05 20:58 ` Julien Roy
[not found] <874k4xblcy.fsf.ref@aol.com>
2022-02-17 14:47 ` bug#54042: 29.0.50; fido-mode and ssh not listing hosts Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-17 16:43 ` Michael Albinus
[not found] ` <handler.54042.D60505.167623003032452.notifdone@debbugs.gnu.org>
2023-02-15 18:31 ` bug#54042: closed (Re: bug#60505: 29.0.60; Fido Mode and Tramp Completion) Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-16 8:51 ` Michael Albinus
2023-02-18 17:25 ` Michael Albinus
2023-02-19 2:04 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-19 9:53 ` 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=8dea9f3e0eb47ac9e4ab@heytings.org \
--to=gregory@heytings.org \
--cc=60505@debbugs.gnu.org \
--cc=julien@jroy.ca \
--cc=michael.albinus@gmx.de \
/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).