-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Ralf Wildenhues on 4/21/2009 2:48 PM:
>> At least we're consistent in using the term 'AC_CONFIG_FOOS' throughout the
>> manual. But on rereading this, I think I'd like:
>>
>> @code{ac_conf...@var{foos}}
>>
>> better, since it emphasizes that FOOS is a meta-syntactic placeholder for
>> one
>> of the four config actions. It won't help info text (since FOOS is already
>> in
>> capitals), but will make html and pdf renderings nicer.
>
> Hmm. We have more instances of using foo or FOO or FOOS instead of
> using metasyntactic variables in the manual, in several markup
> circumstances. I think such a change would deserve a bit more work,
> and maybe some renaming, too.
How about the following? I searched the entire manual for uses of _foo
and _FOO, and only these stood out to me.
- --
Don't work too hard, make some time for fun as well!
Eric Blake [email protected]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknv2BYACgkQ84KuGfSFAYApawCgqk9uHeGWyxFVW4p32WhTYsej
bdsAnikuCa7/o0Cv+RO8O61miCMT2coc
=qLfU
-----END PGP SIGNATURE-----
>From 9cee35c16c4a13555bb8dbda285bf44032b73b0f Mon Sep 17 00:00:00 2001
From: Eric Blake <[email protected]>
Date: Wed, 22 Apr 2009 16:53:19 -0600
Subject: [PATCH] Change FOO placeholder to use @var{text} instead.
* doc/autoconf.texi (Configuration Actions): Rename AC_CONFIG_FOOS
to ac_conf...@var{items}.
* doc/autoconf.texi (config.status Invocation): Likewise.
(AC_FOO_IFELSE vs AC_TRY_FOO): Rename node...
(a...@var{act}_ifelse vs ac_t...@var{act}): ...to this.
Signed-off-by: Eric Blake <[email protected]>
---
ChangeLog | 7 +++++++
doc/autoconf.texi | 22 ++++++++++++----------
2 files changed, 19 insertions(+), 10 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 8bc3ecd..d40e9c0 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,12 @@
2009-04-22 Eric Blake <[email protected]>
+ Change FOO placeholder to use @var{text} instead.
+ * doc/autoconf.texi (Configuration Actions): Rename AC_CONFIG_FOOS
+ to ac_conf...@var{items}.
+ * doc/autoconf.texi (config.status Invocation): Likewise.
+ (AC_FOO_IFELSE vs AC_TRY_FOO): Rename node...
+ (a...@var{act}_ifelse vs ac_t...@var{act}): ...to this.
+
Add m4_argn.
* lib/m4sugar/m4sugar.m4 (m4_argn): New macro.
* NEWS: Document it.
diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index 516e58d..74b64d5 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -594,7 +594,7 @@ Top
* New Macros:: Interaction with foreign macros
* Hosts and Cross-Compilation:: Bugward compatibility kludges
* AC_LIBOBJ vs LIBOBJS:: LIBOBJS is a forbidden token
-* AC_FOO_IFELSE vs AC_TRY_FOO:: A more generic scheme for testing sources
+* a...@var{act}_ifelse vs ac_t...@var{act}:: A more generic scheme for
testing sources
Generating Test Suites with Autotest
@@ -2105,7 +2105,7 @@ Configuration Actions
@c FIXME: Can't use @ovar here, Texinfo 4.0 goes lunatic and emits something
@c awful.
@example
-AC_CONFIG_FOOS(@var{t...@dots{}, [...@var{commands}], [...@var{init-cmds}])
+ac_conf...@var{items}(@var{t...@dots{}, [...@var{commands}],
[...@var{init-cmds}])
@end example
@noindent
@@ -2122,15 +2122,15 @@ Configuration Actions
@example
@dots{} && my_foos="$my_foos fooo"
@dots{} && my_foos="$my_foos foooo"
-AC_CONFIG_FOOS([$my_foos])
+ac_conf...@var{items}([$my_foos])
@end example
@noindent
and use this instead:
@example
-...@dots{} && AC_CONFIG_FOOS([fooo])
-...@dots{} && AC_CONFIG_FOOS([foooo])
+...@dots{} && ac_conf...@var{items}([fooo])
+...@dots{} && ac_conf...@var{items}([foooo])
@end example
The macros @code{AC_CONFIG_FILES} and @code{AC_CONFIG_HEADERS} use
@@ -3434,7 +3434,7 @@ Configuration Commands
Execute the @var{cmds} right before creating @file{config.status}.
This macro presents the last opportunity to call @code{AC_SUBST},
-...@code{ac_define}, or @code{AC_CONFIG_FOOS} macros.
+...@code{ac_define}, or @code{ac_conf...@var{items}} macros.
@end defmac
@defmac AC_CONFIG_COMMANDS_POST (@var{cmds})
@@ -20064,7 +20064,7 @@ config.status Invocation
It configures each @var{tag}; if none are specified, all the templates
are instantiated. A @var{tag} refers to a file or other tag associated
-with a configuration action, as specified by an @code{AC_CONFIG_FOOS}
+with a configuration action, as specified by an @code{ac_conf...@var{items}}
macro (@pxref{Configuration Actions}). The files must be specified
without their dependencies, as in
@@ -21678,7 +21678,7 @@ Autoconf 2.13
* New Macros:: Interaction with foreign macros
* Hosts and Cross-Compilation:: Bugward compatibility kludges
* AC_LIBOBJ vs LIBOBJS:: LIBOBJS is a forbidden token
-* AC_FOO_IFELSE vs AC_TRY_FOO:: A more generic scheme for testing sources
+* a...@var{act}_ifelse vs ac_t...@var{act}:: A more generic scheme for
testing sources
@end menu
@node Changed Quotation
@@ -21974,8 +21974,10 @@ AC_LIBOBJ vs LIBOBJS
The @code{LIBOBJDIR} feature is experimental.
-...@node AC_FOO_IFELSE vs AC_TRY_FOO
-...@subsection @code{AC_FOO_IFELSE} vs.@: @code{AC_TRY_FOO}
+...@node a...@var{act}_ifelse vs ac_t...@var{act}
+...@subsection @code{...@var{act}_ifelse} vs.@: @code{ac_t...@var{act}}
+...@c the anchor keeps the old node name, to try to avoid breaking links
+...@anchor{ac_foo_ifelse vs AC_TRY_FOO}
Since Autoconf 2.50, internal codes uses @code{AC_PREPROC_IFELSE},
@code{AC_COMPILE_IFELSE}, @code{AC_LINK_IFELSE}, and
--
1.6.1.2
