unexpected grep -o behavior
Stefan Ehmann
shoesoft at gmx.net
Sat Jan 21 10:09:32 UTC 2017
On 21.01.2017 07:28, Kyle Evans wrote:
> On Sun, Nov 27, 2016 at 2:52 PM, Stefan Ehmann <shoesoft at gmx.net> wrote:
>> Bug 195763 looks related, but I'm not sure it's the same issue.
>
> Hi,
>
> FYI- that bug is only tangentially related, but I've updated my patch
> to also address it while I'm in the neighborhood of where this problem
> was. See Comment #5 if you're interested in a more detailed
> explanation.
Thanks a lot for taking care of this bug.
bsdgrep now works for my testcase.
As a side note:
On 11.0-RELEASE (GNU) grep in base suffers the same bug. I tried version
2.20 on Debian which works correctly. But I assume it won't get updated
due to GPLv3.
Makes me wonder if we still need two grep variants in base.
More information about the freebsd-stable
mailing list