From: Wayne.Brown@altec.com
To: Joel Jaeggli <joelja@darkwing.uoregon.edu>
Cc: Hacksaw <hacksaw@hacksaw.org>, linux-kernel@vger.kernel.org
Subject: Re: Not a typewriter
Date: Fri, 11 May 2001 13:37:53 -0500 [thread overview]
Message-ID: <86256A49.00664FCE.00@smtpnotes.altec.com> (raw)
On 05/11/2001 at 12:03:43 PM Joel Jaeggli <joelja@darkwing.uoregon.edu> wrote:
>it's not clear to me that that textsearch is a more accurate description
>than Get Regular ExPression
It's not more accurate. But Hacksaw's original point was that a new user would
not know what "not a typewriter" meant. My point was that a newbie wouldn't be
likely to guess that "grep" means "search for text" either; in both cases he'd
have to look it up if he'd never seen it before.
BTW, grep does not stand for "Get Regular ExPression." It comes from an
often-used command in the ed (and ex and vi) editor: g/re/p. The "g" means
"global," the "re" is a regular expression, and the "p" means "print." So to
search for all lines containing the word "foo" in a file you were editing, you
would type g/foo/p. This was such a useful function that it was packaged in a
standalone program that could be used to search multiple files.
Wayne
next reply other threads:[~2001-05-11 18:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 18:37 Wayne.Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-14 2:59 Not a typewriter Wayne.Brown
2001-05-11 23:57 Bingner Sam J. Contractor RSIS
2001-05-11 23:18 Wayne.Brown
2001-05-14 22:22 ` Kai Henningsen
2001-05-11 16:07 Wayne.Brown
2001-05-11 17:03 ` Joel Jaeggli
2001-05-11 21:43 ` Hacksaw
2001-05-13 23:39 ` Mike A. Harris
2001-05-12 4:18 ` John Alvord
2001-05-13 23:35 ` Mike A. Harris
2001-05-14 1:03 ` Horst von Brand
2001-05-14 14:31 ` John Kodis
2001-05-14 15:25 ` Michael Meissner
2001-05-14 17:01 ` Alan Cox
2001-05-14 17:16 ` Michael Meissner
2001-05-14 17:29 ` Jesse Pollard
2001-05-14 18:04 ` H. Peter Anvin
2001-05-14 1:31 ` Jonathan Lundell
2001-05-10 23:06 Wayne.Brown
2001-05-10 23:20 ` Hacksaw
2001-05-10 23:52 ` Jonathan Lundell
2001-05-11 0:07 ` Alexander Viro
2001-05-11 2:01 ` Jonathan Lundell
2001-05-11 9:21 ` Malcolm Beattie
2001-05-11 0:10 ` H. Peter Anvin
2001-05-11 1:31 ` David S. Miller
2001-05-11 1:32 ` Blue Lang
2001-05-11 9:31 ` Alan Cox
2001-05-11 12:25 ` Richard B. Johnson
2001-05-11 9:37 ` Alan Cox
2001-05-15 14:01 ` Anuradha Ratnaweera
2001-05-10 21:42 Richard B. Johnson
2001-05-10 22:38 ` H. Peter Anvin
2001-05-11 7:22 ` Tom Leete
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=86256A49.00664FCE.00@smtpnotes.altec.com \
--to=wayne.brown@altec.com \
--cc=hacksaw@hacksaw.org \
--cc=joelja@darkwing.uoregon.edu \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.