From: David Gordon Hogan <dhog@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Sam / text search query
Date: Thu, 20 Jun 2002 14:58:34 -0400 [thread overview]
Message-ID: <dea1eb8c794b16e2ea80c6da70ccfc26@plan9.bell-labs.com> (raw)
>> > not forgetting that the "s" command supports \(...\) etc.
>> ...while remembering that, as with all regexps in plan 9,
>> the old ed-like \( and \) become egrep-like ( and ),
>
> Yeah, actually that's a pet peeve.
I'm a little confused. Are you peeved at egrep's behaviour,
sam's regexp behaviour, or both?
I much prefer sam's behaviour (which is actually Plan 9
regexp's behaviour in general). You can escape anything
with "\". In egrep, both '(' and '\(' are (different)
metacharacters.
next reply other threads:[~2002-06-20 18:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 18:58 David Gordon Hogan [this message]
2002-06-21 15:00 ` Douglas A. Gwyn
-- strict thread matches above, loose matches on Subject: below --
2002-06-20 16:21 rog
2002-06-19 16:08 rog
2002-06-20 15:47 ` Douglas A. Gwyn
2002-06-18 21:06 Andrew Simmons
2002-06-19 15:37 ` Douglas A. Gwyn
2002-06-18 17:31 Gerry Tomlinson
2002-06-18 5:07 rob pike, esq.
2002-06-18 5:03 Andrew Simmons
2002-06-18 15:03 ` Douglas A. Gwyn
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dea1eb8c794b16e2ea80c6da70ccfc26@plan9.bell-labs.com \
--to=dhog@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).