Re: more doc syncs

[Eric Blake]

Eric Blake <ebb9 <at> byu.net> writes:

> 
> This gets another couple of nodes ported to head, and fixes an
> undocumented option.

And was wrong in its description of -o.  Checking in this followup (the Dumpdef 
node was already correct).

2006-08-16  Eric Blake  <address@hidden>

        * doc/m4.texinfo (Invoking m4, Debug Output): Fix wording to be
        clear that dumpdef does not always go to stderr.

Index: doc/m4.texinfo
===================================================================
RCS file: /sources/m4/m4/doc/m4.texinfo,v
retrieving revision 1.1.1.1.2.66
diff -u -r1.1.1.1.2.66 m4.texinfo
--- doc/m4.texinfo      15 Aug 2006 13:51:47 -0000      1.1.1.1.2.66
+++ doc/m4.texinfo      16 Aug 2006 14:41:50 -0000
@@ -567,10 +567,11 @@
 
 @item -o @var{FILE}
 @itemx address@hidden
-Redirect debug and trace output to the named @var{FILE}.  Warnings,
-error messages, and the output of @code{errprint} and @code{dumpdef},
-are still printed to standard error.  @xref{Debug Output}, for more
-details.
+Redirect @code{dumpdef} output, debug messages, and trace output to the
+named @var{FILE}.  Warnings, error messages, and @code{errprint} output
+are still printed to standard error.  If unspecified, debug output goes
+to standard error; if empty, debug output is discarded.  @xref{Debug
+Output}, for more details.
 
 @item -t @var{NAME}
 @itemx address@hidden
@@ -2235,7 +2236,8 @@
 Sends all further debug and trace output to @var{file}.  If
 @var{file} is empty, debug and trace output are discarded.  If
 @code{debugfile} is called without any arguments, debug and trace output
-are sent to standard error.  This does not affect warnings, which are
+are sent to standard error.  This does not affect warnings, error
+messages, or @code{errprint} output, which are
 always sent to standard error.  If @var{file} cannot be opened, the
 current debug file is unchanged.