spaces in the shebang interpreter path

Configuration Information [Automatically generated, do not change]: Machine: x86_64 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu' -DCONF_VENDOR='redhat'

Re: spaces in the shebang interpreter path

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

Re: spaces in the shebang interpreter path

On Sun, May 11, 2008 at 12:37:12PM -0600, Bob Proulx wrote: Felix Schwarz wrote: I'm not able to specify an interpreter in a shebang line if the path to this interpreter contains spaces. That is correct. It is part of the implementation of the Berkeley #! exec(2) hack and

Re: spaces in the shebang interpreter path

Hi Bob, hi Paul, thanks for your detailed explanations. So I agree that this is not a bash bug ;-) Maybe in ten years we will see a Un*x release which will allow the use of spaces in the shebang line *dreaming*. thanks again fs smime.p7s Description: S/MIME Cryptographic Signature