Subject: Re: bug#6561: dired-do-shell-command " *" vs. "*", too close for comfort

From: Glenn Morris <[email-masked]>
Date: Tue, 10 Jan 2012 21:27:05 -0500

Version: 24.0.93

dired-do-shell-command claims to have a safety feature for this:

  `*' and `?' when not surrounded by whitespace have no special
  significance for `dired-do-shell-command', and are passed through
  normally to the shell, but you must confirm first.

AFAICS, due to a logic bug this feature has never worked.
Hopefully now it does.

I still have no idea what:

   To pass `*' by itself to the shell as a wildcard, type `*\"\"'.

is supposed to mean though.