Date: Tue, 12 Jul 2016 19:36:36 +0200 From: =?iso-8859-1?Q?Dani=EBl?= de Kok <me@danieldk.eu> To: Matthew Seaman <matthew@FreeBSD.org> Cc: freebsd-questions@freebsd.org Subject: Re: grep and anchoring Message-ID: <20160712173623.7fu7orda2gozh2pe@Daniels-MacBook.local> In-Reply-To: <9fc6d5df-108b-5663-5a31-92ca915a9604@FreeBSD.org> References: <20232C89-B821-41EC-9188-C2A19C679BD8@danieldk.eu> <20160626163411.d05f863e.freebsd@edvax.de> <362EE01F-4B49-4ADB-A3A6-43F852FFF87F@danieldk.eu> <9fc6d5df-108b-5663-5a31-92ca915a9604@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 26, 2016 at 04:31:20PM +0100, Matthew Seaman wrote: > You are completely correct -- this is a bug in grep(1) on FreeBSD. In > all current releases including the upcoming 11.0-RELEASE grep is > actually GNU grep version 2.1.5. However, the same bug occurs in > bsdgrep(1): > > % echo 1234 1234 1234 | bsdgrep -o '^....' > 1234 > 123 > 4 12 > > There is already an open PR about a very similar issue: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201650 FWIW, I took some time to look at the bsdgrep issue tonight and have attached a fix to the PR above. With kind regards, Daniël de Kok
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160712173623.7fu7orda2gozh2pe>