From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Christoph Reller <christoph.reller@gmail.com>
Subject: Re: Typing within doifmode leads to error
Date: Fri, 19 Mar 2021 09:49:08 +0100 [thread overview]
Message-ID: <41b732e4-b771-15a2-7fc1-5ead8086f4f9@xs4all.nl> (raw)
In-Reply-To: <CAO8LnPEyBZxVZiBVc265NJmngQMbtD8+9puL1ya+OJg4EZkwFA@mail.gmail.com>
On 3/19/2021 4:58 AM, Christoph Reller wrote:
> Hi,
>
> Consider the following MWE:
>
> \definetyping[T]
> \definemode[mode][yes]
> \starttext
> \doifmode{mode}{%
> \startT
> Bla
> \stopT}
> \stoptext
>
> Compilation with the currently latest ConTeXt LMTX (ver: 2021.03.17
> 17:46 LMTX fmt: 2021.3.18) fails with:
>
> tex error > runaway error: end of file encountered
> mtx-context | fatal error: return code: 1
>
> Compilation is successful if I replace doifmode{mode}{...} by
> \startmode[mode]...\stopmode.
>
> Is there anything I'm missing? (This could be a bug.)
not a bug, just the way tex works .. modes cannot know that what goes
into an argument is something verbose
but you can use this (also more efficient here):
\definetyping[T]
\definemode[mode][yes]
\starttext
\startmode[mode]
\startT
Bla
\stopT
\stopmode
\stoptext
% there's also \startnotmode
-----------------------------------------------------------------
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-03-19 8:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 3:58 Christoph Reller
2021-03-19 4:37 ` Aditya Mahajan
2021-03-19 6:59 ` Christoph Reller
2021-03-19 8:49 ` Hans Hagen [this message]
2021-03-20 5:24 ` Christoph Reller
2021-03-20 7:24 ` Aditya Mahajan
2021-03-20 11:11 ` Hans Hagen
2021-03-20 15:00 ` Christoph Reller
2021-03-20 17:07 ` Hans Hagen
2021-03-20 20:23 ` Aditya Mahajan
2021-03-20 20:49 ` Hans Hagen
2021-03-20 21:03 ` Aditya Mahajan
2021-03-21 1:43 ` Hans Hagen
2021-03-21 2:40 ` Aditya Mahajan
2021-03-21 14:44 ` Christoph Reller
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=41b732e4-b771-15a2-7fc1-5ead8086f4f9@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=christoph.reller@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).