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: Sun, 15 Jan 2023 22:38:57 +0000 [thread overview]
Message-ID: <cf717d2477a320fb64ce@heytings.org> (raw)
In-Reply-To: <87a62jmwj6.fsf@gmx.de>
Hi Michael,
>> what do you think of that patch? It would be regrettable to leave that
>> bug unfixed in Emacs 29.
>
> Yes, it would be desirable to fix this. But it isn't the end of the
> world if this doesn't happen, the problem is already evident in Emacs
> 28, so we don't have a regression.
>
It's correct that the same problem is present in Emacs 28, but it is not
in Emacs 27, so it's a regression. As I tried to explain in bug#50387,
the problem is that once Tramp is loaded, Tramp methods are returned when
completions are requested for a root directory ("/"). This problem is
even worse since commit d5c6bf9625: prior to that commit only the 'scp'
and 'scpx' methods were returned (in emacs -Q), now all methods are
returned. And this confuses the flex and substring completion mechanisms.
>>> By the way, to limit the scope of the potential collateral damages, it
>>> is also possible to use that condition only when completion-styles
>>> contain 'substring' or 'flex'.
>>>
>>> What do you think of the attached patch?
>
> And what do we want to do if there are more completion-styles like this?
> Extend Tramp then?
>
Not extend Tramp, but add them, if necessary, to the list of
completion-styles that are handled specially by Tramp at that place.
Unless of course a better fix has been implemented in the meantime.
>
> And there are more use cases like this, which are not working properly.
> Think about changing the Tramp syntax to `separate', which means a
> remote file name like "[method/user@host]/path/to/file". If you use
> default completion, it works like this:
>
> - emacs -Q -l tramp --eval '(tramp-change-syntax (quote separate))'
> - Type "/ [ s TAB" and you see all methods
> - Continue with "s h / TAB" and you see nonsense :-(
> - Continue with "d TAB" and you see all possible host names starting with "d"
> - Select a host name and type "] TAB TAB" and you see the remote file names
>
> And now with fido:
>
> - emacs -Q -l tramp --eval '(tramp-change-syntax (quote separate))' -f fido-mode
> - Type "/ [ s TAB" and you see no completion at all
> - Continue with "s h / TAB" and you see the same nonsense :-(
> - Continue with "d TAB" and you see no completion at all
> - Type host name and type "] TAB TAB" and you see the remote file names
>
> Although the default completion isn't perfect (likely a Tramp bug),
> there is much more wrong with fido.
>
Well, that looks like a separate problem, with a non-default syntax, which
(given the number of hits of "tramp-change-syntax" on Google or on Github)
is apparently hardly ever used.
Nonetheless, I tried your recipe with the patch applied, and the good news
is that with it, under Fido, Tramp behaves the same way it behaves under
the default completions: the available methods are displayed after "/ [ s
TAB", the same nonsense is displayed after "/ [ ssh/ TAB", and the
possible host names are displayed after typing a letter followed by TAB.
>
> Instead, Tramp shall apply a patch which is not related there, which
> adds further dependencies, which is not working for all use cases, and
> which is good for making more trouble in the future. My opinion.
>
I don't understand what you mean here, sorry.
next prev parent reply other threads:[~2023-01-15 22:38 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cf717d2477a320fb64ce@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.