Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

1
  • 1
    Strange that they would use a bash shebang when there's nothing bash-specific in there. That adds an unnecessary dependency to that shell. That means however that one could call egrep as: env 'BASH_FUNC_echo%%=() { :; }' egrep to remove that warning. You could make your replacement script #! /bin/bash - / exec -a "$0" grep -E "$@" for it to mention egrep in its error messages. Commented Dec 8, 2022 at 20:10