bug with grep 3.0.2 in cygwin 3.0.7
Fri Aug 30 07:48:00 GMT 2019
On 2019-08-29 19:42, Eliot Moss wrote:
> On 8/29/2019 3:08 PM, Andrey Repin wrote:
>>> I encounter some problem with grep option -E on cygwin 3.0.7
>>> echo "a^b" | grep "a^b" #answer a^b ie it's OK
>>> echo "a^b" | grep -E "a^b" #answer nothing " for me it's KO
>> That's an expected result of an impossible constraint.
>>> I have to backslash ^ to be OK like : grep -E 'a\^b'
>>> Is-it a bug ?
>>> I don't know if all versions of cygwin and grep are concerned.
>> RTFM, this is regexp basics.
> There was a really great answer to this earlier.Â I tried an
> answer, but was wrong.Â One has to read the "fine print" really
> carefully.Â At first I thought it was a bug, at least in the
> documentation, but the meaning of a^b, when ^ is the metacharacter,
> is kind of subtle (IMO at least).Â It's easy to miss that
> subtlety and think that if ^ is not at the beginning of an
> expression it will be treated as an ordinary character ...
> But my main point is that RTM would be enough; RTFM seemed
> to me perhaps a little more rude than necessary.
https://cygwin.com/acronyms/#RTFM exists and has been amusing rather than rude
in our industry for decades, especially in non-native English locales e.g. here
in this list: "Read The Fine Manual"; but RTM for software products is usually
"Release To Manufacturing", from the days when media was produced!
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin