From: John Culleton <john@wexfordpress.com>
Subject: Re: verbatim problem
Date: Tue, 27 Apr 2004 07:53:20 -1000 [thread overview]
Message-ID: <200404270753.20710.john@wexfordpress.com> (raw)
In-Reply-To: <20040422185559.9ECCA10B6A@ref.ntg.nl>
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.
--
John Culleton
Able Typesetters and Indexers
http://wexfordpress.com
next prev parent reply other threads:[~2004-04-27 17:53 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 [this message]
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=200404270753.20710.john@wexfordpress.com \
--to=john@wexfordpress.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).