From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \do(single|double|etc)empty behaviour
Date: Wed, 15 Dec 2010 23:56:03 +0100 [thread overview]
Message-ID: <37DA1975-1BCE-4922-A72E-4005474CC3CE@gmail.com> (raw)
In-Reply-To: <87fwtyj2w4.fsf@universe.krase.net>
Am 15.12.2010 um 19:40 schrieb Marco Pessotto:
>
> Hello there.
>
> I was writing a small macro to emulate a custom \part command, and I
> broke my head against \dosingleempty (but finally I won).
>
> […]
>
> It's unclear to me how the arguments are passed between macros.
> Probably it's just a matter of knowledge of TeX macro programming (which
> obviously I don't have).
Your test with \iffirstargument fails because you perform it after \startalignment
which has itself a argument which sets \iffirstargument to true, a better way to
check for content of the optional argument is \doifsomethingelse.
\def\talpart
{\dosingleempty\dotalpart}
\def\dotalpart[#1]#2%
{\page[right]
\blank[force,2*big]
\startalignment[center]
\doifsomethingelse{#1}
{{\bfc#1}\writetolist[talpart]{}{#1. #2}}
{\writetolist[talpart]{}{#2}}%
\blank[2*big]
{\bfd#2}
\stopalignment
\page[left]}
Wolfgang
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-12-15 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 18:40 Marco Pessotto
2010-12-15 22:56 ` Wolfgang Schuster [this message]
2010-12-15 23:31 ` Marco Pessotto
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=37DA1975-1BCE-4922-A72E-4005474CC3CE@gmail.com \
--to=schuster.wolfgang@googlemail.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).