From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: \preventmode does not work
Date: Fri, 21 Nov 2014 20:18:24 +0100 [thread overview]
Message-ID: <546F9000.2040400@wxs.nl> (raw)
In-Reply-To: <546CC9CF.7060406@rik.users.panix.com>
On 11/19/2014 5:48 PM, Rik Kabel wrote:
> (This is a bump, with an improved example, of my earlier note on the
> subject.)
>
> In MKIV, \preventmode does not work. It appears to do the opposite of
> what is intended, and enable the specified mode. It also does not
> prevent the explicit enablement of a mode (as can be seen by
> uncommenting the commented line in the MWE).
>
> I have not tested it with MKII , where it might work. (Will ConTeXt
> online ever be restored?)
>
> This goes back to TL14 and likely earlier.
>
> Do I misunderstand what \preventmode should do, or have I misused it?
>
> And why are there {curlies} instead of [squares] around the mode name in
> \doifmode and friends?
>
> MWE, run context MWE.tex:
>
> \starttext
> \preventmode[X]
> %\enablemode[X]
> \doifmode{X}{!}
> \stoptext
fixed in next beta (there was actually a note in the source that it
needed checking)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2014-11-21 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-30 17:58 Rik
2014-11-19 16:48 ` Rik Kabel
2014-11-21 19:18 ` Hans Hagen [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=546F9000.2040400@wxs.nl \
--to=pragma@wxs.nl \
--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).