From: Tobias Burnus <tobias.burnus@physik.fu-berlin.de>
Subject: Re: AW: verbatim problem
Date: Thu, 22 Apr 2004 22:46:27 +0200 [thread overview]
Message-ID: <40882F23.8010500@physik.fu-berlin.de> (raw)
In-Reply-To: <20040422195839.C616A10AFA@ref.ntg.nl>
Hello again,
Severin Obertüfer wrote:
>>Did you think of putting the information into a buffer and
>>put the contents in your document with \typebuffer?
>>
>>
>\startbuffer [deque]
>[...]
>\stopbuffer
>
>\startEIFFEL
> \typebuffer[deque]
>\stopEIFFEL
>
>
I thought you ment a file, for a buffer one can use, analogously,
\typebuffer[EIFFEL][deque]
Regards,
Tobias
next prev parent reply other threads:[~2004-04-22 20:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 18:59 Severin Obertüfer
2004-04-22 19:51 ` Willi Egger
2004-04-22 20:02 ` AW: " Severin Obertüfer
2004-04-22 20:46 ` Tobias Burnus [this message]
2004-04-29 19:44 ` AW: " Severin Obertüfer
2004-04-22 20:43 ` Tobias Burnus
2004-04-27 17:53 ` John Culleton
2004-04-27 13:29 ` Willi Egger
2004-04-28 0:25 ` John Culleton
2004-04-29 19:55 ` AW: " Severin Obertüfer
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=40882F23.8010500@physik.fu-berlin.de \
--to=tobias.burnus@physik.fu-berlin.de \
--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).