From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl, roegel@lorraine.loria.fr
Subject: Re: \definestartstop problem
Date: Mon, 27 May 2002 22:27:27 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20020527222624.03a3aed8@server-1> (raw)
In-Reply-To: <200205230401.GAA25430@bar.loria.fr>
At 06:01 AM 5/23/2002 +0200, Denis B. Roegel wrote:
>When trying the following example
>
>\definestartstop
> [stars]
> [commands={\inleft{\hbox to
> \leftmarginwidth{\leaders\hbox{$\stars$}\hfill}}},
> before=\blank,
> after=\blank]
>
>
>\startstars
>{\em Hasselter Juffers} are sweet cookies but the name is no
>coincidence. On July 21 in 1233 the {\em Zwartewaterklooster}
>(Blackwater Monastery) was founded. The monastery was meant
>for unmarried girls and women belonging to the nobility of Hasselt.
>These girls and women were called {\em juffers}.
>\stopstars
>
>
>I obtained:
>
>! TeX capacity exceeded, sorry [grouping levels=255].
>\next ... \hsize \!!widtha \raggedcommand \bgroup
Well, this on eis no bug, you use \stars (plural instead of \star) and
\definestartstop also defines \stars, so you nest the commands.
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2002-05-27 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-23 4:01 Denis B. Roegel
2002-05-27 20:27 ` Hans Hagen [this message]
2002-05-28 3:01 ` Denis B. Roegel
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=5.1.0.14.1.20020527222624.03a3aed8@server-1 \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=roegel@lorraine.loria.fr \
/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).