eshell & find

eshell & find

[Peter Lee]

The following works fine from both eshell and shell (with shell for me
being cmd.exe for xp):

find . -iregex ".*\.cpp"


However, the following works only with shell and *not* with
eshell... eshell simply returns.

find . -iregex ".*\.cpp\|.*\.h"

Any ideas why this wouldn't work in eshell ?

Thanks.

Re: eshell & find

[Peter Lee]

Peter Lee <pete_lee/remove-for-email/@swbell.net> writes:

> The following works fine from both eshell and shell (with shell for me
> being cmd.exe for xp):
> 
> find . -iregex ".*\.cpp"
> 
> 
> However, the following works only with shell and *not* with
> eshell... eshell simply returns.
> 
> find . -iregex ".*\.cpp\|.*\.h"
> 

After more experimentation I tried the following:

find . -iregex ".*\\.cpp\\|.*\\.h"

And that works as expected from eshell... So why do I need to
backlashes to escape from eshell but not a normal shell?

Re: eshell & find

[John Wiegley]

Peter Lee <pete_lee/remove-for-email/@swbell.net> writes:

> After more experimentation I tried the following:
>
> find . -iregex ".*\\.cpp\\|.*\\.h"
>
> And that works as expected from eshell... So why do I need to
> backlashes to escape from eshell but not a normal shell?

Because Eshell is basically passing your string on to Lisp, which
needs the double-backslashing.  It's the same behavior expected by
bash.  In this case, cmd.exe is the oddball.

John

Re: eshell & find

[Peter Lee]

John Wiegley <johnw@gnu.org> writes:

> Because Eshell is basically passing your string on to Lisp, which
> needs the double-backslashing.  It's the same behavior expected by
> bash.  In this case, cmd.exe is the oddball.

Ok thanks.