On 11/21/2020 10:05, Wolfgang Schuster wrote:
Rik Kabel schrieb am 20.11.2020 um 00:18:
You are right about not quite understand.
There are cases where you want to pass a command to another command as
it is without replacing it with its content, e.g. when you store the
\TeX logo in the
Rik Kabel schrieb am 20.11.2020 um 00:18:
You are right about not quite understand.
There are cases where you want to pass a command to another command as
it is without replacing it with its content, e.g. when you store the
\TeX logo in the table of content the \TeX command should be
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
On 11/19/2020 17:03, Hans Hagen wrote:
On 11/19/2020 9:41 PM, Wolfgang Schuster wrote:
Rik Kabel schrieb am 19.11.2020 um 21:20:
Another LMTX/MkIV difference, this time with expansion:
\define\Align{yes}
\starttext
\startalignment[\Align]
This works with MkIV but fails
On 11/19/2020 9:41 PM, Wolfgang Schuster wrote:
Rik Kabel schrieb am 19.11.2020 um 21:20:
Another LMTX/MkIV difference, this time with expansion:
\define\Align{yes}
\starttext
\startalignment[\Align]
This works with MkIV but fails with LMTX, complaining: {\tt
tex
Rik Kabel schrieb am 19.11.2020 um 21:20:
Another LMTX/MkIV difference, this time with expansion:
\define\Align{yes}
\starttext
\startalignment[\Align]
This works with MkIV but fails with LMTX, complaining: {\tt
tex error on line 3 in file G:/expand.mkvi: The file
