From: Rik Kabel <ConTeXt@rik.users.panix.com>
To: ntg-context@ntg.nl
Subject: Re: Color problem
Date: Fri, 21 May 2021 09:52:27 -0400 [thread overview]
Message-ID: <0f760048-b24f-a8e5-33bc-c573dda7beba@rik.users.panix.com> (raw)
In-Reply-To: <e47d33be-8254-4e37-824a-0514e12a2651@gmail.com>
On 5/21/2021 00:26, Wolfgang Schuster wrote:
> Aditya Mahajan schrieb am 21.05.2021 um 04:47:
>> On Thu, 20 May 2021, Rik Kabel wrote:
>>
>>> Consider the following example:
>>>
>>> \define \HighlightColor {red}
>> Why not just use:
>>
>> \definecolor[HighlightColor][red]
>>
>> and then use color=HighlightColor, etc.
>
> This is the better way to create unique color names but the problem
> in the example was the use of \define instead of \defineexpandable.
>
> \defineexpandable\HighlightColor{red}
>
> Wolfgang
>
Wolfgang and Aditya,
Thank you both for the lesson.
Is the difference between MkIV (--luatex) and LMTX due to stricter
application of expandability in LMTX?
--
Rik
___________________________________________________________________________________
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-05-21 13:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 2:33 Rik Kabel
2021-05-21 2:47 ` Aditya Mahajan
2021-05-21 4:26 ` Wolfgang Schuster
2021-05-21 13:52 ` Rik Kabel [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-01 18:55 color problem Susanne G. Loeber
2020-10-02 7:10 ` Taco Hoekwater
2020-10-02 12:14 ` Henri Menke
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=0f760048-b24f-a8e5-33bc-c573dda7beba@rik.users.panix.com \
--to=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).