From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Integral limits
Date: Mon, 18 Nov 2013 22:12:57 +0100 [thread overview]
Message-ID: <528A82D9.2000100@wxs.nl> (raw)
In-Reply-To: <alpine.LNX.2.03.1311181537340.18341@hzvpu.rqh>
On 11/18/2013 9:41 PM, Aditya Mahajan wrote:
> Hi,
>
> In MkII, it was possible to change the limits on integrals using
>
> \setupmathematics[integral=...] % limits, nolimits, displaylimits
>
> that would affect how \int, \iint, \iiint, \oint, etc behaved.
>
> I can see two ways of definining a similar feature in MkIV.
>
> 1. Define \intop, \iintop, etc in char-def.lua and then somewhere define:
>
> \define\int{\intop\intlimits}
> \define\iint{\intop\intlimits}
>
> etc.
>
> 2. Define a new mathclass "intop" and use that in char-def.lua. Then, in
> the appropriate math-*.lua file, map intop to the appropriate macro.
>
> What would be the best way to go?
i prefer 2 (as these set the defaults) and we can make a definer for
specific variants if needed (at all)
is intop the best name? (we don't need to be sparse)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2013-11-18 21:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 20:41 Aditya Mahajan
2013-11-18 21:12 ` Hans Hagen [this message]
2013-11-18 22:45 ` Aditya Mahajan
2013-11-19 0:14 ` Hans Hagen
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=528A82D9.2000100@wxs.nl \
--to=pragma@wxs.nl \
--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).