emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: Broken LaTeX export
Date: Wed, 30 May 2012 19:46:15 +0200	[thread overview]
Message-ID: <87mx4po93s.fsf@Rainer.invalid> (raw)
In-Reply-To: loom.20120530T111354-654@post.gmane.org

SW writes:
> Thanks for the details. I noticed the overfull warnings from pdflatex.
> Smaller/simpler test cases I tried exported to LaTeX perfectly.

LaTeX tries very hard not to break pages around headings.  It expects
you to tell it when it is OK to not obey that rule, but you never did.
The correct way of dealing with a file that consists only of headings is
to write your own style file and explicitly allow page breaks in the
sectioning commands (usually before the heading).  While you're doing
that you can also chose a more suitable formatting.

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:

  reply	other threads:[~2012-05-30 17:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-29 12:59 Broken LaTeX export SW
2012-05-29 16:01 ` Nick Dokos
2012-05-29 16:57   ` SW
2012-05-30  9:08     ` Nick Dokos
2012-05-30  9:16       ` SW
2012-05-30 17:46         ` Achim Gratz [this message]
2012-05-30  9:45       ` SW
2012-06-01  7:42         ` Eric S Fraga
2012-07-04 12:41           ` SW
2012-05-30 10:51       ` SW

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:

  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=87mx4po93s.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \


* 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


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).