emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Controlling pagination on headings in Latex/PDF export?
Date: Fri, 17 Feb 2012 17:50:55 +0100	[thread overview]
Message-ID: <804nuppfo0.fsf@somewhere.org> (raw)
In-Reply-To: 1850.1329496807@alphaville

Hi Nick,

Nick Dokos wrote:
> Sebastien Vauban <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> wrote:
>
>> You cannot reproduce it, because I misplaced the call to mykeewithnextpar: it
>> must be between the two things you want to see glue'd together.
>> 
>> Hence, in the example you mention, it works perfectly.
>
> No, that's not what I'm talking about: I'm not using your mechanism at
> all (note the disabling ## in front). What I'm saying is that I find it
> exceedingly difficult to reproduce the behavior the OP reported at all:
> no tricks, just export to LaTeX and process. That's why I wanted to see
> an example of the input file.

OK. Sorry for misreading...

> My contention is that LaTeX is pretty good at keeping things together
> that should be together, so the misbehavior indicates some *other* kind
> of problem: e.g. there is a fairly well known problem that causes all of
> the figures to end up at the end of the chapter, because the constraints
> imposed by the user make it impossible to DTRT.

Things that can easily make LaTeX become crazy is changing the color of the
titles. In such a case, LaTeX will allow much more easily to break after the
title, even if at bottom of page, as changing color somehow affects penalty.

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2012-02-17 16:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16 17:45 Controlling pagination on headings in Latex/PDF export? Jos'h Fuller
2012-02-16 18:20 ` Nick Dokos
2012-02-16 18:25   ` Jos'h Fuller
2012-02-16 18:58     ` Russell Adams
2012-02-16 19:44     ` Sebastien Vauban
2012-02-16 20:09       ` Jos'h Fuller
2012-02-16 20:16         ` Jos'h Fuller
2012-02-16 20:25           ` Sebastien Vauban
2012-02-16 21:02             ` Nick Dokos
2012-02-17  8:05               ` Stefan Nobis
2012-02-17  8:13                 ` Ian Barton
2012-02-17  8:55               ` Sebastien Vauban
2012-02-17 16:40                 ` Nick Dokos
2012-02-17 16:50                   ` Sebastien Vauban [this message]
2012-02-17 17:19                     ` Nick Dokos
2012-02-17 21:48                       ` Sebastien Vauban
2012-02-16 21:12           ` Nick Dokos
2012-02-16 23:12             ` Jos'h Fuller
2012-02-17  8:50               ` Stefan Nobis
2012-02-17  9:09               ` Stefan Nobis
2012-02-17 16:42                 ` Nick Dokos

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=804nuppfo0.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).