From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: xtables in custom macros
Date: Thu, 3 Nov 2011 20:44:57 +0100 [thread overview]
Message-ID: <C0EA7DE6-5E85-4681-91EE-3EF50B1825C7@googlemail.com> (raw)
In-Reply-To: <20111103193727.232750@gmx.net>
Am 03.11.2011 um 20:37 schrieb Stefan Müller:
> Hi list,
>
> I just played a bit with the nice new xtables. It seems as if "\stopxtable" does not work if used inside a custom macro. I get a "Runaway argument" error with the current standalone if I uncomment "\Doesnt" in the following example.
>
> \define\Works{\startxtable \startxrow \startxcell works \stopxcell \stopxrow}
> \define\Doesnt{\startxtable \startxrow \startxcell does not work \stopxcell \stopxrow \stopxtable}
>
> \starttext
> \Works \stopxtable
> %\Doesnt
> \stoptext
>
> Did I miss something or is this a bug?
The stable environment stores the content in a buffer and you can’t
put the start and stop commands of a buffer in different commands.
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:[~2011-11-03 19:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 19:37 "Stefan Müller"
2011-11-03 19:44 ` Wolfgang Schuster [this message]
2011-11-03 22:01 ` "Stefan Müller"
2011-11-04 9:38 ` Hans Hagen
2011-11-04 10:11 ` Thomas A. Schmitz
2011-11-04 12:48 ` Hans Hagen
2011-11-04 21:44 ` Thomas A. Schmitz
2011-11-06 9:43 ` Thomas A. Schmitz
2011-11-04 17:18 ` "Stefan Müller"
2011-11-04 17:47 ` Hans Hagen
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=C0EA7DE6-5E85-4681-91EE-3EF50B1825C7@googlemail.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).