ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Severin Obertüfer" <severinobertuefer@gmx.ch>
Subject: AW: verbatim problem
Date: Thu, 29 Apr 2004 21:55:24 +0200	[thread overview]
Message-ID: <20040429195136.7AC7410B7E@ref.ntg.nl> (raw)
In-Reply-To: <200404270753.20710.john@wexfordpress.com>

 

> -----Ursprüngliche Nachricht-----
> Von: ntg-context-admin@ntg.nl 
> [mailto:ntg-context-admin@ntg.nl] Im Auftrag von John Culleton
> Gesendet: Dienstag, 27. April 2004 19:53
> An: ntg-context@ntg.nl; Severin Obertüfer
> Betreff: Re: [NTG-context] verbatim problem
> 
> On Thursday 22 April 2004 08:59 am, 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:
> 
> Similarly I needed to have the program obey line breaks as in 
> \obeylines but interpet the lines (font changes etc.) in the 
> usual way. I did not want space left between lines. 
> Neither the plain TeX nor the Context solutions fit this 
> purpose exactly, but plain was closer. So I cobbled up this
> code:
> \def\startobey{\medskip\setupwhitespace[none]\obeylines}
> \def\stopobey{\setupwhitespace[small] \medskip}
> 
> I start the section needing verbatim line endings with 
> {\startobey .... and end it with \stopobey}
> 
> I don't know if the braces are necessary but the TeXBook 
> seems to imply such.
> 
> My solution tends to ignore blank lines so I have to put a 
> \medskip instead of a blank line.
> 
> This is a terrible solution but the best I could come up with 
> in a hurry. No doubt someone will suggest a better one. 
> 
> BTW whre is \startEIFFEL documented? I don't recall seeing it 
> before. 
hi
there is the file "verb-eif.tex" in "texmf/tex/context/base" (under miktex)
otherwise i found no other documentation...

severin
> --
> John Culleton
> Able Typesetters and Indexers
> http://wexfordpress.com
> 
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
> 
> 

      parent reply	other threads:[~2004-04-29 19:55 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
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   ` Severin Obertüfer [this message]

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=20040429195136.7AC7410B7E@ref.ntg.nl \
    --to=severinobertuefer@gmx.ch \
    --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).