[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#35159: Bug in grep -e (GNU grep 2.51)
|
From: |
Paul Eggert |
|
Subject: |
bug#35159: Bug in grep -e (GNU grep 2.51) |
|
Date: |
Tue, 9 Apr 2019 11:53:29 -0700 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 |
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.