--- Begin Message ---
Subject: |
dired-do-shell-command " *" vs. "*", too close for comfort |
Date: |
Sun, 04 Jul 2010 10:11:04 +0800 |
Gee, a little slip of the wrist,
(dired-do-shell-command "head -c 999 * |sum" nil (quote ("FlashXXV9Z9sz")))
(dired-do-shell-command "head -c 999 *|sum" nil (quote ("FlashXXV9Z9sz")))
and it goes and gets every file in the directory.
Yes I know it is all well documented, but I can't think of any computer
language where such a tiny difference can make such a big difference.
I don't have an exact solution. All I know is it will bite the reader
sooner or later.
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#6561: dired-do-shell-command " *" vs. "*", too close for comfort |
Date: |
Tue, 10 Jan 2012 21:27:05 -0500 |
User-agent: |
Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) |
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.
--- End Message ---