From: Mark Elston <m_elston@comcast.net>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Sectioning in LaTeX export
Date: Tue, 07 Apr 2009 19:16:27 -0700 [thread overview]
Message-ID: <49DC08FB.5000808@comcast.net> (raw)
In-Reply-To: <49DC0349.4040906@comcast.net>
Mark Elston wrote:
> I have an org file I use specifically for exporting a collection of
> other org files to pdf (using LaTeX). However, the resulting output
> is not very much like I would like it to be.
>
> I am using the book class for now but will likely add my own LaTeX_CLASS
> entry later once I get this all figured out.
>
> Ideally, each included file should form its own chapter. Within that
> chapter each level 1 heading would be a section, level 2 headings would
> be subsections, etc.
>
> I cannot get this to happen. Every level 1 heading is always an itemize
> item and level 2 and below just show up as "** <heading>" lines.
>
> Currently, at the top of my top-level org file I have the following:
>
> #+TITLE: My Tasks
> #+OPTIONS: H:4 num:t d:t
> #+LaTeX_CLASS: book
>
> The title and class seem to work but the options line seems to be
> ignored.
>
> How can I enforce some structure to my resulting latex code?
>
> Mark
I forgot to mention that, right now, I am including the 'chapter' org
files with the following approach:
#+LaTeX: \chapter{Ch 1 Name}
#+INCLUDE: "~/org/ch1.org"
#+LaTeX: \chapter{Ch 2 Name}
#+INCLUDE: "~/org/ch2.org"
etc. This was the only way I could think of to get chapter divisions.
Mark
next prev parent reply other threads:[~2009-04-08 2:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 1:52 Sectioning in LaTeX export Mark Elston
2009-04-08 2:16 ` Mark Elston [this message]
2009-04-08 6:17 ` Manish
[not found] ` <9135.1239160927@gamaville.dokosmarshall.org>
2009-04-08 14:57 ` Mark Elston
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49DC08FB.5000808@comcast.net \
--to=m_elston@comcast.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.