From: Henning Hraban Ramm <hraban@fiee.net>
Subject: Re: recursion/loop with counter?
Date: Thu, 6 Jan 2005 20:35:19 +0100 [thread overview]
Message-ID: <192E4394-601A-11D9-AD4B-0030659899AA@fiee.net> (raw)
In-Reply-To: <41DD4DFC.4070206@wxs.nl>
Am 06.01.2005 um 15:41 schrieb Hans Hagen:
> \dorecurse{20}
> {\bTR \expanded{\bTD \recurselevel bottles of beer \eTD} \bTD \strut
> \eTD \eTR}
But what if I need it in a call to some function like:
\dorecurse{10}{\SkillField{Skill\expanded\recurselevel}}
Then I always get 0 (or an error in some cases).
Grüßlis vom Hraban!
---
http://www.fiee.net/texnique/
http://contextgarden.net
next prev parent reply other threads:[~2005-01-06 19:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 13:25 Henning Hraban Ramm
2005-01-06 13:38 ` Vit Zyka
2005-01-06 14:41 ` Hans Hagen
2005-01-06 19:35 ` Henning Hraban Ramm [this message]
2005-01-07 8:42 ` Hans Hagen
2005-01-07 10:52 ` m-letter Rob Ermers
2005-01-07 11:06 ` m-letter Taco Hoekwater
2005-01-07 14:12 ` m-letter Rob Ermers
2005-01-10 22:53 ` m-letter John Culleton
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=192E4394-601A-11D9-AD4B-0030659899AA@fiee.net \
--to=hraban@fiee.net \
--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).