From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to start the demo in modules
Date: Mon, 30 May 2016 18:59:38 +0200 [thread overview]
Message-ID: <b382226e-8c5f-26d6-266e-272873ef947a@wxs.nl> (raw)
In-Reply-To: <CALBOmsbSxeHQfOYqurmnAFvGHpOrVg=OhZxC4xDjceq9pqOJQA@mail.gmail.com>
On 5/30/2016 1:16 PM, Mojca Miklavec wrote:
> Hi,
>
> MKII uses
> \doifnotmode{demo}{\endinput}
> to enter the demo mode in modules.
>
> I see that MKIV now switched to
> \continueifinputfile{s-something.mkiv}
>
>
> The question arises: What should I suggest to a module writer for a
> relatively simple file that doesn't use any MKIV features and provides
> just the module file t-something.tex?
>
> Is it OK to keep using "\doifnotmode{demo}{\endinput}" also in MKIV?
sure but \continueifinputfile is easier as you then can just process the
(module) file directly without bothering about a mode (and a potential
clash)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | 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:[~2016-05-30 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 11:16 Mojca Miklavec
2016-05-30 16:59 ` 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=b382226e-8c5f-26d6-266e-272873ef947a@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).