From: Marco Patzer via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Marco Patzer <lists@homerow.info>
Subject: Re: \asciimode and MetaPost in LMTX result in “Isolated expression”
Date: Sun, 13 Mar 2022 08:30:28 +0100 [thread overview]
Message-ID: <20220313083028.2b17a501@homerow> (raw)
In-Reply-To: <5dae2242-e6f7-aa34-a4ec-54e781becb04@fiee.net>
On Sat, 12 Mar 2022 22:27:38 +0100
Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl> wrote:
> My current and most MP-heavy project so far, fails in asciimode with
> "Extra }, or forgotten \endgroup"
You can't just run “normal” projects with \asciimode. Chances are,
constructs are being used that are invalid in asciimode.
But as far as I understand, it should be sufficient running it
without asciimode just with the \ctxcatcodes snippet in place to
test if that breaks something.
> No time to investigate why, ATM.
No problem. Thanks for checking.
Marco
___________________________________________________________________________________
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:[~2022-03-13 7:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 19:02 Marco Patzer via ntg-context
2022-03-12 14:35 ` Marco Patzer via ntg-context
2022-03-12 14:51 ` Hans Hagen via ntg-context
2022-03-12 17:08 ` Marco Patzer via ntg-context
2022-03-12 21:27 ` Henning Hraban Ramm via ntg-context
2022-03-13 7:30 ` Marco Patzer via ntg-context [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=20220313083028.2b17a501@homerow \
--to=ntg-context@ntg.nl \
--cc=lists@homerow.info \
/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).