From: Jan Willem Flamma <jwfregister@icloud.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: \doifmode error with question blocks
Date: Thu, 18 May 2017 13:48:46 +0200 [thread overview]
Message-ID: <05ABD768-D102-4DA1-9EF2-7C5BFA78A228@icloud.com> (raw)
Dear list members
If using modes to show or hide certain part of the text.
In the MWE below the part between the startmode[test] .. stopmode works jus fine. When using the \doifmode construction an error is produced on the position of the closing curly bracket.
I prefer to use \doifmode constructions because they can be nested. The question block must play a role here but I don’t know why.
Am I overlooking something here?
Kind regards,
Jan Willem Flamma
========
\enablemode[test]
\defineblock[question]
\defineblock[answer]
\starttext
\doifmode{test}{
\input knuth
\beginquestion
\startquestion
Question
\stopquestion
\endquestion
\beginanswer
\startanswer
Answer
\stopanswer
\endanswer
}
\startmode[test]
\input knuth
\beginquestion
\startquestion
Question
\stopquestion
\endquestion
\beginanswer
\startanswer
Answer
\stopanswer
\endanswer
\stopmode
\stoptext
___________________________________________________________________________________
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 reply other threads:[~2017-05-18 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 11:48 Jan Willem Flamma [this message]
2017-05-18 12:28 ` Hans Hagen
2017-05-18 16:13 ` Large space between mode blocks Jan Willem Flamma
2017-05-18 19:19 ` Hans Hagen
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=05ABD768-D102-4DA1-9EF2-7C5BFA78A228@icloud.com \
--to=jwfregister@icloud.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).