From: Andreas Harder <aharder@uni-koblenz.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug or feature?
Date: Wed, 21 Dec 2011 12:50:18 +0100 [thread overview]
Message-ID: <A36BE09A-80F4-4871-AF5F-7D79D3275AE7@uni-koblenz.de> (raw)
In-Reply-To: <7448D80B-F3E2-4FEB-9AD8-98352CCAA8B6@googlemail.com>
On 21.12.2011, at 12:33, Wolfgang Schuster wrote:
>
> Am 21.12.2011 um 12:04 schrieb Andreas Harder:
>
>> Hi,
>>
>> with the latest beta there is always a line break after a \blackrule … bug or feature?
>>
>> \starttext
>> % \dontleavehmode%
>> \blackrule[width=3cm] unwanted line break!
>> \stoptext
>
> It’s neither a bug nor a feature, just a result of TeX’s horizontal and vertical modes, the same happens when you use \framed in vertical mode.
>
> \starttext
> \framed{line 1}
> \framed{line 2}
> \stoptext
Yes, you are right. My example was too minimal. I used \defineheadplacement and since yesterdays beta the line break is introduced.
\starttext
\defineheadplacement[MyPlacement][vertical]
{\vbox{\localheadsetup\begstrut\blackrule[width=3cm] #2}}
\setuphead[subject][alternative=MyPlacement]
\subject{test Äg}
\stoptext
Andreas
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2011-12-21 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 11:04 Andreas Harder
2011-12-21 11:33 ` Wolfgang Schuster
2011-12-21 11:50 ` Andreas Harder [this message]
2011-12-21 14:02 ` Wolfgang Schuster
2011-12-21 22:38 ` Hans Hagen
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=A36BE09A-80F4-4871-AF5F-7D79D3275AE7@uni-koblenz.de \
--to=aharder@uni-koblenz.de \
--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).