From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: \stopbuffer in macro
Date: Mon, 30 May 2005 23:50:56 +0200 [thread overview]
Message-ID: <429B8AC0.3020503@elvenkind.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0505302140510.25025@gaston.free.fr>
Peter Münster wrote:
> Hello,
>
> how could I build some macros, that make usage of \startbuffer and
> \stopbuffer?
> Example:
> \def\startXXX[#1]{\doSomeMagicSetups{#1}%
> \startbuffer[...]}
> \def\stopXXX{\stopbuffer
> \doSomeSpecialWorkHere}
> And then:
> \startXXX[some options]
> some text
> \stopXXX
I hope this helps:
%%%%%%%%%%%%%%%%%% buf.tex
% use colors
\setupcolors[state=start]
% this defines a new type of buffer called XXX, so that
% the commands \startXXX ... \stopXXX, \getXXX and
% \typeXXX are now defined
\definebuffer[XXX]
% two sentinel definitions are placed before and after
% the actual buffer content, as fetched by \getXXX
\setupbuffer[XXX][before={\beforeXXX},after={\afterXXX}]
% Do not call \getXXX directly, but use a special
% command to pass options to \beforeXXX and \afterXXX
\def\finishXXX{\dosingleempty\dofinishXXX}
\def\dofinishXXX[#1]{{\getparameters[XXX][Color=green,#1]\getXXX }}
% within the next commans, there is now a set if parameters
% starting with \XXX, initialized by the \getparameters
% call in the macro above.
\def\beforeXXX{\startcolor[\XXXColor]}
\def\afterXXX{\stopcolor}
% below here is an example
\starttext
\startXXX
Here is some text
\stopXXX
\finishXXX % defaults to using green text.
\finishXXX[Color=blue] % same text, but in blue
\stoptext
%%%%%%%%%%%%%%%%%%% buf.tex
next prev parent reply other threads:[~2005-05-30 21:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 19:51 Peter Münster
2005-05-30 21:50 ` Taco Hoekwater [this message]
2005-05-30 22:09 ` Hans Hagen
2005-06-02 16:08 ` Peter Münster
2005-06-02 17:27 ` Taco Hoekwater
2005-06-02 20:41 ` Hans Hagen
2005-06-03 19:48 ` Peter Münster
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=429B8AC0.3020503@elvenkind.com \
--to=taco@elvenkind.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).