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

Previous Next

Package: emacs;

Reported by: jidanni <at> jidanni.org

Date: Sun, 4 Jul 2010 02:12:02 UTC

Severity: wishlist

Fixed in version 24.0.93

Done: Glenn Morris <rgm <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


Message #10 received at 6561-done <at> debbugs.gnu.org (full text, mbox):

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.




This bug report was last modified 13 years and 163 days ago.

Previous Next


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