From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: [NTG-context] Re: \doifemptyelse issue?
Date: Mon, 13 Nov 2023 17:21:13 +0100 [thread overview]
Message-ID: <3aca0dea-5b5d-c82e-55b7-ad80a1e09959@gmx.es> (raw)
In-Reply-To: <33A6C923-9BD4-4643-9082-C5768FE4ABC8@scorecrow.com>
On 11/13/23 13:10, Bruce Horrocks wrote:
> The following MWE gives "false false" instead of "false true". I'm
> sure this used to work (18 months or more ago!) as I found it when
> re-processing an old document.> [...]
> There is a work-around using \doiftext instead as that seems to work
> okay with recalled dataset values but I thought I'd raise it.
Hi Bruce,
some time ago Wolfgang explained
(https://mailman.ntg.nl/archives/list/ntg-context@ntg.nl/message/7OO5P34S56RGR5G3K7LXS6DTZWAJGUDZ/):
> \doifempty(else) doesn't expand the argument and any argument counts as
> not empty. To satisfy the command you can expand the first argument
> (\normalexpanded) or you use \doifnothing(else) which expands the argument.
I don’t know whether is what is preveiting your test here, but
\doifnothingelse seems to work fine with your sample.
Just in case it might help,
Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://mailman.ntg.nl/mailman3/lists/ntg-context.ntg.nl
webpage : https://www.pragma-ade.nl / https://context.aanhet.net (mirror)
archive : https://github.com/contextgarden/context
wiki : https://wiki.contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-11-13 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 12:10 [NTG-context] " Bruce Horrocks
2023-11-13 16:21 ` Pablo Rodriguez via ntg-context [this message]
2023-11-14 10:40 ` [NTG-context] " Hans Hagen
2023-11-14 18:02 ` Bruce Horrocks
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=3aca0dea-5b5d-c82e-55b7-ad80a1e09959@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).