From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: SW <sabrewolfy@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Broken LaTeX export
Date: Fri, 1 Jun 2012 17:12:28 +0930 [thread overview]
Message-ID: <87ipfbpjff.fsf@ucl.ac.uk> (raw)
In-Reply-To: <loom.20120530T113943-420@post.gmane.org> (SW's message of "Wed, 30 May 2012 09:45:30 +0000")
SW <sabrewolfy@gmail.com> writes:
> Nick Dokos <nicholas.dokos <at> hp.com> writes:
>
>> Interesting: it seems to be a latex bug of some sort, but I haven't had
>> time to play with it too much yet. I'm trying things like modifying the
>> tex file slightly and seeing if the empty page(s)/overfull page(s)
>> persist. So far, it seems that all the packages that org includes are
>> innocent: I took them all out and the strangeness persists.
[...]
> However, this is a work-around, not a solution, as part of the appeal of
> org-mode and the LaTeX export is to be able to work with and generate outlines
> and structures of documents first, before adding all the content.
A simple solution which keeps your interest in the outline structure at
this stage of the writing is to add the line
#+options: H:3
to the document (remembering to refresh org by typing C-c C-c on this
line). This converts all 4th level headings and lower to lists on
export without you having to change the document content at all.
For your test document, this works just fine.
Once you have added enough text, you can change the 3 to 5 and your
document should export just fine.
HTH,
eric
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org release_7.8.10-630-g4144c5.dirty
next prev parent reply other threads:[~2012-06-01 7:42 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
2012-05-30 9:45 ` SW
2012-06-01 7:42 ` Eric S Fraga [this message]
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:
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=87ipfbpjff.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=sabrewolfy@gmail.com \
/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).