ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \recursestring undefined when inside \dorecurse
Date: Mon, 15 Jun 2020 00:25:06 +0200	[thread overview]
Message-ID: <03d65b46-0bb3-b574-3479-f4a40000184f@xs4all.nl> (raw)
In-Reply-To: <99594972-90e8-67f6-05c8-1d789d3a2935@gmx.es>

On 6/14/2020 11:41 PM, Pablo Rodriguez wrote:
> Dear list,
> 
> I have the following sample:
> 
>      \starttext
>      \dorecurse{25}{\recurselevel\par}
>      \doloopoverstring{a,b,c}{\recursestring}
>      }
>      \stoptext
> 
> Both LMTX and MkIV complain about \recursestring for being undefined.
> 
> I wonder whether this is inteded or it is a bug.

intended, as there is no \doloopoverstring, it's
  \doloopoverlist {red,green,blue} {
     [\recursestring]
}

(btw, you have one } too many)


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2020-06-14 22:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-14 21:41 Pablo Rodriguez
2020-06-14 22:25 ` Hans Hagen [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=03d65b46-0bb3-b574-3479-f4a40000184f@xs4all.nl \
    --to=j.hagen@xs4all.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).