Thanks for your report. However, I'm not sure it is a bug.
El 19/05/17 a las 22:04, john mullee escribió:
> Package: grep
> Version: 2.20-4.1
>
> cat /bin/egrep
> #!/bin/sh
> exec grep -E "$@"
>
> should replace with
>
> exec /bin/grep -E "$@"
>
> to reproduce:
>
> root@debian-512mb-fra1-01:/opt/firewall# bash
> root@debian-512mb-fra1-01:/opt/firewall# PATH=/usr/local egrep "any" /etc/*
> bash: egrep: command not found
>
I am afraid the behaviour of that command is not what you meant. You
shell was looking for egrep at your modified path, it was not even able
to read egrep's content. Try this:
PATH=/usr/local grep a /etc/*
zsh: command not found: grep
PATH=/usr/local /usr/bin/which grep
(empty)
Or even:
PATH=/usr/local ls
zsh: command not found: ls
Note also that the use of egrep, fgrep and rgrep variants is deprecated.
You should use -E, -F or -r instead.
Cheers,
Santiago
P.S. I will close this bug "soon" unless you are able to argue why it is
actually a bug.
