From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Politz <politza@hochschule-trier.de>
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, 25 Mar 2017 22:45:14 +0300 [thread overview]
Message-ID: <834lyhb0ol.fsf@gnu.org> (raw)
In-Reply-To: <871stldulp.fsf@luca> (message from Andreas Politz on Sat, 25 Mar 2017 20:28:18 +0100)
> From: Andreas Politz <politza@hochschule-trier.de>
> Cc: Colin <my.old.email.sucked@gmail.com>, 25807@debbugs.gnu.org
> Date: Sat, 25 Mar 2017 20:28:18 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > [...] 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.
>
> I think in order to do that we would have to figure out whether a given
> filename expands to some existing filenames or not, and this also for
> handled ones. The last part of which seems to be difficult.
Why is the last part difficult? directory-files already supports
that, doesn't it? And completion examines matching files as part of
its thing, so I hoped there's already an option to get that for free.
> A more simpler and less general approach would be the addition of a
> user-option, i.e. list-directory-use-wildcards.
The function in question already supports widlcards, so moving that
support to a new option would be a step backward, I think.
next prev parent reply other threads:[~2017-03-25 19:45 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
2017-03-25 16:16 ` Eli Zaretskii
2017-03-25 19:28 ` Andreas Politz
2017-03-25 19:45 ` Eli Zaretskii [this message]
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
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=834lyhb0ol.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25807@debbugs.gnu.org \
--cc=my.old.email.sucked@gmail.com \
--cc=politza@hochschule-trier.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).