* bug#6561: dired-do-shell-command " *" vs. "*", too close for comfort
@ 2010-07-04 2:11 ` jidanni
2012-01-11 2:27 ` Glenn Morris
2012-01-11 3:14 ` bug#6561: closed (Re: bug#6561: dired-do-shell-command " *" vs. "*", too close for comfort) jidanni
0 siblings, 2 replies; 4+ messages in thread
From: jidanni @ 2010-07-04 2:11 UTC (permalink / raw)
To: 6561
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#6561: dired-do-shell-command " *" vs. "*", too close for comfort
2010-07-04 2:11 ` bug#6561: dired-do-shell-command " *" vs. "*", too close for comfort jidanni
@ 2012-01-11 2:27 ` Glenn Morris
2012-01-11 2:34 ` Glenn Morris
2012-01-11 3:14 ` bug#6561: closed (Re: bug#6561: dired-do-shell-command " *" vs. "*", too close for comfort) jidanni
1 sibling, 1 reply; 4+ messages in thread
From: Glenn Morris @ 2012-01-11 2:27 UTC (permalink / raw)
To: 6561-done
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#6561: dired-do-shell-command " *" vs. "*", too close for comfort
2012-01-11 2:27 ` Glenn Morris
@ 2012-01-11 2:34 ` Glenn Morris
0 siblings, 0 replies; 4+ messages in thread
From: Glenn Morris @ 2012-01-11 2:34 UTC (permalink / raw)
To: 6561
Glenn Morris wrote:
> I still have no idea what:
>
> To pass `*' by itself to the shell as a wildcard, type `*\"\"'.
>
> is supposed to mean though.
I see the manual explains it better:
If you want to use `*' as a shell wildcard with whitespace around it,
^^^^^^^^^^^^^^^
write `*""'. In the shell, this is equivalent to `*'; but since the `*'
is not surrounded by whitespace, Dired does not treat it specially.
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#6561: closed (Re: bug#6561: dired-do-shell-command " *" vs. "*", too close for comfort)
2010-07-04 2:11 ` bug#6561: dired-do-shell-command " *" vs. "*", too close for comfort jidanni
2012-01-11 2:27 ` Glenn Morris
@ 2012-01-11 3:14 ` jidanni
1 sibling, 0 replies; 4+ messages in thread
From: jidanni @ 2012-01-11 3:14 UTC (permalink / raw)
To: 6561
Well
GbTS> `*' and `?' when not surrounded by whitespace have no special
such design is too risky for the general public anyway.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-01-11 3:14 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <handler.6561.D6561.132624885123874.notifdone@debbugs.gnu.org>
2010-07-04 2:11 ` bug#6561: dired-do-shell-command " *" vs. "*", too close for comfort jidanni
2012-01-11 2:27 ` Glenn Morris
2012-01-11 2:34 ` Glenn Morris
2012-01-11 3:14 ` bug#6561: closed (Re: bug#6561: dired-do-shell-command " *" vs. "*", too close for comfort) jidanni
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).