From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bad interaction between new interpretation of underscore and modules
Date: Fri, 14 Jan 2011 12:13:57 +0100 [thread overview]
Message-ID: <F1D96BC8-FE1F-4C13-A342-074B99119238@gmail.com> (raw)
In-Reply-To: <4D302CEE.60701@wxs.nl>
Am 14.01.2011 um 12:01 schrieb Hans Hagen:
> just add a space before the _ when it directly follows a \cs, so
>
> ... $\cs _2$ ...
>
> but regular text like
>
> ... $x_2$ ...
>
> can be left as it is
He put the definitions in a external file which he loads with \usemodule and then this won’t work
\starttexcode
\def\lambdaone{\lambda_x}
\stoptexcode
\starttexcode
\def\lambdatwo{\lambda _x}
\stoptexcode
\starttexcode
\pushcatcodetable\donknuthmode
\def\lambdathree{\lambda_x}
\popcatcodes
\stoptexcode
\starttext
\doifmode{one} {$\lambdaone $}
\doifmode{two} {$\lambdatwo $}
\doifmode{three}{$\lambdathree$}
\stoptext
1. context --mode=one test.tex
! Undefined control sequence.
\lambdaone ->\lambda_x
<argument> $\lambdaone
$
\firstofoneargument #1->#1
l.16 \doifmode{one} {$\lambdaone $}
?
2. context --mode=two test.tex
! Undefined control sequence.
\lambdatwo ->\lambda _
x
<argument> $\lambdatwo
$
\firstofoneargument #1->#1
l.17 \doifmode{two} {$\lambdatwo $}
?
3. context --mode=three test.tex
-> test.pdf
Wolfgang
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2011-01-14 11:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 16:18 Mathieu Boespflug
2011-01-13 21:50 ` Wolfgang Schuster
2011-01-13 22:43 ` Aditya Mahajan
2011-01-14 0:14 ` Wolfgang Schuster
2011-01-14 9:15 ` Mathieu Boespflug
2011-01-14 9:32 ` Wolfgang Schuster
2011-01-14 10:09 ` Mathieu Boespflug
2011-01-14 11:01 ` Hans Hagen
2011-01-14 11:13 ` Wolfgang Schuster [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=F1D96BC8-FE1F-4C13-A342-074B99119238@gmail.com \
--to=schuster.wolfgang@googlemail.com \
--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).