From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Rik Kabel <ConTeXt@rik.users.panix.com>
Subject: Re: LMTX MkIV difference in expansion
Date: Fri, 20 Nov 2020 08:53:43 +0100 [thread overview]
Message-ID: <52e7347d-fb7a-004e-9272-8e8f79ff1fd0@xs4all.nl> (raw)
In-Reply-To: <cb80e224-de97-b972-ca40-f1445ae5d598@rik.users.panix.com>
On 11/20/2020 12:18 AM, Rik Kabel wrote:
> You are right about not quite understand.
>
> Does this mean that I can have the same definitions in MkIV and LMTX
> (after some future update), or should I hunt down the \defines in both,
> or that I should fork (or mode test) my source environment files, one
> set for LMTX and one for MkIV?
Kind of
\protected\def\MyCommand#1{\tricky{?}\stuff{!}}
\def\MyKeyword{tricky stuff}
because you want to always expand MyKeyword and in controlled cases
\MyCommand.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2020-11-20 7:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 20:20 Rik Kabel
2020-11-19 20:41 ` Wolfgang Schuster
2020-11-19 22:03 ` Hans Hagen
2020-11-19 23:18 ` Rik Kabel
2020-11-20 7:53 ` Hans Hagen [this message]
2020-11-21 15:05 ` Wolfgang Schuster
2020-11-21 15:25 ` Rik Kabel
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=52e7347d-fb7a-004e-9272-8e8f79ff1fd0@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ConTeXt@rik.users.panix.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).