From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Testing for LMTX: \ifmode
Date: Sun, 25 Jul 2021 09:46:18 +0200 [thread overview]
Message-ID: <d63646b6-8d71-f70d-4e50-ca118c999238@gmail.com> (raw)
In-Reply-To: <623E1E52-2E4A-4655-B714-6D4EF4492FC4@axelkielhorn.de>
Axel Kielhorn schrieb am 25.07.2021 um 09:06:
> Hi,
>
> I have a document that doesn’t work with LMTX right now.
>
> While testing LMTX I would like to exclude certain passages and work on them later.
>
> When I run the following:
>
> \doifmode{*mkiv}{mkiv}
> \doifmode{*contextlmtxmode}{contextlmtx}
> \doifmode{*lmtx}{lmtx}
>
> I always get „mkiv“.
> I’ve tried
>
> - pre LMTX context
> - LMTX --luatex
> - LMTX (2021.07.23)
>
> What is the recommended way to detect LMTX?
There is no mode value for LMTX, only MkIV is set. To check for LMTX
you have to use \ifcase\contextlmtxmode but an additional for lmtx
would be useful.
\starttext
\ifcase\contextlmtxmode
\MKIV
\else
\MKIV\ + \LMTX
\fi
\stoptext
Wolfgang
___________________________________________________________________________________
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 prev parent reply other threads:[~2021-07-25 7:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-25 7:06 Axel Kielhorn
2021-07-25 7:46 ` Wolfgang Schuster [this message]
2021-07-25 10:17 ` Hans Hagen
2021-07-25 10:43 ` Axel Kielhorn
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=d63646b6-8d71-f70d-4e50-ca118c999238@gmail.com \
--to=wolfgang.schuster.lists@gmail.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).