(Changes to grep) Time To Stop Using egrep and fgrep Commands, Per GNU grep 3.8
1–10 of 27 posts
Re: (Changes to grep) Time To Stop Using egrep and fgrep Commands, Per GNU grep 3.8
#2I feel like this is a pretty silly thing to deprecate. What is the harm in keeping around egrep and fgrep?
Re: (Changes to grep) Time To Stop Using egrep and fgrep Commands, Per GNU grep 3.8
#3I'm shocked - neither egrep nor fgrep are POSIX standards!
I had every expectation that they would be.
https://pubs.opengroup.org/onlinepubs/9699919799/utilities/g...
Re: (Changes to grep) Time To Stop Using egrep and fgrep Commands, Per GNU grep 3.8
#4What's the rational for keeping them around in new installs?
How have others handled command deprecation on the past?
May this also serve as a warning about adding functionality and being very careful about removing it.
Re: (Changes to grep) Time To Stop Using egrep and fgrep Commands, Per GNU grep 3.8
#5I feel like this is a pretty silly thing to deprecate. What is the harm in keeping around egrep and fgrep?
On their own it's probably trivial. I suspect over time it becomes a large tasks/maintenance question.
Depending on the number of additional commands on similar removal paths it may have performance/memory improvement implications for minimum supported specs.
Re: (Changes to grep) Time To Stop Using egrep and fgrep Commands, Per GNU grep 3.8
#6I feel like this is a pretty silly thing to deprecate. What is the harm in keeping around egrep and fgrep?
On their own it's probably trivial. I suspect over time it becomes a large tasks/maintenance question. Depending on the number of additional commands on similar removal paths it may have performance/memory improvement implications for minimum supported specs.
Does it though? I mean we’re really talking about a teeny tiny little startup code to read arg0 and use it to do the equivalent of passing -E or -P.
Re: (Changes to grep) Time To Stop Using egrep and fgrep Commands, Per GNU grep 3.8
#7What does "$@@" do? I have used just "$@" for what the script at the end is trying to accomplish, is there some edge case where that fails?
Re: (Changes to grep) Time To Stop Using egrep and fgrep Commands, Per GNU grep 3.8
#8The main addendum is that fgrep without a file list is -F, and egrep is -E.
Re: (Changes to grep) Time To Stop Using egrep and fgrep Commands, Per GNU grep 3.8
#9What does "$@@" do? I have used just "$@" for what the script at the end is trying to accomplish, is there some edge case where that fails?
I think that's just the markup for a single @-sign.
Re: (Changes to grep) Time To Stop Using egrep and fgrep Commands, Per GNU grep 3.8
#10I feel like this is a pretty silly thing to deprecate. What is the harm in keeping around egrep and fgrep?
On their own it's probably trivial. I suspect over time it becomes a large tasks/maintenance question. Depending on the number of additional commands on similar removal paths it may have performance/memory improvement implications for minimum supported specs.
I don't think that's why, on my Arch Linux box they're just shell scripts that pass the -E/-F argument to regular Grep.
$ cat /usr/bin/egrep
#!/bin/sh
exec grep -E "$@"
$ cat /usr/bin/fgrep
#!/bin/sh
exec grep -F "$@"