clarify how custom commands in shebang lines are terminated
This commit is contained in:
parent
87b5e7eaff
commit
940f5defd5
|
@ -163,8 +163,9 @@ Shebang line parsing
|
|||
parsed, the command will be categorized according to the following rules:
|
||||
|
||||
* If the command starts with the definition of a customized command
|
||||
followed by a space character, the customized command will be used.
|
||||
See below for a description of customized commands.
|
||||
followed by a whitespace character (including a newline), the customized
|
||||
command will be used. See below for a description of customized
|
||||
commands.
|
||||
|
||||
* The launcher will define a set of strings which are considered Unix
|
||||
compatible commands to launch Python, such as '/usr/bin/python' etc.
|
||||
|
|
Loading…
Reference in New Issue