summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2012-03-04 09:49:27 -0800
committerPaul Eggert <eggert@cs.ucla.edu>2012-03-04 09:50:07 -0800
commit5046bf6ee6d1d33373434db07ba18da4ad293f1a (patch)
treebd55df327657dc4e291f04c140999de4cdaba024
parent43814d248d030849c366e83e550f90a88596461d (diff)
downloadautoconf-5046bf6ee6d1d33373434db07ba18da4ad293f1a.tar.gz
doc: mention PATH bug with "ksh foo"
* doc/autoconf.texi (Invoking the Shell): Mention ksh PATH bug.
-rw-r--r--doc/autoconf.texi16
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index da34a4e8..9442e224 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -15219,6 +15219,22 @@ Bash in Mac OS X 10.2.
@cindex invoking the shell
@cindex shell invocation
+The Korn shell (up to at least version M-12/28/93d) has a bug when
+invoked on a file whose name does not contain a slash. It first
+searches for the file's name in @env{PATH}, and if found it executes
+that rather than the original file. For example, assuming there is a
+binary executable @file{/usr/bin/script} in your @env{PATH}, the last
+command in the following example fails because the Korn shell finds
+@file{/usr/bin/script} and refuses to execute it as a shell script:
+
+@example
+$ @kbd{touch xxyzzyz script}
+$ @kbd{ksh xxyzzyz}
+$ @kbd{ksh ./script}
+$ @kbd{ksh script}
+ksh: script: cannot execute
+@end example
+
Bash 2.03 has a bug when invoked with the @option{-c} option: if the
option-argument ends in backslash-newline, Bash incorrectly reports a
syntax error. The problem does not occur if a character follows the