mirror/autoconf
2
0
Fork 0
mirror of git://git.sv.gnu.org/autoconf synced 2025-03-13 14:36:50 +08:00
Code Issues Packages Projects Releases Wiki Activity

* doc/autoconf.texi (Shellology, Special Shell Variables): Document that the Zsh

Browse Source 
problem with NULLCMD was fixed in zsh 3.1.6-dev-18.
This commit is contained in:
Paul Eggert 2004-10-11 21:42:05 +00:00
parent 0952c34e3c
commit 9bf04c6b54
2 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ChangeLog
View File

@ -4,6 +4,10 @@
to "POSIX" or "@acronym{POSIX}"), and similarly for "DOS
variants", "Unix", and some related minor wording fixups.
(Shellology, Special Shell Variables): Document that the Zsh
problem with NULLCMD was fixed in zsh 3.1.6-dev-18. Thanks
to Alexandre Duret-Lutz for this info.
2004-10-10 Alexandre Duret-Lutz <adl@gnu.org>
* doc/autoconf.texi (One-Shot Macros): New node.

10
doc/autoconf.texi
View File

@ -9542,7 +9542,8 @@ Substitutions}).
@cindex Zsh
To detect whether you are running @command{zsh}, test whether
@code{ZSH_VERSION} is set. By default @command{zsh} is @emph{not}
compatible with the Bourne shell: you have to run @samp{emulate sh} and
compatible with the Bourne shell: you must execute @samp{emulate sh},
and for @command{zsh} versions before 3.1.6-dev-18 you must also
set @code{NULLCMD} to @samp{:}. @xref{Compatibility,, Compatibility,
zsh, The Z Shell Manual}, for details.
@ -10431,9 +10432,10 @@ $ @kbd{sed '=' <lineno |}
@item NULLCMD
@evindex NULLCMD
When executing the command @samp{>foo}, @command{zsh} executes
@samp{$NULLCMD >foo}. The Bourne shell considers @code{NULLCMD} to be
@samp{:}, while @command{zsh}, even in Bourne shell compatibility mode,
sets @code{NULLCMD} to @samp{cat}. If you forgot to set @code{NULLCMD},
@samp{$NULLCMD >foo} unless it is operating in Bourne shell
compatibility mode and the @command{zsh} version is newer
than 3.1.6-dev-18. If are using an older @command{zsh}
and forget to set @code{NULLCMD},
your script might be suspended waiting for data on its standard input.
@item ENV