GNU bug report logs - #35159
Bug in grep -e (GNU grep 2.51)

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#35159: closed (Bug in grep -e (GNU grep 2.51))
Date: Tue, 09 Apr 2019 18:54:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Tue, 9 Apr 2019 11:53:29 -0700
with message-id <67d2a7d3-175e-1fc2-8cd6-5d7407e65400 <at> cs.ucla.edu>
and subject line Re: bug#35159: Bug in grep -e (GNU grep 2.51)
has caused the debbugs.gnu.org bug report #35159,
regarding Bug in grep -e (GNU grep 2.51)
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
35159: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=35159
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Andrew Browne <andrew.p.browne-nr <at> raytheon.com>
To: "bug-grep <at> gnu.org" <bug-grep <at> gnu.org>
Subject: Bug in grep -e (GNU grep 2.51)
Date: Fri, 5 Apr 2019 13:18:08 +0000

[Message part 3 (text/plain, inline)]

Hi,

I am using GNU grep 2.5.1, so maybe this has been fixed by now.

Bug: 'grep -e <pattern1> -e <pattern2> <file>' sometimes doesn't show all of the matches for one pattern.
Example: 'grep -e blah -e stuff <file>' finds all "blah", but only some of "stuff", when <file> contains lots of "blah" and only a few "stuff" mixed in.

As an alternative that works, I used 'grep -E '<pattern1>|<patter2>' <file>'


Andrew Browne

[Message part 4 (text/html, inline)]

[Message part 5 (message/rfc822, inline)]

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Andrew Browne <andrew.p.browne-nr <at> raytheon.com>
Cc: 35159-done <at> debbugs.gnu.org
Subject: Re: bug#35159: Bug in grep -e (GNU grep 2.51)
Date: Tue, 9 Apr 2019 11:53:29 -0700

On 4/8/19 6:03 AM, Andrew Browne wrote:
> * dummyfile1.txt contains "blah blah blah one two three blah blah blah one two three blah blah blah"
> * dummyfile2.txt contains "blah blah blah one two three blah blah blah one two three"
> * 'grep --color -i -e blah -e two dummyfile1.txt' produces the file with all colored "blah" and none of the "two" are colored.
> * 'grep --color -i -e blah -e two dummyfile2.txt' produces the file with all colored "blah" and only the second "two" is colored. (It seems to like finding <pattern2> on a line only after all of <pattern1> are found on that line.)

I don't observe these symptoms in grep 3.3, the current version. So I
think the bug has been fixed, and am closing the bug report. Thanks
anyway for reporting it. grep 2.5.1 was released in 2004, and it's time
to upgrade for other reasons.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.