Re: invalid node names in Autoconf manual

[Paul Eggert]

Ralf Wildenhues <address@hidden> writes:

> IMVHO emacs giving problems is less a problem than URL stability: Info
> mode could be fixed.

You're going where _Karl_ fears to tread?  You're a brave man....

> Paul, can we please revert this change in Autoconf?

OK, I installed the following.  It doesn't undo all the change (I like
some of the change regardless, as it's better to avoid cryptic
abbreviations in node names) but it does undo the ones I found
troublesome, in particular the config.status invocation node.

2006-12-12  Paul Eggert  <address@hidden>

        * doc/autoconf.texi: Undo some of the 2006-12-10 change.  It was
        too drastic, even if Texinfo in theory requires it for info mode.

        (config.status Invocation): Renamed back from Recreating a
        Configuration).
        (Obsolete config.status Use): Renamed back from Obsolete Recreation.
        (Autoconf 2.13): Renamed back from 20th-century Autoconf 2.

--- autoconf.texi.~1.1117~      2006-12-10 23:12:07.000000000 -0800
+++ autoconf.texi       2006-12-12 09:48:13.000000000 -0800
@@ -224,7 +224,7 @@ published by the Free Software Foundatio
 * configure: (autoconf)configure Invocation.    Configuring a package.
 * autoupdate: (autoconf)autoupdate Invocation.
                                 Automatic update of @file{configure.ac}
-* config.status: (autoconf)Recreating a Configuration. Recreating 
configurations.
+* config.status: (autoconf)config.status Invocation. Recreating configurations.
 * testsuite: (autoconf)testsuite Invocation.    Running an Autotest test suite.
 @end direntry
 
@@ -267,7 +267,7 @@ published by the Free Software Foundatio
 * Manual Configuration::        Selecting features that can't be guessed
 * Site Configuration::          Local defaults for @command{configure}
 * Running configure Scripts::   How to use the Autoconf output
-* Recreating a Configuration::  Invoking @command{config.status}
+* config.status Invocation::    Recreating a configuration
 * Obsolete Constructs::         Kept for backward compatibility
 * Using Autotest::              Creating portable test suites
 * FAQ::                         Frequent Autoconf Questions, with answers
@@ -553,12 +553,12 @@ Running @command{configure} Scripts
 
 Obsolete Constructs
 
-* Obsolete Recreation::         Obsolete convention for @command{config.status}
+* Obsolete config.status Use::  Obsolete convention for @command{config.status}
 * acconfig Header::             Additional entries in @file{config.h.in}
 * autoupdate Invocation::       Automatic update of @file{configure.ac}
 * Obsolete Macros::             Backward compatibility macros
 * Autoconf 1::                  Tips for upgrading your files
-* 20th-century Autoconf 2::     Some fresher tips
+* Autoconf 2.13::               Some fresher tips
 
 Upgrading From Version 1
 
@@ -912,7 +912,7 @@ containing @code{#define} directives (@p
 
 @item
 a shell script called @file{config.status} that, when run, recreates
-the files listed above (@pxref{Recreating a Configuration});
+the files listed above (@pxref{config.status Invocation});
 
 @item
 an optional shell script normally called @file{config.cache}
@@ -2037,7 +2037,7 @@ The special value @samp{-} might be used
 when used in @var{output}, or the standard input when used in the
 @var{inputs}.  You most probably don't need to use this in
 @file{configure.ac}, but it is convenient when using the command line
-interface of @file{./config.status}, see @ref{Recreating a Configuration},
+interface of @file{./config.status}, see @ref{config.status Invocation},
 for more details.
 
 The @var{inputs} may be absolute or relative file names.  In the latter
@@ -2883,7 +2883,7 @@ AC_CONFIG_FILES([stamp-h], [echo timesta
 so @file{config.status} ensures that @file{config.h} is considered up to
 date.  @xref{Output}, for more information about @code{AC_OUTPUT}.
 
address@hidden a Configuration}, for more examples of handling
address@hidden Invocation}, for more examples of handling
 configuration-related dependencies.
 
 @node Configuration Headers
@@ -8400,7 +8400,7 @@ dangerous.  If for instance the user run
 files depend upon @command{bizarre-cc} being the C compiler.  If
 for some reason the user runs @command{./configure} again, or if it is
 run via @samp{./config.status --recheck}, (@xref{Automatic Remaking},
-and @pxref{Recreating a Configuration}), then the configuration can be
+and @pxref{config.status Invocation}), then the configuration can be
 inconsistent, composed of results depending upon two different
 compilers.
 
@@ -8452,7 +8452,7 @@ and similarly if the variable is unset, 
 
 @item
 @var{variable} is kept during automatic reconfiguration
-(@pxref{Recreating a Configuration}) as if it had been passed as a command
+(@pxref{config.status Invocation}) as if it had been passed as a command
 line argument, including when no cache is used:
 
 @example
@@ -16028,10 +16028,10 @@ may use comes with Autoconf.
 @include install.texi
 
 
address@hidden ============================================== Recreating a 
Configuration
address@hidden ============================================== config.status 
Invocation
 
address@hidden Recreating a Configuration
address@hidden Recreating a Configuration
address@hidden config.status Invocation
address@hidden config.status Invocation
 @cindex @command{config.status}
 
 The @command{configure} script creates a file named @file{config.status},
@@ -16155,7 +16155,7 @@ Makefile: Makefile.in config.status
 @end example
 
 The calling convention of @file{config.status} has changed; see
address@hidden Recreation}, for details.
address@hidden config.status Use}, for details.
 
 
 @c =================================================== Obsolete Constructs
@@ -16174,19 +16174,19 @@ intention is mainly to help maintainers 
 understanding how to move to more modern constructs.
 
 @menu
-* Obsolete Recreation::         Obsolete convention for @command{config.status}
+* Obsolete config.status Use::  Obsolete convention for @command{config.status}
 * acconfig Header::             Additional entries in @file{config.h.in}
 * autoupdate Invocation::       Automatic update of @file{configure.ac}
 * Obsolete Macros::             Backward compatibility macros
 * Autoconf 1::                  Tips for upgrading your files
-* 20th-century Autoconf 2::     Some fresher tips
+* Autoconf 2.13::               Some fresher tips
 @end menu
 
address@hidden Obsolete Recreation
address@hidden Obsolete config.status Use
 @section Obsolete @file{config.status} Invocation
 
 @file{config.status} now supports arguments to specify the files to
-instantiate; see @ref{Recreating a Configuration}, for more details.
+instantiate; see @ref{config.status Invocation}, for more details.
 Before, environment variables had to be used.
 
 @defvar CONFIG_COMMANDS
@@ -16217,7 +16217,7 @@ The symbolic links to establish.  The de
 @file{config.status} ignores this variable.
 @end defvar
 
-In @ref{Recreating a Configuration}, using this old interface, the example
+In @ref{config.status Invocation}, using this old interface, the example
 would be:
 
 @example
@@ -17447,7 +17447,7 @@ See whether any of your tests are of gen
 encapsulate them into macros that you can share.
 
 
address@hidden 20th-century Autoconf 2
address@hidden Autoconf 2.13
 @section Upgrading From Version 2.13
 @cindex Upgrading autoconf
 @cindex Autoconf upgrading