autoconf-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Possible zsh contention in pdfroff (Re: [autoconf] ensure a VPATH bu


From: Ralf Wildenhues
Subject: Re: Possible zsh contention in pdfroff (Re: [autoconf] ensure a VPATH build)
Date: Tue, 14 Mar 2006 08:19:36 +0100
User-agent: Mutt/1.5.11

To finish at least this one part of the discussion:

* Keith MARSHALL wrote on Tue, Feb 21, 2006 at 02:49:12PM CET:
> 
> BTW Ralf, I notice a typo in the above autoconf.info snippet: under the
> `NULLCMD' heading, `If are using an older...' should read `If you are...',
> i.e. the word `you' is missing.

I have applied the patch below.

Cheers,
Ralf

        * doc/autoconf.texi (Special Shell Variables): Missing word.
        Reported by Keith Marshall <address@hidden>.

Index: doc/autoconf.texi
===================================================================
RCS file: /cvsroot/autoconf/autoconf/doc/autoconf.texi,v
retrieving revision 1.963
diff -u -r1.963 autoconf.texi
--- doc/autoconf.texi   12 Mar 2006 19:58:31 -0000      1.963
+++ doc/autoconf.texi   13 Mar 2006 22:43:55 -0000
@@ -11298,7 +11298,7 @@
 When executing the command @samp{>foo}, @command{zsh} executes
 @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}
+than 3.1.6-dev-18.  If you are using an older @command{zsh}
 and forget to set @env{NULLCMD},
 your script might be suspended waiting for data on its standard input.
 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]