From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
Dmitry Gutov <dgutov@yandex.ru>
Cc: 25807@debbugs.gnu.org, my.old.email.sucked@gmail.com
Subject: bug#25807: 24.5; List-Directory closes with error when invalid path is typed instead of prompting the user to fix it
Date: Sat, 04 Mar 2017 12:23:04 +0200 [thread overview]
Message-ID: <838toll4s7.fsf@gnu.org> (raw)
In-Reply-To: <83mvdbsmi6.fsf@gnu.org> (message from Eli Zaretskii on Fri, 24 Feb 2017 16:15:45 +0200)
Ping!
> Date: Fri, 24 Feb 2017 16:15:45 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 25807@debbugs.gnu.org
>
> > From: Colin <my.old.email.sucked@gmail.com>
> > Date: Mon, 20 Feb 2017 17:20:10 +1100
> >
> > If I hit `C-x C-d`, I receive the prompt `List directory (breif): ~/` - if I
> > type `/tmp/foo` and hit Enter my message buffer shows `insert-directory:
> > Reading directory: no such file or directory, /tmp/foo` - the prompt has
> > now gone and I'm unable to fix my mistake without repeating the entire
> > process.
>
> Could someone knowledgeable about completion please suggest a way to
> do better in these use cases, or perhaps propose a patch? We are
> looking for a way to reject non-existing directories, but accept
> existing ones and wildcards, when the user types RET in these cases.
>
> There is "permissive completion with confirmation", but that requires
> the user to type TAB before it kicks in, which IMO is sub-optimal (and
> counter-intuitive) in this case.
>
> TIA
next prev parent reply other threads:[~2017-03-04 10:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 6:20 bug#25807: 24.5; List-Directory closes with error when invalid path is typed instead of prompting the user to fix it Colin
2017-02-24 14:15 ` Eli Zaretskii
2017-03-04 10:23 ` Eli Zaretskii [this message]
2017-03-25 16:16 ` Eli Zaretskii
2017-03-25 19:28 ` Andreas Politz
2017-03-25 19:45 ` Eli Zaretskii
2021-12-01 19:16 ` Lars Ingebrigtsen
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=838toll4s7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25807@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=monnier@iro.umontreal.ca \
--cc=my.old.email.sucked@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.