Re: Rebuild menus in the manual.

[Bob Friesenhahn]

On Sun, 14 Nov 2010, Ralf Wildenhues wrote:

> I would like to push this patch that has emacs-rebuilt menus.
> They actually typeset a bit worse than the hand-written ones
> (see e.g. the last hunk) but I think that doing something
> automatically is better than doing it manually, and if there
> is pain involved then we should consider trying to shorten the
> names of the nodes in question.  (If we do, we need to remember
> to add entries to html_node/.symlinks in the web cvs, so the old
> URLs remain valid.)
>
> Opinions?

Automatically is definitely better and so I am in favor of this patch. 
When considering shortening the names, it is good to consider that the 
terms "Native MinGW", "Cygwin/Windows", and "Unix/Windows" are really 
not very meaningful.  For example, if we are talking about Wine we 
should probably just call it "Wine" and describe what Wine is for 
people who are not aware of it.

Bob

> Thanks,
> Ralf
>
>    Rebuild menus in the manual.
>
>    * doc/automake.texi: Rebuild menus (using ^C ^U ^A in emacs).
>    Thanks to Ian Lance Taylor for the suggestion.
>
> diff --git a/doc/libtool.texi b/doc/libtool.texi
> index 5c2570d..12d006b 100644
> --- a/doc/libtool.texi
> +++ b/doc/libtool.texi
> @@ -100,7 +100,7 @@ GNU Libtool.
> * FAQ::                         Frequently Asked Questions
> * Troubleshooting::             When libtool doesn't work as advertised.
> * Maintaining::                 Information used by the libtool maintainer.
> -* GNU Free Documentation License:: License for this manual.
> +* GNU Free Documentation License::  License for this manual.
> * Combined Index::              Full index.
>
> @detailmenu
> @@ -127,7 +127,7 @@ Linking executables
>
> * Wrapper executables::         Wrapper executables for some platforms.
>
> -Invoking @code{libtool}
> +Invoking @command{libtool}
>
> * Compile mode::                Creating library object files.
> * Link mode::                   Generating executables and libraries.
> @@ -176,7 +176,7 @@ Dlopened modules
>
> * Building modules::            Creating dlopenable objects and libraries.
> * Dlpreopening::                Dlopening that works on static platforms.
> -* Linking with dlopened modules:: Using dlopenable modules in libraries.
> +* Linking with dlopened modules::  Using dlopenable modules in libraries.
> * Finding the dlname::          Choosing the right file to @code{dlopen}.
> * Dlopen issues::               Unresolved problems that need your attention.
>
> @@ -189,7 +189,7 @@ Using libltdl
> * Module loaders for libltdl::  Creating user defined module loaders.
> * Distributing libltdl::        How to distribute libltdl with your package.
>
> -Frequently Asked Questions
> +Frequently Asked Questions about libtool
>
> * Stripped link flags::         Dropped flags when creating a library
>
> @@ -200,7 +200,7 @@ Troubleshooting
>
> The libtool test suite
>
> -* Test descriptions::           The contents of the test suite.
> +* Test descriptions::           The contents of the old test suite.
> * When tests fail::             What to do when a test fails.
>
> Maintenance notes for libtool
> @@ -227,6 +227,15 @@ Platform quirks
> * File name conversion::        Converting file names between platforms.
> * Windows DLLs::                Windows header defines.
>
> +File name conversion
> +
> +* File Name Conversion Failure::  What happens when file name conversion fails
> +* Native MinGW File Name Conversion::  MSYS file name conversion idiosyncrasies
> +* Cygwin/Windows File Name Conversion::  Using @command{cygpath} to convert 
> Cygwin file names
> +* Unix/Windows File Name Conversion::  Using Wine to convert Unix paths
> +* LT_CYGPATH::                  Invoking @command{cygpath} from other 
> environments
> +* Cygwin to MinGW Cross::       Other notes concerning MinGW cross
> +
> @end detailmenu
> @end menu
>
> @@ -3347,7 +3356,7 @@ use libtool to generate dlopen-accessible modules.
> @menu
> * Building modules::            Creating dlopenable objects and libraries.
> * Dlpreopening::                Dlopening that works on static platforms.
> -* Linking with dlopened modules:: Using dlopenable modules in libraries.
> +* Linking with dlopened modules::  Using dlopenable modules in libraries.
> * Finding the dlname::          Choosing the right file to @code{dlopen}.
> * Dlopen issues::               Unresolved problems that need your attention.
> @end menu
> @@ -6069,12 +6078,12 @@ See @pxref{Unix/Windows File Name Conversion} and 
> @pxref{LT_CYGPATH}.
> @end multitable
>
> @menu
> -* File Name Conversion Failure::        What happens when file name conversion 
> fails
> -* Native MinGW File Name Conversion::   MSYS file name conversion 
> idiosyncrasies
> -* Cygwin/Windows File Name Conversion:: Using @command{cygpath} to convert 
> Cygwin file names
> -* Unix/Windows File Name Conversion::   Using Wine to convert Unix paths
> -* LT_CYGPATH::                          Invoking @command{cygpath} from other 
> environments
> -* Cygwin to MinGW Cross::               Other notes concerning MinGW cross
> +* File Name Conversion Failure::  What happens when file name conversion fails
> +* Native MinGW File Name Conversion::  MSYS file name conversion idiosyncrasies
> +* Cygwin/Windows File Name Conversion::  Using @command{cygpath} to convert 
> Cygwin file names
> +* Unix/Windows File Name Conversion::  Using Wine to convert Unix paths
> +* LT_CYGPATH::                  Invoking @command{cygpath} from other 
> environments
> +* Cygwin to MinGW Cross::       Other notes concerning MinGW cross
> @end menu
>
> @node File Name Conversion Failure

--
Bob Friesenhahn
address@hidden, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/