ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Willi Egger <w.egger@boede.nl>
Subject: Re: verbatim problem
Date: Thu, 22 Apr 2004 21:51:00 +0200	[thread overview]
Message-ID: <40882224.502@boede.nl> (raw)
In-Reply-To: <20040422185559.9ECCA10B6A@ref.ntg.nl>

Hi,

Did you think of putting the information into a buffer and put the 
contents in your document with \typebuffer?

Kind regards Willi

Severin Obertüfer wrote:

> hello 
>  
> i have a little verbatim problem
>  
> i used the \startEIFFEL \stopEIFFEL verbatim environment in a verry simple
> way like this:
>  
> \startEIFFEL
> class
>     DEQUE [G]
>  
>     inherit
>         DOUBLE_LINKED_LIST[G]
>         rename
>             extend as insertRight,
>             prepend as insertLeft
>         end
> create
>     make, make_empty
>  
> feature -- Access
>             
>     -- and so on
> 
> \stopEIFFEL
>  
> now i wanted to make this things a bit more useful and flexible.
>  
> i thougt of something like this
>  
> \startEIFFEL
>     \input deque
> \stopEIFFEL
>  
> but of corse the keyword input is normal text in verbatim mode... :)
> is there a simple solution for that, for example like this
>  
> \startEIFFEL
> \specialcommand{\input deque}
> \stopEIFFEL
> ???
>  
> by the way : can i give as to the inputcommand a argument like this:
>  
> \input D:\Files\ETH\Eiffel\deque.e
>  
> where "deque.e" is a normal eiffel source file....
>  
> thanks for an answer
>  
> mfg
>  
> severin
> 

  reply	other threads:[~2004-04-22 19:51 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 [this message]
2004-04-22 20:02   ` AW: " Severin Obertüfer
2004-04-22 20:46     ` Tobias Burnus
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=40882224.502@boede.nl \
    --to=w.egger@boede.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).