Date: Sat, 21 Jan 2017 11:09:18 +0100 From: Stefan Ehmann <shoesoft@gmx.net> To: Kyle Evans <kevans91@ksu.edu> Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org> Subject: Re: unexpected grep -o behavior Message-ID: <d0227ed2-3928-183f-eeff-6c40008f0abf@gmx.net> In-Reply-To: <CACNAnaG5dGSY25nVLucBSbkWW8rJcuFW7%2B_p5akqVMnKm-QKAw@mail.gmail.com> References: <b70e8022-d8f8-24ce-f571-40b07c07c6e1@gmx.net> <CACNAnaG5dGSY25nVLucBSbkWW8rJcuFW7%2B_p5akqVMnKm-QKAw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21.01.2017 07:28, Kyle Evans wrote: > On Sun, Nov 27, 2016 at 2:52 PM, Stefan Ehmann <shoesoft@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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d0227ed2-3928-183f-eeff-6c40008f0abf>