bug#4406: 23.1; eshell quoting problem with -exec rm {} \;

bug#4406: 23.1; eshell quoting problem with -exec rm {} \;

[Xah Lee]

this is probably a bug.

when running eshell in Windows, i do

c:\Users\xah\web>find -name "*el" -exec rm {} \;
find -name "*el" -exec rm {} \;
find: missing argument to `-exec'

it turns out, one needs to quote the ending semicolon.

This does not work:
find -name "*el" -exec rm {} \\;

This works:
find -name "*el" -exec rm {} ';'

It appears to me, this seems to be a bug, since
-exec rm {} \;
is a standard idiom in bash, and no reason that shouldn't work.

(Pascal J Bourguignon gave the correct solution. This issue is discussed a 
bit at gnu.emacs.help here
http://groups.google.com/group/gnu.emacs.help/browse_frm/thread/46eb4e95fcbc1fb9? )

  Xah
∑ http://xahlee.org/

☄ 

bug#4406: 23.1; eshell quoting problem with -exec rm {} \;

[Eli Zaretskii]

> From: "Xah Lee" <xah@xahlee.org>
> Date: Fri, 11 Sep 2009 11:59:30 -0700
> Cc: 
> 
> c:\Users\xah\web>find -name "*el" -exec rm {} \;
> find -name "*el" -exec rm {} \;
> find: missing argument to `-exec'
> 
> it turns out, one needs to quote the ending semicolon.
> 
> This does not work:
> find -name "*el" -exec rm {} \\;
> 
> This works:
> find -name "*el" -exec rm {} ';'
> 
> It appears to me, this seems to be a bug, since
> -exec rm {} \;
> is a standard idiom in bash, and no reason that shouldn't work.

Eshell is not Bash, and on Windows, it treats the backslash as a
directory separator (unlike Bash).

So I think this is not a bug, just a platform-specific behavior that
needs to be learned.