COMMIT makeinfo does not complain about this, while texinfmt.el says: Formatting: The Compilation Functions ... Formatting: Options for the Byte Compiler ... Stop. Compilation exited abnormally with code 2 at Sun Sep 25 23:00:30 This patch brings the manual in line with the docstring, which should be non-controversial. Best regards, Adrian xemacs-21.5-clean ChangeLog patch: Diff command: cvs -q diff -U 0 Files affected: man/ChangeLog Index: man/ChangeLog =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/man/ChangeLog,v retrieving revision 1.310 diff -u -U0 -r1.310 ChangeLog --- man/ChangeLog 14 Sep 2005 05:30:00 -0000 1.310 +++ man/ChangeLog 25 Sep 2005 21:39:34 -0000 ＠＠ -0,0 +1,6 ＠＠ +2005-09-25 Adrian Aichner <adrian(a)xemacs.org&gt; + + * lispref/compile.texi (Compilation Options): Supply missing + argument to ＠var{}, using same SYMBOL as in variable docstring of + `byte-compile-print-gensym'. + xemacs-21.5-clean source patch: Diff command: cvs -f -z3 -q diff -u -w -N Files affected: man/lispref/compile.texi Index: man/lispref/compile.texi =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/man/lispref/compile.texi,v retrieving revision 1.6 diff -u -w -r1.6 compile.texi --- man/lispref/compile.texi 12 Nov 2002 03:57:48 -0000 1.6 +++ man/lispref/compile.texi 25 Sep 2005 21:31:56 -0000 ＠＠ -503,8 +503,8 ＠＠ ＠defvar byte-compile-print-gensym When non-＠code{nil}, the compiler may generate code that creates unique symbols at run-time. This is achieved by printing uninterned symbols -using the ＠code{#:＠var{}} notation, so that they will be read uninterned -when run. +using the ＠code{#:＠var{SYMBOL}} notation, so that they will be read +uninterned when run. With this feature, code that uses uninterned symbols in macros will not be runnable under pre-21.0 XEmacsen. -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/