Jim Meyering writes:
> This would be an envvar for which we do not commit to any level of
> support in future releases.
Would the envvar be documented? Would it be a deprecated feature, with
a removal plan? It seems we traded removing [ef]grep into introducing
new unsupported features which
Paul Eggert via Bug reports for GNU grep writes:
> $ grep '\Q' /dev/null
> grep: warning: stray \ before Q
> $ grep '[:alpha:]' /dev/null
> grep: character class syntax is [[:space:]], not [:space:]
Is the use of diagnostic warnings like this supported by POSIX?
Personally, I'd rather have
Karl Berry writes:
> But, whatever. Since it bothers you to use POSIXLY_CORRECT, let's invent
> some other envvar that turns off the warning, like
> "PLEASE_LET_ME_USE_EFGREP_I_DONT_CARE_ABOUT_POSIX", and Arnold and I
> will set it and life can go on.
>
> https://bugs.gnu.org/49996
>
> I'm
Daniel Forsberg writes:
> Hello fellow Grepers!
>
> the following line:
>
> echo -n ":egov" | sha256sum | grep -E "[0-9a-f]+" -o | xxd -r -p |
> base32 | grep -E "[0-9A-Z]+" -o
>
> produces the following output
>
> LCBSPBBX6BY6
> VZX6P6TZMMRETTCSPXZU7GJTAPPZCPKF2UJEYDA
This is because W is
Hi! A long standing pet issue of mine are the "deprecated" (since
2005?) tools fgrep and egrep. If there is any meaning to the term
"deprecated", maybe they should be dropped at some point, or the
deprecation-status escalated (stderr warning? syslog output?). What do
you think?
Maybe now is an
