From: Hans Hagen <pragma@wxs.nl>
Subject: Re: doifempty
Date: Thu, 10 Aug 2006 09:19:26 +0200 [thread overview]
Message-ID: <44DADDFE.1020603@wxs.nl> (raw)
In-Reply-To: <44DAD222.9090908@militzer.net>
Bernd Militzer wrote:
> Hi all,
>
> after I defined
>
> \def\VariA{}
> \def\VariB{with Text}
>
> \doifemptyelse{\VariA}{empty}{not empty}\crlf
> \doifemptyelse{\VariB}{empty}{not empty}
>
> both results are "not empty"!
>
the empty test is kind of special, use \doifelsenothing cum suis
> what do I wrong?
>
> thanks for help
>
> Bernd
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2006-08-10 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 6:28 doifempty Bernd Militzer
2006-08-10 7:19 ` Hans Hagen [this message]
2006-08-10 7:38 ` doifempty Bernd Militzer
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=44DADDFE.1020603@wxs.nl \
--to=pragma@wxs.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).