From: Hans Hagen <pragma@wxs.nl>
Subject: Re: \stopbuffer in macro
Date: Thu, 02 Jun 2005 22:41:42 +0200 [thread overview]
Message-ID: <429F6F06.4070406@wxs.nl> (raw)
In-Reply-To: <429F4182.3080208@elvenkind.com>
I once made the option
\usememorybuffers
but i'm not sure if it does the same
====
Taco Hoekwater wrote:
> This should help:
>
> \def\startLST[#1]%
> {\def\stopLST{End of #1}%
> \dostartbuffer[LST][startLST][stopLST]}
>
> This is almost the same as:
>
> \definebuffer[LST]
> \def\stopLST{End of LST}
>
> Except that it is a little bit more low-level and thereby allows
> an argument to \startLST. Using a local definition if \stopLST
> is another trick, to lift the argument to the end of the buffer.
>
> A less sophisticated but clearer approach is:
>
> \def\startLST[#1]%
> {\def\LSTArgs{#1}%
> \dostartbuffer[LST][startLST][stopLST]}
>
> \def\stopLST{End of \LSTArgs}
>
> Full example:
>
> \def\startLST[#1]%
> {\def\stopLST{End of #1}%
> \dostartbuffer[LST][startLST][stopLST]}
>
> \starttext
> \startLST[whatever]
> bla bla
> \stopLST
> alb alb
> \stoptext
>
> You'll have to fill in the commands etc. yourself of course.
>
> Greetings, Taco
>
> Peter Münster wrote:
>
>> On Tue, 31 May 2005, Hans Hagen wrote:
>>
>>
>>> \definebuffer[crap]
>>>
>>> \setupbuffer[crap][before=\blank\bgroup here we start,after=and here
>>> we end\egroup\blank]
>>
>>
>>
>> [...]
>>
>> Hello Hans and Taco,
>> thank you for your hints, but I think, I did not explain my question well
>> enough...
>> I fact, all I need is to know, how I could write some verbatim text
>> between
>> 2 commands (\startXXX...\stopXXX) into a file, but with my own macros.
>> Here an example in detail:
>>
>> \newcount\LSTnum
>> \newwrite\LSTfile
>> \def\LSTfileprefix{\jobname-LST\LSTnum}
>>
>> \def\startLST[#1]#2\stopLST{%
>> \immediate\openout\LSTfile=\LSTfileprefix.tmp
>> \immediate\write\LSTfile{#2}% Here I seek a solution for verbatim
>> text!
>> \immediate\closeout\LSTfile
>> \immediate\write18{createListing.sh \LSTfileprefix #1}% #1 is for
>> \lstset
>> \externalfigure[\LSTfileprefix]
>> \advance\LSTnum by 1
>> }
>>
>> and then, the user types only:
>>
>> \startLST[language=C]
>> main()
>> {
>> return 0;
>> }
>> \stopLST
>>
>> It's already possible to do this with some further macros (\finishLST
>> after
>> \stopLST for example), but I prefer only one \start/\stop pair.
>>
>> Greetings, Peter
>>
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
>
>
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2005-06-02 20:41 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
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 [this message]
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=429F6F06.4070406@wxs.nl \
--to=pragma@wxs.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).