From: "Christian" <metan0r@gmx.de>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Avoiding widows and orphans (again?)
Date: Wed, 23 Nov 2011 15:45:59 +0100 [thread overview]
Message-ID: <008401cca9ee$9e972d40$dbc587c0$@gmx.de> (raw)
Good day to you,
I saw the related messages in the archive, but I don't really get it.
I'm looking for a (global) setting, that prevents the last line of a paragraph to slip on the next page. If it really must, it shall also drag another one with it for company.
Please enlighten me.
___________________________________________________________________________________
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 reply other threads:[~2011-11-23 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 14:45 Christian [this message]
2011-11-23 15:29 ` Hans Hagen
2011-11-23 15:59 ` Wolfgang Schuster
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='008401cca9ee$9e972d40$dbc587c0$@gmx.de' \
--to=metan0r@gmx.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).