From: "Meer, Hans van der" <H.vanderMeer@uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: \doiftext vs. \doifemtpy
Date: Thu, 14 Jan 2016 10:46:04 +0000 [thread overview]
Message-ID: <C8B1A0E5-6826-46C8-BA87-68160CD3CDC9@uva.nl> (raw)
In-Reply-To: <20160114084144.10b57289@homerow>
[-- Attachment #1.1: Type: text/plain, Size: 1644 bytes --]
Watch out. There is a pitfall here (yes, I have fallen in this trap).
Try \type{\doifempty{\empty}{yes}} = <\doifempty{\empty}{yes}>\crlf
and you will see that it is NOT empty despite the suggestive use of the \empty macro!
Hans van der Meer
On 14 Jan 2016, at 08:41, Marco Patzer <lists@homerow.info<mailto:lists@homerow.info>> wrote:
On Wed, 13 Jan 2016 23:18:03 +0100
Pablo Rodriguez <oinos@gmx.es<mailto:oinos@gmx.es>> wrote:
which is the difference between \doiftext and \doifempty?
First of all, the logic is reversed, \doiftext prints the second
argument if the first one contains text, \doifempty does print the
second argument if the first one *does not* contain anything. You can
get around this by using the \…else versions.
Then, the major difference is that \doifempty checks if the argument
is empty and nothing else. \doiftext checks if it contains a box of
non-zero width.
\starttext
text: \doiftextelse{foo}{is text}{no text}\par
text: \doifemptyelse{foo}{is empty}{not empty}\par
empty: \doiftextelse{}{is text}{no text}\par
empty: \doifemptyelse{}{is empty}{not empty}\par
space: \doiftextelse{\space}{is text}{no text}\par
space: \doifemptyelse{\space}{is empty}{not empty}\par
zero width: \doiftextelse{\framed[width=0cm]{frame}}{is text}{no text}\par
zero width: \doifemptyelse{\framed[width=0cm]{frame}}{is empty}{not empty}\par
image: \doiftextelse{\externalfigure[cow]}{is text}{no text}\par
image: \doifemptyelse{\externalfigure[cow]}{is empty}{not empty}\par
\stoptext
Marco
________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 2816 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2016-01-14 10:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 22:18 Pablo Rodriguez
2016-01-14 7:41 ` Marco Patzer
2016-01-14 10:46 ` Meer, Hans van der [this message]
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=C8B1A0E5-6826-46C8-BA87-68160CD3CDC9@uva.nl \
--to=h.vandermeer@uva.nl \
--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).