On Sat, Feb 23, 2013 at 12:15:11PM +0200, Eli Zaretskii wrote: > > . There are some errors: > > tramp.texi:2457: misplaced { (possibly involving @xxx) > tramp.texi:2457: misplaced } > tramp.texi:2457: misplaced { > tramp.texi:2457: misplaced } > tramp.texi:2459: too many columns in multitable item (max 1) > tramp.texi:2460: too many columns in multitable item (max 1) > tramp.texi:2484: misplaced { (possibly involving @xxx) > tramp.texi:2484: misplaced } > tramp.texi:2484: misplaced { > tramp.texi:2484: misplaced }
For the errors corresponding to @multitable, something like @multitable {@trampfn{telnet, , melancholia.danann.net,}} {@trampfn{telnet, , 192.168.0.1,}} ... @end multitable the issue is not @clear or @set, but the line that is expanded, telnet@w{}@value{postfixhop}@c that stops the multitable. A simplified example is @macro ttt @c @end macro @multitable {aaa @ttt{} bbb} @end multitable makeinfo in C handles that, but errors out with the expanded version, which should be equivalent: @multitable {aaa @c bbb} @end multitable So, in that case, I think that the makeinfo in C behaviour is incorrect, and happens by chance because of an inconsistent expansion of user defined macros in some contexts. An additional hint of this the case is that when called with -E, makeinfo in C do not expand the user defined macro. For example, with the macro above and -E, @multitable {aaa @ttt{} bbb} @end multitable aaa @ttt{} bbb leads to @multitable {aaa @ttt{} bbb} @end multitable aaa @c bbb So, my analysis is that this should be kept as an error. -- Pat