From: Bruce Horrocks via ntg-context <ntg-context@ntg.nl>
To: ntg-context mailing list <ntg-context@ntg.nl>
Cc: Bruce Horrocks <ntg@scorecrow.com>
Subject: Re: Problem with \stoptabulate
Date: Tue, 21 Mar 2023 11:06:30 +0000 [thread overview]
Message-ID: <AAE688A4-23AE-46C2-BE84-A7D85D421C10@scorecrow.com> (raw)
In-Reply-To: <57b95a90-5456-93ed-f778-ee229cde7651@gmail.com>
Thanks Julian - I tried a startstop environment originally but it didn't work.
The answer turns out to be trivial - just needed to use \long\def for \stoptabulate so the following appears to work:
\def\startMyExample{\starttabulate[|r|c|l|p|]}
\long\def\stopMyExample{\stoptabulate} %% long def required here
\def\MyExampleItem#1#2#3{\NC #1 \NC \rightarrow \NC #2 \NC #3 \NC\NR}
\starttext
Here are some examples...
\startMyExample
\MyExampleItem{before}{after}{change before into after}
\MyExampleItem{straw}{gold}{Rumpelstiltskin}
\stoptabulate
\stoptext
> On 21 Mar 2023, at 05:23, jbf via ntg-context <ntg-context@ntg.nl> wrote:
>
> Not sure if this helps, Bruce, but there is \definestartstop
>
> Julian
>
> On 21/3/23 10:34, Bruce Horrocks via ntg-context wrote:
>> I have a technical manual style document that requires a lot of examples to be included.
>>
>> They can easily be typeset with a table so I thought I would save myself some typing by defining macros for the various bits of a tabulate table. Thus I have:
>>
>> \def\startMyExample{\starttabulate[|r|c|l|p|]}
>> \def\stopMyExample{\stoptabulate}
>> \def\MyExampleItem#1#2#3{\NC #1 \NC \rightarrow \NC #2 \NC #3 \NC\NR}
>>
>> \starttext
>> Here are some examples...
>>
>> \startMyExample
>> \MyExampleItem{before}{after}{change before into after}
>> \MyExampleItem{straw}{gold}{Rumpelstiltskin}
>> \stopMyExample
>> %\stoptabulate
>>
>> \stoptext
>>
>> The problem is that \stopMyExample doesn't work - the \stoptabulate isn't recognised and I get an end of file reached error. If use a straight \stoptabulate then it works as expected. That's fine but it would be nice, from an aesthetic point of view, to have start & stop 'paired' commands in the source.
>>
>> Presumably some sort of deep ConTeXt fu is going on - can anyone explain it please?
>>
>> Regards,
>> —
>> Bruce Horrocks
>> Hampshire, UK
—
Bruce Horrocks
Hampshire, UK
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-03-21 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 23:34 Bruce Horrocks via ntg-context
2023-03-21 5:23 ` jbf via ntg-context
2023-03-21 11:06 ` Bruce Horrocks via ntg-context [this message]
2023-03-21 11:32 ` Bruce Horrocks via ntg-context
2023-03-21 8:35 ` Hans Hagen via ntg-context
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=AAE688A4-23AE-46C2-BE84-A7D85D421C10@scorecrow.com \
--to=ntg-context@ntg.nl \
--cc=ntg@scorecrow.com \
/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).