From: tsd@tsdye.com (Thomas S. Dye)
To: Ken Mankoff <mankoff@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: latex export for 4th-level heading
Date: Thu, 10 Jul 2014 11:20:49 -1000 [thread overview]
Message-ID: <m2a98g29n2.fsf@tsdye.com> (raw)
In-Reply-To: <m28uo0q5lt.fsf@gmail.com> (Ken Mankoff's message of "Thu, 10 Jul 2014 17:13:38 -0400")
Ken Mankoff <mankoff@gmail.com> writes:
> * On 2014-07-10 at 17:08, Thomas S. Dye wrote:
>> Aloha Ken,
>>
>> Ken Mankoff <mankoff@gmail.com> writes:
>>
>>> When exporting to LaTeX, fourth-level headings become \enumerate. In
>>> LaTeX, the item below \subsubsection is \paragraph, not \enumerate.
>>>
>>> Here is what happens:
>>>
>>> * Top becomes \section
>>> ** Second becomes \subsection
>>> *** Third becomes \subsubsection
>>> **** Fourth becomes \enumerate
>>>
>>> Is there a way to set Fourth to either \paragraph or just nothing?
>>
>> Only the first three outline levels will be used as headings. Deeper
>> levels will become itemized lists. You can change the location of this
>> switch globally by setting the variable org-export-headline-levels, or
>> on a per-file basis with a line
>>
>> #+OPTIONS: H:4
>>
>
> Thanks. That makes sense. I thought that was just for controlling the
> TOC depth, but it makes sense it controls content headings too.
The table of contents is normally inserted directly before the first
headline of the file.
#+OPTIONS: toc:2 (only to two levels in TOC)
#+OPTIONS: toc:nil (no TOC at all)
hth,
Tom
--
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com
prev parent reply other threads:[~2014-07-10 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 17:05 latex export for 4th-level heading Ken Mankoff
2014-07-10 21:08 ` Thomas S. Dye
2014-07-10 21:13 ` Ken Mankoff
2014-07-10 21:20 ` Thomas S. Dye [this message]
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=m2a98g29n2.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=mankoff@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).