bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Problem with texinfo.tex 6.0


From: David Kastrup
Subject: Re: Problem with texinfo.tex 6.0
Date: Wed, 01 Jul 2015 20:07:09 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)

Gavin Smith <address@hidden> writes:

>> At any rate, what you cite from the Texinfo manual converns macros with
>> multiple arguments.  For the one-argument macro that is at bay here, we
>> rather have
>>
>>   1. If a macro takes only one argument, all commas in its invocation
>>      are quoted by default.  For example:
>>
>>           @macro TRYME{text}
>>           @strong{TRYME: \text\}
>>           @end macro
>>
>>           @TRYME{A nice feature, though it can be dangerous.}
>>
>>      will produce the following output
>>
>>           *TRYME: A nice feature, though it can be dangerous.*
>>
>>      And indeed, it can.  Namely, 'makeinfo' does not control the number
>>      of arguments passed to one-argument macros, so be careful when you
>>      invoke them.
>>
>> So it would appear that for the one-argument situation, some sort of
>> quoting/protection/whatever of \ would seem warranted.
>
> It would be possible to turn backslash interpretation off altogether
> for single-parameter macros when invoked using braces (as is now done
> for whole-line arguments), but this would be a bad idea because it
> would be inconsistent with macros with more parameters,

Well, according to point 1 above, macros with more parameters _are_
already treated different from macros with one parameter.

> and likely incompatible with makeinfo. (E.g. @warning{\\} should
> output a single backslash, not two.)

No idea here.

-- 
David Kastrup



reply via email to

[Prev in Thread] Current Thread [Next in Thread]