> Date: Mon, 1 Jan 2018 17:55:52 +0000 > Cc: [email protected] > From: Alan Mackenzie <[email protected]> > > > I believe you are right. One place where this is definitely used is > > in some macros. > > The actual source in cc-mode.texi which showed up the bug was indeed in > a macro, namely: > > @macro hereFn{func} > <- @i{\func\}@c > @end macro > > . This macro was committed on 2003-05-12. The @c at EOL2 looks like a > workaround for some glitch in an earlier version of makeinfo. (As a > matter of interest, makeinfo 4.13 builds the source correctly, whether > or not the "@c" is present.).
What bug did that cause in recent versions of makeinfo? > This workaround could be present in a lot of files.texi that were being > actively modified around 15 years ago. Again, would it be possible to > output a warning for this situation, and possibly document it in > texinfo's own documentation? What's to warn about? This trick is for versions of makeinfo which leave newlines in macro expansions, since otherwise you will have trouble coming up with macros that expand into Texinfo directives which need to be alone on their lines, like "@item" or "@end SOMETHING".
