ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: <phthenry@iglou.com>
Subject: Re: widow and orphan control
Date: Wed, 30 Mar 2005 09:29:16 -0500	[thread overview]
Message-ID: <E1DGeC4-0002MI-NT@iglou.com> (raw)
In-Reply-To: <424A772D.9060803@seznam.cz>



From: Vit Zyka <vit.zyka@seznam.cz>
>  >>Hans Hagen wrote (8:53):
> >> Paul Tremblay wrote:
> >>> What I would need is some type of macro that can determine how much
> >>> space is left on the page. If the space is less than some small,
> >>> pretermined amount (say, 24 points, for example), then put the
> title on
> >>> the next page, or put in a \blank[24pt, flexible]
> >>>
> >>> I know nothing about writing macros, or if this is possible. 
> >> 
> >> \testpage[24pt]
> 
> Vit Zyka wrote (11:35):
>  >\penalty50
>  >\vskip3\baselineskip plus1fil
>  >\nobreak
>  >\vskip-3\baselineskip plus-1fil
>  >
>  >It is useful before section title etc. I believe it is implemented to
>  >ConTeXt, but I do not know the interface.
> 
> Whawgh! Hans had answered the question before I sent it. Sorry, my 
> homing pigeon was too lazy... Although Hasselt-to-Prague way in 2.5 hrs
> it is not so bad :)
> 

Actually, no! Both your responses help me out.

Could you explain your snippet of code? I don't quite know what 
the \penalty50 means. I know TeX applies a penalty to each line,
but I'm confused if the penalty is for fitting the line 
horizontally or vertically, or both. 

I know what vskip does, but I'm not sure about the other commands,
or the strategy. Incidently, I do very much want code that acts
on titles for sections and subsections. That is my exact problem 
right now. I believe that ConTeXt will generally handle widows
if they just occur in a regular paragraph.

Hans provided a very useful tidbit in \testpage[24pt], but I'm not 
sure if I should use this in a macro. I have never written a 
macro in TeX before. I was hoping I would not have to write macros,
but maybe I should just learn the basics?

I guess there is a section on macros in the big manual. But that 
is sitting at home next to my computer that has the ConTeXt on it!

Thanks

Paul

  reply	other threads:[~2005-03-30 14:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-29  3:04 Paul Tremblay
2005-03-29 23:24 ` Paul Tremblay
2005-03-30  0:45   ` speter
2005-03-30  6:53   ` Hans Hagen
2005-03-30  9:53     ` Vit Zyka
2005-03-30 14:29       ` phthenry [this message]
2005-03-30 23:23         ` Vit Zyka
2005-03-30 23:03       ` Paul Tremblay
2005-03-30 23:02     ` Paul Tremblay
2005-03-31  7:11       ` Hans Hagen
2005-04-28 15:57       ` Using modes Matthias Weber
2005-04-28 19:00         ` Willi Egger
2005-04-28 21:43           ` Matthias Weber
2005-04-28 21:47           ` Matthias Weber
2005-04-28 22:17             ` David Munger
2005-03-30  7:31   ` widow and orphan control Patrick Gundlach
2005-03-30 23:05     ` Paul Tremblay
2005-03-30  9:35   ` Vit Zyka
2005-03-30  4:03 ` Paul Tremblay
2005-03-30  7:24   ` Patrick Gundlach
2005-03-30 23:08     ` Paul Tremblay

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=E1DGeC4-0002MI-NT@iglou.com \
    --to=phthenry@iglou.com \
    --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).