doc: Clarify why multiple arguments are not supported in shebang line
It's not a limitation of `/usr/bin/env`, it's just how the OS processes shebang lines (see http://stackoverflow.com/a/4304187)
This commit is contained in:
		
							parent
							
								
									607d91517e
								
							
						
					
					
						commit
						36b9ce24b1
					
				
					 1 changed files with 2 additions and 2 deletions
				
			
		|  | @ -252,8 +252,8 @@ dependencies in Nixpkgs.</para> | ||||||
| <para>The lines starting with <literal>#! nix-shell</literal> specify | <para>The lines starting with <literal>#! nix-shell</literal> specify | ||||||
| <command>nix-shell</command> options (see above). Note that you cannot | <command>nix-shell</command> options (see above). Note that you cannot | ||||||
| write <literal>#1 /usr/bin/env nix-shell -i ...</literal> because | write <literal>#1 /usr/bin/env nix-shell -i ...</literal> because | ||||||
| <command>/usr/bin/env</command> does not support passing options to | many operating systems only allow one argument in | ||||||
| the interpreter.</para> | <literal>#!</literal> lines.</para> | ||||||
| 
 | 
 | ||||||
| <para>For example, here is a Python script that depends on Python and | <para>For example, here is a Python script that depends on Python and | ||||||
| the <literal>prettytable</literal> package: | the <literal>prettytable</literal> package: | ||||||
|  |  | ||||||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue