From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: orphan headline
Date: Sun, 29 May 2016 11:57:32 +0200 [thread overview]
Message-ID: <be77f8ef-6ed4-d309-4207-891253062ab3@gmx.es> (raw)
In-Reply-To: <57484249.2020704@gmail.com>
On 05/27/2016 02:49 PM, Wolfgang Schuster wrote:
>> Pablo Rodriguez 26. Mai 2016 um 21:29
>>
>> In a much simpler case, it seems to work:
>>
>> \setuphead[section]
>> [style=\ss\tfa, after={\hrule\blank[samepage,big]}]
>> %~ [style=\ss\tfa, after={\hrule\blank[big]}]
>> [..]
>
> A good idea but it can be improved.
>
> \definevspace[sectionrule][3mm]
>
> \setuphead
> [section]
> [ width=0.8\textwidth,
> commandafter={\vspace[sectionrule]\hrule},
> before={\blank[0.5cm]},
> after={\blank[1cm]}]
Wolfgang,
many thanks for the improvement.
I have a question about your code:
What prevents page break between heading the next paragraph?
I might guess that is the two distinct options commandafter and after.
But this is only my suspicion on what may work there.
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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:[~2016-05-29 9:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 8:56 Andrea Valle
2016-05-26 15:40 ` Pablo Rodriguez
2016-05-26 15:45 ` Andrea Valle
2016-05-26 19:29 ` Pablo Rodriguez
2016-05-27 12:49 ` Wolfgang Schuster
2016-05-29 9:57 ` Pablo Rodriguez [this message]
2016-05-29 11:26 ` Hans Hagen
2016-05-26 19:55 ` Wolfgang Schuster
2016-05-27 8:16 ` Andrea Valle
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=be77f8ef-6ed4-d309-4207-891253062ab3@gmx.es \
--to=oinos@gmx.es \
--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).