Re: unexpected grep -o behavior

2017-01-21 Thread Stefan Ehmann
On 21.01.2017 07:28, Kyle Evans wrote: On Sun, Nov 27, 2016 at 2:52 PM, Stefan Ehmann 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 thi

Re: unexpected grep -o behavior

2017-01-20 Thread Kyle Evans
On Sun, Nov 27, 2016 at 2:52 PM, Stefan Ehmann 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

unexpected grep -o behavior

2016-11-27 Thread Stefan Ehmann
When I try to match the first character of a line grep also matches all subsequent characters: $ echo 123 | grep -o '^.' 1 2 3 Same with bsdgrep. grep from ports works as expected: $ echo 123 | /usr/local/bin/grep -o '^.' 1 Tested on 11.0. Bug 195763 looks related, but I'm not sure it's the sa