From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: troubles with \enablemode
Date: Fri, 30 Oct 2020 14:49:17 -0400 (EDT) [thread overview]
Message-ID: <nycvar.YAK.7.78.908.2010301444460.3664@nqv-guvaxcnq> (raw)
In-Reply-To: <20201030182634.GA32435@valencay.home>
On Fri, 30 Oct 2020, Damien Thiriet wrote:
> Hi @list,
>
>
> I don't fully understand the \enablemode mechanism. Given this MWE:
>
>
> \startmode[test]
> \setupframedtext [foregroundcolor=white,style={\tfa}]
> \stopmode
>
>
> \starttext
> \startframedtext
> ceci est un texte
> \stopframedtext
> \enablemode [test]
> \startframedtext
> ceci est un texte
> \stopframedtext
> \stoptext
>
> I cannot see the expected effect when I compile, that is both texts are
> in black. When I compile with
> context --mode=test
> both framed texts are in white, which is what I expect.
>
> What did I miss?
When the compilation starts and context reads the line \startmode[test], the mode is not enabled, so the rest of the block is discarded. When you get to do enable the mode, it is too late. TeX does not do backtracking while compiling a document. Depending on what exactly you want, you could use:
\startsetups[test]
....
\stopsetups
...
\setups{test}
....
Or perhaps even (untested)
\setupframedtext[foregroundcolor={\doifmode{test}{white}}, style={\tfa}]
Aditya
___________________________________________________________________________________
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:[~2020-10-30 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 18:26 Damien Thiriet
2020-10-30 18:39 ` Henning Hraban Ramm
2020-10-30 18:49 ` Aditya Mahajan [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=nycvar.YAK.7.78.908.2010301444460.3664@nqv-guvaxcnq \
--to=adityam@umich.edu \
--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).