From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: Bug with type << .. >>?
Date: Sun, 30 Jul 2006 00:04:26 -0400 (EDT) [thread overview]
Message-ID: <Pine.WNT.4.63.0607300002150.3812@nqvgln> (raw)
In-Reply-To: <44CB3A96.8040104@wxs.nl>
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
prev parent reply other threads:[~2006-07-30 4:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 5:02 Aditya Mahajan
2006-07-28 5:05 ` Aditya Mahajan
2006-07-28 9:57 ` Hans Hagen
2006-07-28 10:39 ` Hans Hagen
2006-07-29 0:53 ` Aditya Mahajan
2006-07-28 9:55 ` Hans Hagen
2006-07-29 1:07 ` Aditya Mahajan
2006-07-29 10:38 ` Hans Hagen
2006-07-29 12:16 ` Taco Hoekwater
2006-07-30 19:31 ` Hans Hagen
2006-07-30 4:04 ` Aditya Mahajan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.WNT.4.63.0607300002150.3812@nqvgln \
--to=adityam@umich.edu \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).