aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTim Cuthbertson <tim@gfxmonk.net>2015-12-06 10:39:25 +1100
committerEelco Dolstra <eelco.dolstra@logicblox.com>2016-01-05 13:46:05 +0100
commit36b9ce24b11a87b3e71f4f4fec9f3e5ad6af7b95 (patch)
tree42fa6008824312c4dd251d1882ae7a70101f1462
parent607d91517e3b36837d4a0a9df3e3d7890f394169 (diff)
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)
-rw-r--r--doc/manual/command-ref/nix-shell.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/manual/command-ref/nix-shell.xml b/doc/manual/command-ref/nix-shell.xml
index 9e3e6d188..a13d9d7c1 100644
--- a/doc/manual/command-ref/nix-shell.xml
+++ b/doc/manual/command-ref/nix-shell.xml
@@ -252,8 +252,8 @@ dependencies in Nixpkgs.</para>
<para>The lines starting with <literal>#! nix-shell</literal> specify
<command>nix-shell</command> options (see above). Note that you cannot
write <literal>#1 /usr/bin/env nix-shell -i ...</literal> because
-<command>/usr/bin/env</command> does not support passing options to
-the interpreter.</para>
+many operating systems only allow one argument in
+<literal>#!</literal> lines.</para>
<para>For example, here is a Python script that depends on Python and
the <literal>prettytable</literal> package: