"Permission denied" PATH-searching bug

[Hrvoje.Niksic@public.srce.hr (Hrvoje Niksic)]

I do not remember if this problem was reported, but it was present in all
2.6 beta releases of zsh. If you have a directory you may not read in your
PATH, any command not found in search find will be followed by "Permission
denied" error, instead of "Command not found".

Script started on Sat Apr 20 22:37:03 1996
jagor% export PATH=/bin
jagor% ls -a
.           ..          typescript
jagor% something-not-in-path
zsh: command not found: something-not-in-path
jagor% mkdir forbid
jagor% chmod 0 forbid
jagor% PATH=$PATH:forbid
jagor% something-not-in-path
zsh: permission denied: something-not-in-path
jagor% 

script done on Sat Apr 20 22:37:43 1996

Experience has shown that this is extremely confusing to users, equally
newbies and experienced ones (excluding the ones having experience with this
bug:>). People often have a forbidden directory in their path, which means
they get "Permission denied" every time they misspell a command.

-- 
hniksic@srce.hr              |  Student of electrical engineering
hniksic@fly.cc.fer.hr        |  University of Zagreb, Croatia
------------------------------------------------------------------
`VI' - An editor used by those heretics that don't subscribe to
       the Emacs religion.