unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Tramp shows no user/host completions (solved while writing)
Date: Sat, 26 Oct 2019 23:51:06 +0200	[thread overview]
Message-ID: <87zhhn9nw5.fsf@gnu.org> (raw)
In-Reply-To: <87lft8yjnj.fsf@gmx.de> (Michael Albinus's message of "Fri, 25 Oct 2019 16:38:56 +0200")

Michael Albinus <michael.albinus@gmx.de> writes:

> Indeed. When I complete "/ssh:f TAB" with one of `emacs21', `emacs22'
> or `basic' in `completion-styles', I see the call
>
> (file-name-all-completions "ssh:f" "/")
>
> which performs host name completion in Tramp. For the other completion
> styles, there is just
>
> (file-name-all-completions "ssh" "/") ;; for `partial-completion'
>
> or
>
> (file-name-all-completions "" "/") ;; for `substring' and `flex'
>
> or even no call for `initials'.

Would you consider that a bug?

At least from a user perspective, it seems odd that more powerful
completion styles restrict the completion candidates, though I do
understand the technical details that lead to the observed results.

> So I have added the following sentence to the Tramp manual:
>
> User name and host name completion is activated only, if file name
> completion has one of the styles ‘basic’, ‘emacs21’, or ‘emacs22’.
> *Note (emacs)Completion Styles::.

Good.  (But it would be better if it wasn't needed.)

Bye,
Tassilo



  reply	other threads:[~2019-10-26 21:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 16:01 Tramp shows no user/host completions (solved while writing) Tassilo Horn
2019-10-24 16:47 ` Drew Adams
2019-10-24 19:40   ` Michael Albinus
2019-10-24 20:08     ` Drew Adams
2019-10-24 19:36 ` Michael Albinus
2019-10-24 19:45   ` Tassilo Horn
2019-10-25  5:00     ` Tassilo Horn
2019-10-25 14:38       ` Michael Albinus
2019-10-26 21:51         ` Tassilo Horn [this message]
2019-10-27  8:01           ` Michael Albinus
2019-10-27 21:30             ` Stefan Monnier
2019-10-28  6:57               ` Tassilo Horn
2019-10-28  7:44               ` 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=87zhhn9nw5.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    --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.
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).