Dear list,
In case someone else stumbles upon this issue, the following code works.
MWE:
\autofences
\starttext
$\left]-\infty; a\right[$
\stoptext
Best regards,
Alex
Le 22 sept. 2022 à 12:59 +0200, Alexandre Christe , a
écrit :
> Hi Hans,
>
> Thanks a lot for the example. It works great
Hi Hans,
Thanks a lot for the example. It works great in most cases, however what I
stumbled upon is with the interval notation, in particular the following
cases arise:
- closed interval: easy, since the delimiters are [... ; ... ]
- open interval: not easy, since the delimiters are ]... ; ... [
On 9/10/2022 9:45 AM, Alexandre Christe via ntg-context wrote:
Hi Hans,
Will |\mvert|and|\midalso be included in the \autofencelogic? It would
be quite useful.|
we don't have \mvert so i'll add that ... in a next upload you can do
the attached (kind of experimental as Mikael and I need to
On 9/10/2022 9:45 AM, Alexandre Christe via ntg-context wrote:
Hi Hans,
Will |\mvert|and|\midalso be included in the \autofencelogic? It would
be quite useful.|
i prototyped it but the chairman of the CMS has to check it before we
decide to enable it
one complication is that
$
Hi Hans,
Will \mvert and \mid also be included in the \autofence logic? It would be
quite useful.
Le jeu. 25 août 2022 à 18:18, Hans Hagen via ntg-context
a écrit :
> Hi,
>
> I uploaded a new lmtx. Again some updated math of which details will be
> revealed later. Apart from some details we
Hi,
I uploaded a new lmtx. Again some updated math of which details will be
revealed later. Apart from some details we added suport for fourier
notations. There are no high level definitions yet as we have to invent
names but this is how it works (private unicode slots might change):
Hi,
a new lmtx upload
- crash with bottom floats probably solved: had to do with tricky
interaction between engine insert handling and callback interference (as
well as some assumptions in the engine dating that relate to the fact
that tex was never written to be opened up this way)
-