From: Michael Albinus <michael.albinus@gmx.de>
To: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
Cc: 39389@debbugs.gnu.org
Subject: bug#39389: 27.0.60; A couple of bugs messing with minibuffer completion of /sudo::
Date: Sun, 02 Feb 2020 21:11:00 +0100 [thread overview]
Message-ID: <875zgowy0b.fsf@gmx.de> (raw)
In-Reply-To: <9b2b8ce4-97fc-52cf-384d-2ee83ca37251@gmail.com> (Jimmy Yuen Ho Wong's message of "Sun, 2 Feb 2020 18:30:40 +0000")
Jimmy Yuen Ho Wong <wyuenho@gmail.com> writes:
>> I'm just surprised, that you set ido-enable-tramp-completion to nil, and
>> that you still expect Tramp file name support. That doesn't sound right
>> to me.
> I expect either that variable didn't exist and Tramp file name
> completion was always fast, or when it's off, ido just reverts back to
> the behavior of the regular `find-file`, which should allow me to type
> out the whole Tramp syntax.
Why do you expect this? At least the docstring of that variable doesn't
tell that ido behaves like this, when the variable is set to nil.
I agree with you, that the variable shall document its behaviour in this
case.
Best regards, Michael.
next prev parent reply other threads:[~2020-02-02 20:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 14:50 bug#39389: 27.0.60; A couple of bugs messing with minibuffer completion of /sudo:: Jimmy Yuen Ho Wong
2020-02-02 15:47 ` Michael Albinus
2020-02-02 18:05 ` Jimmy Yuen Ho Wong
2020-02-02 18:14 ` Michael Albinus
2020-02-02 18:30 ` Jimmy Yuen Ho Wong
2020-02-02 20:11 ` Michael Albinus [this message]
2020-02-05 13:31 ` Jimmy Yuen Ho Wong
2020-02-05 14:39 ` Michael Albinus
2020-02-08 13:03 ` Jimmy Yuen Ho Wong
2020-02-08 18:36 ` Michael Albinus
2020-02-09 5:22 ` Jimmy Yuen Ho Wong
2020-02-09 23:44 ` Jimmy Yuen Ho Wong
2020-02-10 0:16 ` Jimmy Yuen Ho Wong
2020-02-10 9:23 ` Michael Albinus
2020-02-10 9:18 ` Michael Albinus
2020-02-10 21:00 ` Jimmy Yuen Ho Wong
2020-02-10 21:06 ` Jimmy Yuen Ho Wong
2020-02-11 8:56 ` Michael Albinus
2020-02-16 19:30 ` 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=875zgowy0b.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=39389@debbugs.gnu.org \
--cc=wyuenho@gmail.com \
/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.