Re: grep command or operator
- From: Jakov Sosic <jsosic@xxxxxxxxxxxxxxxxxxx>
- Date: Mon, 30 Mar 2009 20:48:38 +0200
On 2009-03-30, guzzijason <jasonwtucker@xxxxxxxxx> wrote:
I'm sorry I was to busy to think out my response in a way that didn't
upset you. Yes... I'm *well* aware of the significance of the "e" in
"egrep". My point was, that instead of using '/usr/xpg4/bin/grep',
which can handle regex - but in my experience has not always been
available, depending on how the system was built - I simply tend to
use 'egrep' instead. I guess that in my haste, I didn't make that
clear. Or I didn't think it mattered. Probably the latter. :-)
You sounded like you were surprised by the better handling of regexpes
with egrep, so I just wanted to point that egrep was in fact grep with
support for regular expressions ;)
--
| Jakov Sosic | ICQ: 28410271 | PGP: 0x965CAE2D |
=================================================================
| start fighting cancer -> http://www.worldcommunitygrid.org/ |
.
- Follow-Ups:
- Re: grep command or operator
- From: suru
- Re: grep command or operator
- References:
- grep command or operator
- From: suru
- Re: grep command or operator
- From: guzzijason
- Re: grep command or operator
- From: Jakov Sosic
- Re: grep command or operator
- From: guzzijason
- grep command or operator
- Prev by Date: Re: How to configure the monitor?
- Next by Date: Identifying number of cores/CPU's from a system domain on T2000
- Previous by thread: Re: grep command or operator
- Next by thread: Re: grep command or operator
- Index(es):
Relevant Pages
|