I have a feeling I may be treading over old ground here but wouldn't a
simple solution be to simply abandon fast-path for explicit $(shell ...)
invocations? After all, as Kirill says:
> The documentation of the `shell` function pretty directly states that it
will launch the shell, no exceptions, t
On Sun, 2022-10-09 at 13:08 -0400, Kirill Elagin wrote:
> On Sun, Oct 9, 2022 at 11:57 AM wrote:
> > The interpretation of a bad shebang is platform-specific and has no
> > single consistent interpretation.
>
> I am not convinced that platform-specific handling is not practical,
> given that ther
On Sun, Oct 9, 2022 at 11:57 AM wrote:
> The interpretation of a bad shebang is platform-specific and has no single
> consistent interpretation. Some platforms will report EPERM, EACCESS, or
> ENOENT. The error is not necessarily under bash or zsh control but could come
> from exec[vpe] dependi
On October 9, 2022 11:16 AM, Kirill Elagin wrote:
>There is a bit of unexpected behaviour in the `shell` function (due to the
>undocumented fact that it sometimes avoids actually calling the
>shell):
>
>```
>$ cat Makefile
>FOO:=$(shell ./foo.sh)
>
>$ cat foo.sh
>#!/bin/ohno
>echo hi
>
>$ make
>mak
