From: WolfgangZ <wollez@gmx.net>
To: ntg-context@ntg.nl
Subject: Re: additional blank line in starttyping environment
Date: Sun, 15 Jul 2007 21:56:18 +0200 [thread overview]
Message-ID: <f7du53$t4d$2@sea.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707152000060.29497@gaston.couberia.bzh>
Peter Münster schrieb:
> On Sun, 15 Jul 2007, WolfgangZ wrote:
>
>> I get an extra blank line at the beginning of the starttyping
>> environment. How do I get rid of it?
>
> The cause of the problem seems to be the "align=flushleft".
> Workaround: \vskip-\lineheight
>
> Minimal example, showing the problem and the workaround:
>
> \setupcolors[state=start]
> \setuptyping[before=,after=]
> \startbuffer
> BYTEORDER M
> \stopbuffer
> \starttext
> \framed[background=color,backgroundcolor=red]{\typebuffer}
> \framed[align=flushleft,background=color,backgroundcolor=red]{\typebuffer}
> \framed[align=flushleft,background=color,backgroundcolor=red]{%
> \vskip-\lineheight\typebuffer}
> \stoptext
>
> Cheers, Peter
>
It seemd that I needed align=flushleft to get the lines of the buffer
correctly and not without any line break at all.
Many thanks for your help
Wolfgang
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2007-07-15 19:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 15:45 WolfgangZ
2007-07-15 15:57 ` Thomas A. Schmitz
2007-07-15 18:49 ` Peter Münster
2007-07-15 19:56 ` WolfgangZ [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='f7du53$t4d$2@sea.gmane.org' \
--to=wollez@gmx.net \
--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).