Subject: Re: bug#28969: 27.0.50; dired: Confirmation prompt for wildcard not surrounded by whitespace

From: Kévin Le Gouguec <[email-masked]>
Date: Tue, 16 Jul 2019 07:53:09 +0200

Michael Heerdegen <[email-masked]> writes:

> 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?

No idea how to fix that off the top of my head.

> (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 "*"?

I think it really means *"".  From some quick testing in a Dired buffer:

    M-! touch foo bar baz RET
    g                           ; Assuming point is now on "bar"
    ! echo quux "*" corge RET y ; ⇒ quux * corge bar
    ! echo quux *"" corge RET y ; ⇒ quux bar baz foo corge bar

*'' also works.  AFAICT it's a way to work around Dired's isolation
detection (* is not surrounded with spaces, so it's not isolated) while
exploiting the fact that the quoted empty string will disappear once
"expanded" by the shell.