From: "Meer, Hans van der" <H.vanderMeer@uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: new features
Date: Sun, 22 May 2016 13:33:36 +0000 [thread overview]
Message-ID: <B5F96181-6780-4936-B993-6572C242073E@uva.nl> (raw)
In-Reply-To: <38152b3e-6feb-42c0-9bf9-ef9ab8b9d0c1@wxs.nl>
[-- Attachment #1.1: Type: text/plain, Size: 772 bytes --]
On 22 May 2016, at 15:11, Hans Hagen <pragma@wxs.nl<mailto:pragma@wxs.nl>> wrote:
Finally, when \definemode makes testing a lot faster why than not implement this always? That is, using \enablemode or \disablemode the first time implies a \definemode for that mode. Doing so avoids another macro to remember: less clutter for my brain ;-)
because one property of modes is that one doesn't have to define them, you'd be quite unhappy if you would have to define all possible modes that could be introduced in styles
The idea was not to have the user define the mode, but let ConTeXt automatically do the defining when it encounters a specific mode the first time. The work is done by ConTeXt then (would make me even more happy ;-)
Hans van der Meer
[-- Attachment #1.2: Type: text/html, Size: 2708 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2016-05-22 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 10:08 Hans Hagen
2016-05-22 8:07 ` Meer, Hans van der
2016-05-22 13:11 ` Hans Hagen
2016-05-22 13:33 ` Meer, Hans van der [this message]
2016-05-22 13:59 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
1999-08-13 8:13 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=B5F96181-6780-4936-B993-6572C242073E@uva.nl \
--to=h.vandermeer@uva.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).