From: SW <sabrewolfy@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Broken LaTeX export
Date: Wed, 4 Jul 2012 12:41:28 +0000 (UTC) [thread overview]
Message-ID: <loom.20120704T143950-762@post.gmane.org> (raw)
In-Reply-To: 87ipfbpjff.fsf@ucl.ac.uk
Eric S Fraga <e.fraga <at> ucl.ac.uk> writes:
> 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
...
Thanks. That's a useful suggestion.
next prev parent reply other threads:[~2012-07-04 12:45 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
2012-07-04 12:41 ` SW [this message]
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=loom.20120704T143950-762@post.gmane.org \
--to=sabrewolfy@gmail.com \
--cc=emacs-orgmode@gnu.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).