ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Sergey Slyusarev <cph.lmy@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: Bug: \textext inside \*MPinclusions causes error
Date: Thu, 12 Jan 2017 14:23:25 +0300	[thread overview]
Message-ID: <CAHUe7fB7EdC95-w63KneNGQrF_c_qD=3pnD02ezTQZJzfJZ9VA@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 792 bytes --]

> you can use
> \startMPinitializations
> \stopMPinitializations
> as these are expanded each graphic run


Thank you! This works fine with minimal example (in which the
behaviour in question appears).
But in specific context in which this problem affects me, this
solution breaks many things:

There are many *MPinclusions with as many MPinstances (so variables
from one instance don't contaminate another).
(here's that place:
https://github.com/jemmybutton/byrne-euclid/blob/master/preamble.tex#L30)

If this is indeed a bug and it's going to be fixed one day, I'll go
with some less invasive hack to overcome it,
but if this behaviour is correct, I'll try to rewrite everything accordingly.

Or I got it wrong and *MPinitializations can substitute for
*MPinclusions in this case?

Sergey

[-- Attachment #1.2: Type: text/html, Size: 1027 bytes --]

[-- Attachment #2: Type: text/plain, Size: 492 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

             reply	other threads:[~2017-01-12 11:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 11:23 Sergey Slyusarev [this message]
2017-01-15 17:55 ` Hans Hagen
  -- strict thread matches above, loose matches on Subject: below --
2017-01-16 19:31 Sergey Slyusarev
2017-01-17  8:35 ` Hans Hagen
2017-01-21 21:13   ` Sergey Slyusarev
2017-01-22 12:23     ` Hans Hagen
2017-02-13 22:36       ` Sergey Slyusarev
2017-02-14 12:13         ` Hans Hagen
2017-01-11 22:08 Sergey Slyusarev
2017-01-12  9:06 ` Hans Hagen
2017-01-12 16:53   ` Alan Braslau

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='CAHUe7fB7EdC95-w63KneNGQrF_c_qD=3pnD02ezTQZJzfJZ9VA@mail.gmail.com' \
    --to=cph.lmy@gmail.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).