From: Jimmy Yuen Ho Wong <wyuenho@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 39389@debbugs.gnu.org
Subject: bug#39389: 27.0.60; A couple of bugs messing with minibuffer completion of /sudo::
Date: Wed, 5 Feb 2020 13:31:31 +0000 [thread overview]
Message-ID: <CAKDRQS4LNSULn4cy6SErzZBWeSBjHpzr4CQPjXjp_z6TFtFgZQ@mail.gmail.com> (raw)
In-Reply-To: <875zgowy0b.fsf@gmx.de>
On Sun, Feb 2, 2020 at 8:11 PM Michael Albinus <michael.albinus@gmx.de> wrote:
>
> 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.
>
Because no reasonable person will knowing turn on something that will
break tramp during find-file completely.
> I agree with you, that the variable shall document its behaviour in this
> case.
>
It's not a documentation problem. It's called the principle of least
astonishment, and the culprit for bug 1 is hidden somewhere in
`ido-read-internal` in one of the 2 cases that deals with tramp
syntax.
For bug 2 and 3, there's definitely something wrong with the
`auth-source-search` call in `tramp-read-passwd` that's blocking the
display of the password prompt, as the same workaround works for both
issues.
next prev parent reply other threads:[~2020-02-05 13:31 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
2020-02-05 13:31 ` Jimmy Yuen Ho Wong [this message]
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
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=CAKDRQS4LNSULn4cy6SErzZBWeSBjHpzr4CQPjXjp_z6TFtFgZQ@mail.gmail.com \
--to=wyuenho@gmail.com \
--cc=39389@debbugs.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.
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).