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

Sat Jul 29 03:07:48 CEST 2006

On Fri, 28 Jul 2006, Hans Hagen 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

! Extra }, or forgotten $. <recently read> } <argument> ...tofoneargument {\type {$\Pr \{A\}$}} \endstrut }\xdef \localhe... \@@ko::normal ...box {\localheadsetup \noindent #2 }\fi \doplaceheadtext ...attributes \dostopattributes } }\fi \endheadplacement {#1... \dodododoconstructhead ...arking [#1\v!number ]{}} \writesection {#1}{-}{#4}\... l.69 \title{\type{$\Pr\{A\}\$}}

which I think is the currect behaviour.

There is really no need to change anything. I am happy with "Do not
use \type inside argument. The unexpected can happen."