From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Index entries messing up page breaks
Date: Tue, 13 Dec 2005 17:47:52 +0100 [thread overview]
Message-ID: <439EFB38.6090104@wxs.nl> (raw)
In-Reply-To: <439EF71D.9050003@capdm.com>
Duncan Hothersall wrote:
>I said:
>
>
>>Is there any workaround/fix?
>>
>>
>
>I find that the addition of \dontleavehmode fixes it. Is this safe to
>use in general?
>
>\starttext
>\section{Tufte}
>\dorecurse{4}{\input tufte \par}
>\section{Knuth}
>\dontleavehmode\index{knuth}
>\input knuth \par
>\stoptext
>
>
no, use \dontleavehmode instead
if you see a tex file on the web and wonder why the spacing is messed up
... it's probably because of abundant use of \leavemode
(recent versions of pdftex provide \quitvmode which is equivalent to
\dontleavehmode; taco wrote that patch a while ago)
Hans
next prev parent reply other threads:[~2005-12-13 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-13 16:30 Duncan Hothersall
2005-12-13 16:47 ` Hans Hagen [this message]
2005-12-13 17:21 ` Taco Hoekwater
[not found] <20051213220414.AAFF112850@ronja.ntg.nl>
2005-12-14 10:25 ` Duncan Hothersall
-- strict thread matches above, loose matches on Subject: below --
2005-12-13 16:13 Duncan Hothersall
2005-12-13 22:03 ` 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=439EFB38.6090104@wxs.nl \
--to=pragma@wxs.nl \
--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).