On 8/16/21 4:32 AM, Jim Meyering wrote:
* src/egrep.sh: Issue a obsolescence warning.
s/a/an/
Thanks, I fixed that and installed the result with a bug# in the commit
message. Closing the bug report.
On Sun, Aug 15, 2021 at 8:11 PM Paul Eggert wrote:
>
> On 8/15/21 7:25 AM, arn...@skeeve.com wrote:
> > I'm willing to bet that the majority of grep/egrep/fgrep invocations
> > come from the command line rather than from scripts.
>
> That's not true for me, as I almost always invoke 'grep' via a
On 8/15/21 7:25 AM, arn...@skeeve.com wrote:
I'm willing to bet that the majority of grep/egrep/fgrep invocations
come from the command line rather than from scripts.
That's not true for me, as I almost always invoke 'grep' via a script or
shell function or Emacs. And I'm skeptical that it's
Jim Meyering wrote:
> IMHO, they must be removed.
> Anyone who requires to be able to use "egrep" or "fgrep" from the
> command line can use a function or alias. Given their lack of
> standardization, those should not be used in scripts.
I beg to differ. Scripts is one thing. But breaking 40+
On Wed, Aug 11, 2021 at 9:35 AM Paul Eggert wrote:
> On 8/11/21 12:22 AM, Simon Josefsson via Bug reports for GNU grep wrote:
> > I think the main reason for deprecating
> > them was that POSIX dropped a requirement for them?
>
> As I recall, it was because they were kinda useless cruft. Portable
On 8/11/21 12:22 AM, Simon Josefsson via Bug reports for GNU grep wrote:
I think the main reason for deprecating
them was that POSIX dropped a requirement for them?
As I recall, it was because they were kinda useless cruft. Portable
scripts can't use egrep and fgrep since they're not
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
