From: Vikas Rawal <vikasrawal@gmail.com>
To: William Denton <wtd@pobox.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: #+latex_header blocks, or, managing lots of LaTeX headers
Date: Tue, 12 Apr 2022 08:21:29 +0530 [thread overview]
Message-ID: <CALtzAB103mztcWPiS5qJFoms+Cp7EFU877-qtVvmD-_GEU9zLA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2204111958230.78594@shell3.miskatonic.org>
[-- Attachment #1: Type: text/plain, Size: 1842 bytes --]
For a major project like this, I would just put these in a separate file,
and include it using #+INCLUDE:
Vikas
On Tue, 12 Apr 2022 at 06:37, William Denton <wtd@pobox.com> wrote:
> I have another question related to managing a book I'm doing building for
> export
> to LaTeX: what do people do for managing all of the headers?
>
> I have about 30 #+latex_header lines in the project I'm working on, and
> I'm
> still just working on it as a basic article. When I'm ready to do more
> formatting I'll use the memoir class and then there will be more
> commands. I
> imagine some of you have huge headers with custom commands and more.
>
> It would be great if there was a way to manage these lines as LaTeX, for
> example
> in a "#+begin_export latex" block, but as far as I can tell, there isn't a
> way
> (unless once again I overlooked something).
>
> The idea came up about seven years ago, and Nicolas mentioned the
> possibility of
> a "#+begin_export latex :header t" implementation.
>
> https://lists.gnu.org/archive/html/emacs-orgmode/2015-05/msg00538.html
>
> It's possible to add a new class to the org-latex-classes variable, and in
> the
> documentation on it I see there are options ([NO-DEFAULT-PACKAGES],
> [NO-PACKAGES], [NO-EXTRA]) that allow one to trim away all the default
> headers.
> That makes it easy to take away, but not to add in lines I want, short of
> managing them in my init file.
>
> What sorts of practices do people have for managing lots of LaTeX headers?
> Juan Manuel Macías, you mentioned something like this---literate
> programming in
> Org to export LaTeX source---may I ask how you do it?
>
> Thanks,
>
> Bill
>
> --
> William Denton
> https://www.miskatonic.org/
> Librarian, artist and licensed private investigator.
> Toronto, Canada
[-- Attachment #2: Type: text/html, Size: 2450 bytes --]
next prev parent reply other threads:[~2022-04-12 2:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 0:46 #+latex_header blocks, or, managing lots of LaTeX headers William Denton
2022-04-12 2:51 ` Vikas Rawal [this message]
2022-04-12 14:34 ` Kaushal Modi
2022-04-12 6:16 ` Tim Cross
2022-04-12 8:02 ` Timothy
2022-04-12 8:55 ` Juan Manuel Macías
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=CALtzAB103mztcWPiS5qJFoms+Cp7EFU877-qtVvmD-_GEU9zLA@mail.gmail.com \
--to=vikasrawal@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).