bzegrep behaviour not consistent with egrep?
parv at pair.com
Thu Oct 20 17:02:58 PDT 2005
in message <200510201711.49382.jkim at FreeBSD.org>,
wrote Jung-uk Kim thusly...
> On Thursday 20 October 2005 04:57 pm, Parv wrote:
> > in message <20051020194725.GA10376 at ns.museum.rain.com>,
> > wrote James Long thusly...
> > > $ bzegrep "38436|41640" /var/log/maillog.0.bz2 | wc -l
> > > 0
> > > $ bzcat /var/log/maillog.0.bz2 | egrep "38436|41640" | wc -l
> > > 121
> > And more fun, try also "egrep -J| wc", which is similar to the
> > 2d case above.
> Can you elaborate the fun, please?
In short: will you take "bad choice of words" as an explanation?
In somewhat long form: i had read once, twice, or more times in past
(most likely in comp.unix.*) that "egrep" was exactly not same as
"grep -E", and/or "fgrep" not exactly as "grep -F". The OP's
finding reminded me of that even if behaviour difference that was
due to an actual bug.
More information about the freebsd-questions