From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Otared Kavian <otared@gmail.com>
Subject: Re: \mathopen, \Uover and friends
Date: Sat, 9 May 2020 23:27:54 +0200 [thread overview]
Message-ID: <55b4c501-e7b3-e2e3-df64-f1cba065d111@xs4all.nl> (raw)
In-Reply-To: <855F1FE9-BBC9-4217-B5E4-FF261D922186@gmail.com>
On 5/9/2020 6:29 PM, Otared Kavian wrote:
> Hi Hans,
>
> Thanks for the quick fix of today's upload.
> I could typeset your examples with \mathopen, \mathclose and these are great features in order to fine tune the spacing in math mode.
>
> Regarding the new command \Uover, I thought maybe it would be more consistent to have the usual structure
> ${1} \Uover {2}$
> like the more friendly ${1} \over {2}$ instead of having
That would involve backtracking and be a psin in the butt wrt control.
One can't have it all.
> $\Uover{1}{2}$
> which is more like the \frac structure.
Watch out: these are low level primitives (it is actually a set of
primitives that put stuff on top of each other). The \frac is the
interfaced variant.
> Also a structure like
> $\Uover style \textstyle{1}{2}$
> seems a little bit far from the usual ConTeXt atmposphere… Would it not be possible to have
> ${1} \Uover[style=textstyle] {2}$
> instead?
That is what we have frac for (and one can define veriants that have set
styles).
> In any case, thanks a lot for the constant addition of cute features…
Some of these engine level extensions have been on my list for a while
and eventually make implementing the user interfaced wrappers nicer (and
sometimes more robust). Some is actually possible because some engine
internals are a bit reorganized.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2020-05-09 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 16:29 Otared Kavian
2020-05-09 21:27 ` Hans Hagen [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=55b4c501-e7b3-e2e3-df64-f1cba065d111@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
--cc=otared@gmail.com \
/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).