From: Noah Friedman <noah@splode.com>
To: 66582@debbugs.gnu.org
Subject: bug#66582: annoying, needless warning messages from [fe]grep
Date: Mon, 16 Oct 2023 17:44:39 -0700 (PDT) [thread overview]
Message-ID: <20231016174439.415263.FMU1197@unexploded-cow.prv.splode.com> (raw)
Just because a program is considered deprecated or obsolete by a standards
committee, is no reason to actually force that program out of use or
availablity. And since when does GNU adhere strictly to POSIX anyway?
So my bug report is this: fgrep and egrep should not emit any warning on
stderr about being obsolescent unless the environment POSIXLY_CORRECT is
set. If you want to be *really* pedantic, it shouldn't emit a warning
unless POSIXLY_CORRECT is set to the specific standards level (or above) in
which it was declared obsolete. :-P
Because goddammit, there are 40 years worth of old programs out there that
are going to keep using egrep, and as a crusty 50+ year old myself, I'm not
planning to train my fingers out of using it either.
Just let some things *be*.
next reply other threads:[~2023-10-17 0:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 0:44 Noah Friedman [this message]
2023-10-17 3:28 ` bug#66582: annoying, needless warning messages from [fe]grep Sam James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-coreutils
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231016174439.415263.FMU1197@unexploded-cow.prv.splode.com \
--to=noah@splode.com \
--cc=66582@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).