$(_sc_search_regexp)
# Check for opening brace on next line in shell function definition.
-exclude_file_name_regexp--sc_require_function_nl_brace = (^HACKING|\.[ch])$$
+exclude_file_name_regexp--sc_require_function_nl_brace = (^HACKING|\.[ch]|\.texi)$$
sc_require_function_nl_brace:
@for file in $$($(VC_LIST_EXCEPT)); do \
sed -n '/^func_[^ ]*[ ]*(/{ \
package.
@example
- vc_ignore=".gitignore"
+ vc_ignore=.gitignore
@end example
@table @code
A newline-delimited list of triples of @strong{programs} (which must
accept the option @option{--version} without hanging or failing), the
@strong{minimum version required} (or just `-' in the version field if
-any version will be sufficient) and @strong{homepage @acronym{url} (to
+any version will be sufficient) and @strong{homepage URL (to
help users locate missing packages)
@smallexample
-buildreq='
+buildreq='
git 1.5.5 http://git-scm.com
help2man 1.29 http://www.gnu.org/s/help2man
'
@item buildreq_readme
Name of a file containing instructions on installing missing packages
required in @code{buildreq}. Usually, the instructions at the given
-@acronym{url} should be sufficient, though some projects add additional
-notes in @file{HACKING}.
+URL should be sufficient, though some projects add additional notes
+in @file{HACKING}.
@smallexample
buildreq_readme=README-hacking
alternative values here in @file{bootstrap.conf}.
If you check @file{gnulib-cache.m4} into your repository, then these
-values will be extracted automatically. @pxref{Usage Patterns}, for more
+values will be extracted automatically. @xref{Usage Patterns}, for more
details.
The list of gnulib modules required at @command{gnulib-tool} time.
If you check @file{gnulib-cache.m4} into your repository, then this list
-will be extracted automatically. @pxref{Usage Patterns}, for more
+will be extracted automatically. @xref{Usage Patterns}, for more
details.