Re: spaces in the shebang interpreter path

[Paul Jarc]

Felix Schwarz <[EMAIL PROTECTED]> wrote:
>         I'm not able to specify an interpreter in a shebang line if the path
>         to this interpreter contains spaces.

It's actually the kernel that interprets that line, not bash.  The
historical behavior is that space separates the interpreter from an
optional argument, and there is no escape mechanism, so there's no way
to specify an interpreter with a space in the path.  It's unlikely
that this would ever change, since that would break existing scripts
that rely on thecurrent behavior.


paul