From: Michael Heerdegen <michael_heerdegen@web.de>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
28969@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>
Subject: bug#28969: 27.0.50; dired: Confirmation prompt for wildcard not surrounded by whitespace
Date: Mon, 15 Jul 2019 22:50:12 +0200 [thread overview]
Message-ID: <87wogjxbsr.fsf@web.de> (raw)
In-Reply-To: <87blxvp0ly.fsf@gmail.com> ("Kévin Le Gouguec"'s message of "Mon, 15 Jul 2019 21:19:05 +0200")
Kévin Le Gouguec <kevin.legouguec@gmail.com> writes:
> Yup, that's what I set out to do in bug#35564. Here is the patch
> series, condensed into a single patch for convenience.
Ok, will try it.
> Although note that you can already tell Dired that your '?' is meant to
> be substituted, by surrounding it with backquotes. E.g. try to mark
> some files, then
>
> ! echo 'foo`?`bar'
Maybe this is already enough.
> It's not implemented for '*' though.
Dunno if that has use cases.
BTW, in the docstring of `dired-do-shell-command',
(1) In this sentence:
| `*' and `?' when not surrounded by whitespace nor ``' have no special
can we avoid that ` gets linked to the backquote macro?
And
(2) "If you want to use `*' as a shell wildcard with whitespace around
it, write `*\"\"' in place of just `*'."
does that really mean *"" or rather "*"?
Michael.
next prev parent reply other threads:[~2019-07-15 20:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 16:40 bug#28969: 27.0.50; dired: Confirmation prompt for wildcard not surrounded by whitespace Michael Heerdegen
2019-07-14 21:23 ` Lars Ingebrigtsen
2019-07-14 22:38 ` Noam Postavsky
2019-07-15 1:34 ` Michael Heerdegen
2019-07-15 19:19 ` Kévin Le Gouguec
2019-07-15 20:50 ` Michael Heerdegen [this message]
2019-07-16 5:53 ` Kévin Le Gouguec
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=87wogjxbsr.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=28969@debbugs.gnu.org \
--cc=kevin.legouguec@gmail.com \
--cc=larsi@gnus.org \
--cc=npostavs@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 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).