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: Thu, 16 Feb 2012 20:44:12 +0100	[thread overview]
Message-ID: <80obsyr2b7.fsf@somewhere.org> (raw)
In-Reply-To: 44B0EAE8544C834188E8790873CDE1CC3E154C@ARCEXCHANGE.arc.local

Hi Jos'h,

Jos'h Fuller wrote:
> I am familiar with \newpage (and I especially like to put it at the front of
> the document to keep my content out of my table of contents!), but I was
> hoping to be able to do this in some more automatic fashion, since these are
> long reports and I want to be able to process them unattended.
>
> Is it possible to do something like this:
>
> * Period...
> ** Asset
> #+latex: \keepthisstufftogether{begin}
> *** DEPARTMENT A
>     | Table | Data | Here. |
>     | Table | Data | Here. |
>     | Table | Data | Here. |
> #+latex: \keepthisstufftogether{end}
> *** DEPARTMENT B
> ...
>
> I have no idea what /actual/ LaTeX call fills in for
> "\keepthisstufftogether" though...

I have written such a thing, years ago, first for LaTeX, now for Org:

--8<---------------cut here---------------start------------->8---
% how not to have a page break with what is following?
\def\mykeepwithnextpar{\par\nobreak\@afterheading}
--8<---------------cut here---------------end--------------->8---

and I put whereever it's needed

--8<---------------cut here---------------start------------->8---
** Asset
#+latex: \mykeepwithnextpar{}
*** DEPARTMENT A
    | Table | Data | Here. |
    | Table | Data | Here. |
    | Table | Data | Here. |
*** DEPARTMENT B
--8<---------------cut here---------------end--------------->8---

Does it work for you?

Best regards,
  Seb

-- 
Sebastien Vauban

  parent reply	other threads:[~2012-02-16 19:44 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 [this message]
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
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=80obsyr2b7.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).