From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Some problems with framing typed text.
Date: Tue, 10 Aug 2004 20:48:16 +0200 [thread overview]
Message-ID: <41191870.1030705@wxs.nl> (raw)
In-Reply-To: <351383E8-EAF7-11D8-B138-0030659899AA@fiee.net>
Henning Hraban Ramm wrote:
>
> Am 10.08.2004 um 19:30 schrieb Brooks Moses:
>
>> In the document I'm working on, I'd like to put some typed code bits
>> in frames, to get an appearance sort of like the code excerpts on the
>> ConTeXtWiki. However, I've found myself needing to do a couple of
>> rather ugly hacks to get that to work right, and I'm hoping for some
>> suggestions on how to avoid that.
>
>
> Did you try something like:
>
> \setupbackground[background=screen, frame=on, color=blue]
> \setuptyping[before=\startbackground, after=\stopbackground]
>
> \starttyping
> bla bla
> \stoptyping
or:
\starttext
\defineframedtext
[myframed]
[background=color,
backgroundcolor=gray,
frame=on,
strut=yes,
offset=2mm,
width=broad,
framecolor=black,
align=right]
\definetyping[mytyping]
\setuptyping
[before=\startmyframed,
after=\stopmyframed]
\startmytyping
This is an example.
\stopmytyping
\stoptext
-----------------------------------------------------------------
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:[~2004-08-10 18:48 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-10 17:30 Brooks Moses
2004-08-10 18:00 ` Henning Hraban Ramm
2004-08-10 18:47 ` Brooks Moses
2004-08-10 19:04 ` Hans Hagen
2004-08-10 20:35 ` no graph after compilation Floris van Manen
2004-08-11 12:55 ` Peter Rolf
2004-08-11 13:38 ` Re[2]: " Floris van Manen
2004-08-11 14:00 ` Vit Zyka
2004-08-11 14:09 ` Re[2]: " Floris van Manen
2004-08-11 14:21 ` Patrick Gundlach
2004-08-11 14:44 ` Re[2]: " Floris van Manen
2004-08-11 15:07 ` Patrick Gundlach
2004-08-11 15:14 ` Patrick Gundlach
2004-08-11 15:24 ` Re[2]: " Floris van Manen
2004-08-11 15:34 ` Patrick Gundlach
2004-08-11 15:57 ` Re[2]: " Floris van Manen
2004-08-11 16:38 ` Patrick Gundlach
2004-08-11 18:03 ` Re[2]: " Floris van Manen
2004-08-11 18:17 ` Patrick Gundlach
2004-08-11 22:17 ` Re[2]: " Floris van Manen
2004-08-12 7:47 ` Patrick Gundlach
2004-08-12 8:05 ` Eros Albertazzi
2004-08-12 11:30 ` Re[2]: " Floris van Manen
2004-08-12 11:03 ` Vit Zyka
2004-08-12 11:29 ` Re[2]: " Floris van Manen
2004-08-12 19:26 ` Patrick Gundlach
2004-08-12 22:02 ` Hans Hagen
2004-08-12 23:32 ` Re[2]: getting context going Floris van Manen
2004-08-12 23:48 ` Hans Hagen
2004-08-13 8:24 ` Patrick Gundlach
2004-08-13 12:29 ` Re[2]: getting context going --> feature tool request Floris van Manen
2004-08-12 7:25 ` no graph after compilation Hans Hagen
2004-08-12 11:06 ` Re[2]: " Floris van Manen
2004-08-12 7:13 ` Hans Hagen
2004-08-12 7:42 ` Patrick Gundlach
2004-08-11 16:00 ` Vit Zyka
2004-08-11 16:30 ` Patrick Gundlach
2004-08-11 17:14 ` Re[2]: " Peter Münster
2004-08-10 18:48 ` Hans Hagen [this message]
2004-08-10 19:21 ` Some problems with framing typed text Brooks Moses
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=41191870.1030705@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).