From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/29795 Path: news.gmane.org!not-for-mail From: Aditya Mahajan Newsgroups: gmane.comp.tex.context Subject: Re: Bug with type << .. >>? Date: Sun, 30 Jul 2006 00:04:26 -0400 (EDT) Message-ID: References: <44C9DF26.2030208@wxs.nl> <44CB3A96.8040104@wxs.nl> Reply-To: mailing list for ConTeXt users NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1154232293 10603 80.91.229.2 (30 Jul 2006 04:04:53 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 30 Jul 2006 04:04:53 +0000 (UTC) Original-X-From: ntg-context-bounces@ntg.nl Sun Jul 30 06:04:51 2006 Return-path: Envelope-to: gctc-ntg-context-518@m.gmane.org Original-Received: from ronja.vet.uu.nl ([131.211.172.88] helo=ronja.ntg.nl) by ciao.gmane.org with esmtp (Exim 4.43) id 1G72Xq-0006Nj-8P for gctc-ntg-context-518@m.gmane.org; Sun, 30 Jul 2006 06:04:50 +0200 Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 11DFC1FE84; Sun, 30 Jul 2006 06:04:49 +0200 (CEST) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (smtp.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 22216-05; Sun, 30 Jul 2006 06:04:41 +0200 (CEST) Original-Received: from ronja.vet.uu.nl (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id B9D581FE73; Sun, 30 Jul 2006 06:04:40 +0200 (CEST) Original-Received: from localhost (localhost [127.0.0.1]) by ronja.ntg.nl (Postfix) with ESMTP id 5BA3D1FE73 for ; Sun, 30 Jul 2006 06:04:37 +0200 (CEST) Original-Received: from ronja.ntg.nl ([127.0.0.1]) by localhost (smtp.ntg.nl [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 23111-01 for ; Sun, 30 Jul 2006 06:04:33 +0200 (CEST) Original-Received: from tombraider.mr.itd.umich.edu (smtp.mail.umich.edu [141.211.93.161]) by ronja.ntg.nl (Postfix) with SMTP id 6CC341FE59 for ; Sun, 30 Jul 2006 06:04:32 +0200 (CEST) Original-Received: FROM aditya.annarb01.mi.comcast.net (c-68-40-50-205.hsd1.mi.comcast.net [68.40.50.205]) BY tombraider.mr.itd.umich.edu ID 44CC2FCC.77AF3.31774 ; 30 Jul 2006 00:04:29 -0400 Original-To: mailing list for ConTeXt users In-Reply-To: <44CB3A96.8040104@wxs.nl> X-Virus-Scanned: amavisd-new at ntg.nl X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.7 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: ntg-context-bounces@ntg.nl Errors-To: ntg-context-bounces@ntg.nl X-Virus-Scanned: amavisd-new at ntg.nl Xref: news.gmane.org gmane.comp.tex.context:29795 Archived-At: 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<>} >>>> >>>> >>> << >> 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