[NTG-context] Bug with type << .. >>?

Aditya Mahajan adityam at umich.edu
Sun Jul 30 06:04:26 CEST 2006


On Sat, 29 Jul 2006, Hans Hagen wrote:

> Aditya Mahajan wrote:
>> On Fri, 28 Jul 2006, Hans Hagen wrote:
>>
>>
>>> Aditya Mahajan wrote:
>>>
>>>> Isn't \type<<..>> be supposed to be equivalent to \type{..} ?
>>>>
>>>> \title{some \type{thing} }
>>>>
>>>> works perfectly but
>>>>
>>>> \title{some \type<<thing>>}
>>>>
>>>>
>>> << >> will not work in commands that get an argument because it is
>>> related to catcode changes
>>>
>>
>> Ah. Makes sense.
>>
>>
>>> we could use \scantokens if there was not this space-creeps-in-after
>>> \cs  problem)
>>>
>>
>> Well, found a workaround. Not sure if this one is a bug or a feature
>> (is a feature to me)
>>
>> \title{some \type{\thing\{and\}}}
>>
>> However, things get real weird.
>>
>> \title{\type{$\Pr\{A\}$}}
>>
>> gives me
>>
>
> you can try:
>
> \title{\retype{$\Pr\{A\}$}}
>
> watch the space after \Pr

Thanks for the hint.

I also found out

\startbuffer
$\Pr\{A\}$
\stopbuffer

\title{\typebuffer}

which seems pretty robust.

Aditya


More information about the ntg-context mailing list