* doc/autoconf.texi (Limitations of Builtins) <.>: Mention bash bug.

Signed-off-by: Eric Blake <ebb9@byu.net>

diff --git a/ChangeLog b/ChangeLog
index 42da03c4c0d7d3fc4d7c7d9a32aaf02cf12f0622..8d592df47a567fa70b6d0c9bf7f801fe6cd6463f 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2008-01-29  Eric Blake  <ebb9@byu.net>
+
+       * doc/autoconf.texi (Limitations of Builtins) <.>: Mention bash
+       bug.
+
 2008-01-28  Eric Blake  <ebb9@byu.net>
 
        Fix regression in handling VAR=VALUE arguments to testsuite.

diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index f6421d7a28f674dee640811197536c62ec71900b..9c5b1920da37d70823347f0818b3ba60218c1821 100644 (file)
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -13598,10 +13598,12 @@ the @samp{x} into account later in the pipe.
 @c --------------
 @prindex @command{.}
 Use @command{.} only with regular files (use @samp{test -f}).  Bash
-2.03, for instance, chokes on @samp{. /dev/null}.  Also, remember that
-@command{.} uses @env{PATH} if its argument contains no slashes, so if
-you want to use @command{.} on a file @file{foo} in the current
-directory, you must use @samp{. ./foo}.
+2.03, for instance, chokes on @samp{. /dev/null}.  Remember that
+@command{.} uses @env{PATH} if its argument contains no slashes.  Also,
+some shells, including bash 3.2, implicitly append the current directory
+to this @env{PATH} search, even though Posix forbids it.  So if you want
+to use @command{.} on a file @file{foo} in the current directory, you
+must use @samp{. ./foo}.
 
 @item @command{!}
 @c --------------