Re: Why sh-set-shell insert a space after #!

[Thierry Volpiatto]

Leo <address@hidden> writes:

> On 2012-08-17 15:18 +0800, Stephen J. Turnbull wrote:
>> IIRC, POSIX allows but doesn't require the space.  However, some
>> historical mostly-compatible shells had problems if there was no
>> space.  Since it never hurts with fully conforming shells, and
>> sometimes helps, it's a definite portability win.  (AFAIK there was no
>> particular correlation between this kind of non-conformance and other,
>> more important, non-conformance.)
>
> From my reading of the two links, separation #! and the path with a
> space is abnormal and evidenced by all scripts I can find. So I think
> the better default for executable-prefix is "#!", not "#! ".
Agree, also in all books, manuals I found , it is described like "#!/bin/bash"
and never "#! /bin/bash", same for python.

-- 
  Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997