unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
* eshell & find
@ 2003-03-06 21:01 Peter Lee
  2003-03-06 21:04 ` Peter Lee
  0 siblings, 1 reply; 4+ messages in thread
From: Peter Lee @ 2003-03-06 21:01 UTC (permalink / raw)


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.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: eshell & find
  2003-03-06 21:01 eshell & find Peter Lee
@ 2003-03-06 21:04 ` Peter Lee
  2003-03-06 21:21   ` John Wiegley
  0 siblings, 1 reply; 4+ messages in thread
From: Peter Lee @ 2003-03-06 21:04 UTC (permalink / raw)


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?

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: eshell & find
  2003-03-06 21:04 ` Peter Lee
@ 2003-03-06 21:21   ` John Wiegley
  2003-03-06 21:47     ` Peter Lee
  0 siblings, 1 reply; 4+ messages in thread
From: John Wiegley @ 2003-03-06 21:21 UTC (permalink / raw)


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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: eshell & find
  2003-03-06 21:21   ` John Wiegley
@ 2003-03-06 21:47     ` Peter Lee
  0 siblings, 0 replies; 4+ messages in thread
From: Peter Lee @ 2003-03-06 21:47 UTC (permalink / raw)


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.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2003-03-06 21:47 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-03-06 21:01 eshell & find Peter Lee
2003-03-06 21:04 ` Peter Lee
2003-03-06 21:21   ` John Wiegley
2003-03-06 21:47     ` Peter Lee

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).