GNU bug report logs - #6561
dired-do-shell-command " *" vs. "*", too close for comfort

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Glenn Morris <rgm <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#6561: closed (dired-do-shell-command " *" vs. "*", too close
 for comfort)
Date: Wed, 11 Jan 2012 02:28:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Tue, 10 Jan 2012 21:27:05 -0500
with message-id <an4nw3m0sm.fsf <at> fencepost.gnu.org>
and subject line Re: bug#6561: dired-do-shell-command " *" vs. "*", too close for comfort
has caused the debbugs.gnu.org bug report #6561,
regarding dired-do-shell-command " *" vs. "*", too close for comfort
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
6561: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=6561
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: jidanni <at> jidanni.org
To: bug-gnu-emacs <at> gnu.org
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.

[Message part 3 (message/rfc822, inline)]

From: Glenn Morris <rgm <at> gnu.org>
To: 6561-done <at> debbugs.gnu.org
Subject: Re: bug#6561: dired-do-shell-command " *" vs. "*",
	too close for comfort
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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.