From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \blank[inhibit] broken ???
Date: Fri, 25 Jul 2008 10:52:22 +0200 [thread overview]
Message-ID: <3D61AA91-64B5-46A1-BF32-04F69B2C8ABB@st.estfiles.de> (raw)
In-Reply-To: <115224fb0807250139m108e16c4tcaa1660afd106070@mail.gmail.com>
Am 25.07.2008 um 10:39 schrieb Wolfgang Schuster:
> On Fri, Jul 25, 2008 at 10:33 AM, Steffen Wolfrum
> <context@st.estfiles.de> wrote:
>>
>> Am 25.07.2008 um 10:25 schrieb Wolfgang Schuster:
>>
>>> On Fri, Jul 25, 2008 at 10:15 AM, Steffen Wolfrum
>>> <context@st.estfiles.de> wrote:
>>>>
>>>> ... yes, but Hans said so (see my email quoting him)!!!
>>>>
>>>> What did he mean?
>>>> Do you know an other solution?
>>>
>>> \defineblankmethod [nobreak] {\penalty\plustenthousand}
>>> \defineblankmethod [endgraf] {\endgraf}
>>>
>>> \definehead[myhead][section]
>>> \setuphead[myhead][after={\blank[endgraf,nobreak,big]}]
>>>
>>> Not sure about the order in the blank command but this should work.
>>
>> Hmm, I think I have tried all possible combination now but it does
>> not work.
>> Did you try?
>>
>> \starttext
>>
>> \defineblankmethod [nobreak] {\penalty\plustenthousand}
>> \defineblankmethod [endgraf] {\endgraf}
>>
>> \definehead[myhead][section]
>> \setuphead[myhead][after={\blank[nobreak,endgraf,big]}]
>>
>> \input tufte \par
>> \input knuth \par
>> \input tufte \par
>> \input knuth \par
>>
>> \myhead{Sektion}
>>
>> \index{Index}
>>
>> test
>>
>> \stoptext
>>
>> Steffen
>
> You're looking for http://wiki.contextgarden.net/Registers#Technical_note
ok, but this was just one easily reproducible example of troubling
situations.
For another is \vskip, as sometimes the distance between two heading
must be smaller than the normal space above or below:
\subsection ...
\vskip-14pt
\subsubsection ...
In this situation I always experience the same problem: you have a
heading at bottom of page :o(
I just didn't manage to show this with an minimal example.
Steffen
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2008-07-25 8:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 7:58 Steffen Wolfrum
2008-07-25 8:08 ` Wolfgang Schuster
2008-07-25 8:15 ` Steffen Wolfrum
2008-07-25 8:25 ` Wolfgang Schuster
2008-07-25 8:33 ` Steffen Wolfrum
2008-07-25 8:39 ` Wolfgang Schuster
2008-07-25 8:52 ` Steffen Wolfrum [this message]
2008-07-25 11:22 ` Wolfgang Schuster
2008-07-25 12:56 ` Steffen Wolfrum
2008-07-27 18:28 ` Peter Münster
2008-07-28 6:20 ` Wolfgang Schuster
2008-07-26 11:37 ` Taco Hoekwater
2008-07-28 14:28 ` Hans Hagen
2008-07-28 15:24 ` Steffen Wolfrum
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=3D61AA91-64B5-46A1-BF32-04F69B2C8ABB@st.estfiles.de \
--to=context@st.estfiles.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).