Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: trying directories in path one by one



On Wed, Nov 4, 2026 at 3:46 PM Mandar Mitra <mandar.mitra@xxxxxxxxx> wrote:
>
> Mark J. Reed wrote (Wed, Nov 04, 2026 at 08:54:59AM -0500):
> > What do you mean by "fails"? Zsh will execute the first one that is, well,
> > executable. It doesn't run it and then check the exit code and keep looking
> > through the PATH for another one to try. Perhaps you could be very specific
> > about exactly what you are seeing?
>
> Sorry, my bad. What I'm seeing is that if execve (?) fails on the virtualenv pip with a bad interpreter error, then /bin/pip runs. With 2>&1, I see
>
> zsh: ..../junk/bin/pip: bad interpreter: .... /junk/bin/python: no such file or directory
>
> followed by the output from (I'm guessing) /bin/pip.
>
> I'd like things to stop at the bad interpreter error, so that I don't miss it amidst all the other output.
>
> Is this configurable?
>
> Thanks,
> Mandar.
>

This is a bug which was fixed in workers/55076 [1], but there is not
yet a release which has it.

[1] https://www.zsh.org/mla/workers/2026/msg00923.html

-- 
Mikael Magnusson




Messages sorted by: Reverse Date, Date, Thread, Author