From: Taj Khattra <taj.khattra@pobox.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] configure misery
Date: Thu, 13 Nov 2003 08:17:59 -0800 [thread overview]
Message-ID: <20031113161759.GC21872@localhost.localdomain> (raw)
In-Reply-To: <81132473206F3A46A72BD6116E1A06AE479CA3@black.aprote.com>
On Thu, Nov 13, 2003 at 01:26:42PM +0200, Tiit Lankots wrote:
> >Seeing as how this is grep, the + is NOT a metacharacter. Thus it's
>
> Not necessarily. GNU grep (by far the most widespread by now) is using
> the 'extended' syntax where + IS a metacharacter.
only if you ask it to do so (i think via 'grep -E')
-taj
next parent reply other threads:[~2003-11-13 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <81132473206F3A46A72BD6116E1A06AE479CA3@black.aprote.com>
2003-11-13 16:17 ` Taj Khattra [this message]
[not found] <c40d2beae31a26c28b62b84dbf5acba0@hamnavoe.com>
2003-11-13 22:51 ` Bruce Ellis
2003-11-13 23:10 ` Charles Forsyth
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=20031113161759.GC21872@localhost.localdomain \
--to=taj.khattra@pobox.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).