From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: Bug with type << .. >>?
Date: Fri, 28 Jul 2006 21:07:48 -0400 (EDT) [thread overview]
Message-ID: <Pine.WNT.4.63.0607282058130.2644@nqvgln> (raw)
In-Reply-To: <44C9DF26.2030208@wxs.nl>
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
! 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."
Aditya
next prev parent reply other threads:[~2006-07-29 1:07 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 [this message]
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
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.0607282058130.2644@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).