Are these new maintainers anyways who are bored and just trying to stir something up, or what?).
#Grep vs.egrep software
IMO software distributions should freeze on what version Grep will ship to one before the dumb warning was added and just start declining any further updates from the maintainers of grep (Keep the old version.
I suppose it's "more optimal" to just call "grep" directly because it avoids running a second shell to build the new "grep" commandĪlso silly to turn it into a shell script. Regular expressions with stray backslashes now cause warnings.Instead of GREP_COLOR='xxx' use GREP_COLORS='mt=xxx' The confusing GREP_COLOR environment variable is now obsolescent.Other notable changes from the release announcement: If you prefer the old names, you can use use your own substitutes, such as a shell script. In the current GNU implementation, egrep and fgrep issue a warning and then act like their modern counterparts eventually, they are planned to be removed entirely. Although breaking up grep into three programs was perhaps useful on the small computers of the 1970s, egrep and fgrep were not standardized by POSIX and are no longer needed. Beginning with GNU Grep 3.8 today, calling these commands will now issue a warning to the user that instead they should use grep -E and grep -F, respectively.Įventually, GNU Grep will drop the egrep / fgrep commands completely but there doesn't seem to be a firm deadline yet for when that removal will happen.ħth Edition Unix had commands egrep and fgrep that were the counterparts of the modern 'grep -E' and 'grep -F'. The egrep and fgrep commands have been deprecated since 2007. The biggest change? "It's now made more clear that if you are still relying on the egrep and fgrep commands, it's past due for switching to just grep with the appropriate command-line arguments."
After 104 commits from six different people, GNU grep was released Saturday, reports Phoronix.
0 kommentar(er)
