unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Gregory Heytings <gregory@heytings.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 50387@debbugs.gnu.org
Subject: bug#50387: Possible bug in Tramp or in completions
Date: Tue, 07 Sep 2021 13:23:10 +0000	[thread overview]
Message-ID: <11c4e3821a86a11e0b8f@heytings.org> (raw)
In-Reply-To: <87eea0czkx.fsf@gmx.de>


>
> All of this does not fit to your commit message "Do not return methods 
> when the filename already contains a complete method.", I believe. But 
> so what.
>

It could be more precise indeed: "when the filename alread contains a 
complete method or does not contain the prefix of a method", or something 
like that.

>
> Your patch does not handle the case when `tramp-syntax' is `separate'. 
> There are no methods in the remote file name then, and you must handle 
> user and host names properly.
>

I guess adding a test to the conditional would be sufficient: (unless 
(string-empty-p method) -> (unless (or (string-empty-p method) (eq 
'tramp-syntax 'separate)).  I do know what the "separate" syntax is, so I 
did not test it.

>
> Finally, I have submitted a patch to master, which deactivates *default* 
> method, user and host name expansion in 
> `tramp-completion-handle-file-name-all-completions'. The difference to 
> your patch is, that it doesn't manipulate the results, but it 
> deactivates this expansion by usual Tramp means.
>
> Could you pls check how it fits in your use case? My (limited) tests 
> along your examples look good.
>

Alas it doesn't.

emacs -Q -l tramp --eval "(add-to-list 'completion-styles 'substring)"

C-x C-f /scp: TAB

still shows "Sole completion".





  reply	other threads:[~2021-09-07 13:23 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 [this message]
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=11c4e3821a86a11e0b8f@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).