From: John Wiegley <johnw@gnu.org>
Subject: Re: eshell & find
Date: Thu, 06 Mar 2003 14:21:32 -0700 [thread overview]
Message-ID: <871y1k6vj7.fsf@alice.dynodns.net> (raw)
In-Reply-To: uwujckxzz.fsf@swbell.net
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
next prev parent reply other threads:[~2003-03-06 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 21:01 eshell & find Peter Lee
2003-03-06 21:04 ` Peter Lee
2003-03-06 21:21 ` John Wiegley [this message]
2003-03-06 21:47 ` Peter Lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871y1k6vj7.fsf@alice.dynodns.net \
--to=johnw@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).