From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \everymath problem
Date: Wed, 19 Aug 2009 16:53:57 +0200 [thread overview]
Message-ID: <AEB2AC7D-413B-4929-B06F-A231FA2E7200@gmail.com> (raw)
In-Reply-To: <4A8C1091.5000601@wxs.nl>
Am 19.08.2009 um 16:47 schrieb Hans Hagen:
> Eythan Weg wrote:
>> Hi,
>> I use luatex 0.43 with yesterday's beta. Running \everymath =
>> {\displaystyle}
>> \starttext
>> ${a\over b}$
>> \stoptext
>> results in ! Use of \dospecialabout doesn't match its definition.
>> l.4 ${a\over b
>> }$
>> Plain format under luatex has no problem here.
>> If I change \over to \times it runs with fonts changed
>> to roman (i.e, not math italics).
>
> taco and i looked into it (fearing big problems) but it's actually
> normal; use
>
> \everymath = \expandafter{\the\everymath \displaystyle}
>
> or
>
> \appendtoks \displaystyle \to \everymath
>
> as (among other important things) \everymath does initialize \over
And with \frac it can be configured at context low level (why no key
for \setupmathematics?)
\chardef\mathfracmode=1 % 0=auto, 1=displaystyle, 2=textstyle,
3=scriptstyle, 4=scriptscriptstyle, 5=mathstyle
$\frac{a}{b}$
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-08-19 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 13:22 Eythan Weg
2009-08-19 14:47 ` Hans Hagen
2009-08-19 14:53 ` Wolfgang Schuster [this message]
2009-08-20 14:59 ` Frac (was \everymath problem) 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=AEB2AC7D-413B-4929-B06F-A231FA2E7200@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).