Hello;
Aidan Gauland writes:
> I can not reproduce this on my system (Debian 7.1 x86_64). Which OS are
> you running?
I originally stumbled upon the problem running 24.3 on FreeBSD 9. I also
tested on a couple of GNU/Linux systems and things worked as expected,
but the problem exists on OS X.
[using the right bug address, this time]
On Mon, Sep 23, 2013 at 11:26 AM, Aharon Robbins wrote:
> Hi.
>
>> $ printf '\x82\n' > in; ./grep -q '\S' in && echo match
>> match
>>
>> Now, require a back-reference (forcing switch from grep's DFA matcher
>> to use of the regex functions), and y
On Mon, Sep 23, 2013 at 6:34 AM, Jaroslav Skarvada wrote:
> printf
> '1234x\n'
> | grep 1234 --color=always
Thank you for the report.
I confirm that setting GREP_COLORS=ne is a work-around. Does that
have unwel
On Mon, Sep 23, 2013 at 6:26 AM, Stefano Lattarini
wrote:
> Hi Jim.
>
> On 09/23/2013 06:18 AM, Jim Meyering wrote:
>>
>> Here's a test for the original problem, which is also fixed by the
>> preceding patch:
>>
>> ...
>
>>
>>
>> +grep '^\S$' in > out-S && fail=1
>
>> +compare /dev/null out-S || e
Reproducer:
$ printf
'1234x\n'
| grep 1234 --color=always
123x
This can be reproduced at least on xterm and linux console,
but i
Hi Jim.
On 09/23/2013 06:18 AM, Jim Meyering wrote:
Here's a test for the original problem, which is also fixed by the
preceding patch:
...
>
+grep '^\S$' in > out-S && fail=1
> +compare /dev/null out-S || exit=1
>
Shouldn't this be "|| fail=1"?
> +grep '^\s$' in > out-s && fail=1
> +compar
