bug#57604: [ef]grep usage -> POSIXLY_CORRECT?

2022-09-07 Thread arnold
I totally agree here with Karl, obsoleting fgrep and egrep is the wrong way to go. It's built into too many scripts world-wide, as well as burned into the "finger ROMs" of too many users. Not to mention all the books / training materials that talk about them that people may have. Thanks, Arnold

bug#57604: [ef]grep usage -> POSIXLY_CORRECT?

2022-09-07 Thread Simon Josefsson via Bug reports for GNU grep
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 un

bug#57604: [ef]grep usage -> POSIXLY_CORRECT?

2022-09-07 Thread Simon Josefsson via Bug reports for GNU grep
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 tools

bug#57604: [ef]grep usage -> POSIXLY_CORRECT?

2022-09-07 Thread Gary Johnson
On 2022-09-07, Simon Josefsson via Bug reports for GNU grep wrote: > On the other hand, it seems your main problem here is the warning: and I > agree that is annoying and should be fixed. There doesn't seem to be > any way to disable it now? It would be nice to fix that. > > I think the simples

bug#57604: [ef]grep usage -> POSIXLY_CORRECT?

2022-09-07 Thread Gary Johnson
On 2022-09-07, Simon Josefsson via Bug reports for GNU grep wrote: > Personally, I'd rather have tools exit with an error code on invalid > uses rather than issuing warning messages. The warning messages are merely annoying. Returning a non-zero exit status would break scripts, and in many cases

bug#57604: [ef]grep usage -> POSIXLY_CORRECT?

2022-09-07 Thread Paul Eggert via Bug reports for GNU grep
On 9/7/22 03:02, Simon Josefsson via Bug reports for GNU grep wrote: $ 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? Yes, POSIX says tha

bug#57604: [ef]grep usage -> POSIXLY_CORRECT?

2022-09-07 Thread Karl Berry
sj> Personally, I'd rather have tools exit with an error code on invalid uses rather than issuing warning messages. For me (and according to historical practice), an unnecessary \ is not invalid. So, not surprisingly, I, on the other hand, would rather have grep provide a way to turn off t

bug#57604: [ef]grep usage -> POSIXLY_CORRECT?

2022-09-07 Thread Karl Berry
[ef]grep I guess my basic issue is that I don't understand the benefit of the new warning. It causes a lot of trouble. What is the countervailing positive benefit? $ grep '\Q' /dev/null grep: warning: stray \ before Q It would be nice to be able to turn those off too. (It hit me to

bug#57604: [ef]grep usage -> POSIXLY_CORRECT?

2022-09-07 Thread Karl Berry
simpler solution to undeprecate the tools in documentation and have them be official GNU-enhancements as they de-facto has been for the past 20+ years +20 My pet issue was the inconsistency between documentation and reality, Agreed. I think the simplest way to fix that is t