From: David Masterson <dsmasterson@gmail.com>
To: William Denton <wtd@pobox.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: LaTeX tutorial (focused on what Org exports) ??
Date: Fri, 06 Jan 2023 15:57:18 -0800 [thread overview]
Message-ID: <SJ0PR03MB5455E2E506C1C3894CB0F27DA2FB9@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2301061254030.459618@shell3.miskatonic.org> (William Denton's message of "Fri, 6 Jan 2023 13:07:01 -0500 (EST)")
William Denton <wtd@pobox.com> writes:
> On 5 January 2023, David Masterson wrote:
>
>> With the Org files that you create, how many levels of headers do you
>> use? I use Org for personal task management mostly, but I'd like to
>> produce good PDFs to give to my wife (Org is too complicated). My
>> problem is that I'll structure my documents with many (5+) header
>> levels with tasks at the bottom. The problem is that the 'article' and
>> 'report' document classes used by Org don't look right if you go beyond
>> 3 levels -- if you know what I mean. (NOTE: LaTeX newbie)
>
> By default the first three levels go to LaTeX headings, and then after that they
> become lists. You can change that with the H option in a header, as described
> here, to set org-export-headline-levels:
>
> https://orgmode.org/org.html#Export-Settings
>
> So you could say:
>
> #+options: H:5
>
> Level four headings become paragraphs, and level five become subparagraphs.
>
> With that in place, you might like how the titlesec package can give a great
> deal of control over section headings. I use this for some reports---it wraps
> text around level three headings, which about as far as I usually go for
> documents I export.
>
> #+LATEX_HEADER: \usepackage[]{titlesec}
> #+LATEX_HEADER: \titleformat{\section} {\centering\Large}{\thesection}{}{}
> #+LATEX_HEADER: \titleformat{\subsubsection}[drop]{\itshape}{\thesection}{}{}{}
> #+LATEX_HEADER: \titlespacing{\subsubsection}{0.75in}{\baselineskip}{0.5in}
This looks interesting -- now to find some time to dig in. Thanks.
--
David Masterson
next prev parent reply other threads:[~2023-01-07 0:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 7:18 Re: LaTeX tutorial (focused on what Org exports) ?? Pedro Andres Aranda Gutierrez
2023-01-06 6:21 ` David Masterson
2023-01-06 18:07 ` William Denton
2023-01-06 23:57 ` David Masterson [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-30 21:29 David Masterson
2022-12-31 1:18 ` Thomas S. Dye
2022-12-31 10:32 ` Marcin Borkowski
2023-01-01 7:08 ` David Masterson
2023-01-02 18:31 ` William Denton
2023-01-03 3:25 ` David Masterson
2022-12-31 11:55 ` Fraga, Eric
2023-01-01 7:12 ` David Masterson
2023-01-01 7:19 ` Ihor Radchenko
2023-01-01 13:18 ` Fraga, Eric
2023-01-01 13:43 ` Ihor Radchenko
2023-01-02 12:30 ` Fraga, Eric
2023-01-03 3:23 ` David Masterson
2023-01-03 9:10 ` Fraga, Eric
2023-01-04 0:12 ` David Masterson
[not found] ` <87o7rgmhcs.fsf@penguin>
2023-01-03 3:28 ` David Masterson
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=SJ0PR03MB5455E2E506C1C3894CB0F27DA2FB9@SJ0PR03MB5455.namprd03.prod.outlook.com \
--to=dsmasterson@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wtd@pobox.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).