Re: makeinfo bug: macros with no arguments don't work as expected

2009-05-06 Thread Bruno Haible
An update on this one: When I define the macro through @macro texnl{} @end macro and invoke it through @texnl then it eats up all text until the next newline, like @c. When I define the macro through @macro texnl @end macro and invoke it through @texnl then it eats up all spaces

Re: makeinfo bug: macros with no arguments don't work as expected

2009-05-06 Thread Karl Berry
Only @texnl{} appears to work right. Can this be either fixed or a warning added to the documentation? As previously stated, it already is in the documentation. What would be more useful is to have a warning in the code. Patrice? Thanks, k

makeinfo bug: macros with no arguments don't work as expected

2009-05-01 Thread Bruno Haible
Hi, I'm using makeinfo-4.13, and define a macro that should take no arguments and should produce an empty expansion. The texinfo doc says: If a macro needs no parameters, you can define it either with an empty list (`...@macro foo {}') or with no braces at all (`...@macro foo'). When I

Re: makeinfo bug: macros with no arguments don't work as expected

2009-05-01 Thread Ben Pfaff
Bruno Haible br...@clisp.org writes: When I define the macro as follows: @macro texnl{} @end macro and my input text is: This is a more low-level API. The word break property is a property defined in Unicode Standard Annex #29, section ``Word Boundaries'', see