From: "Fraga, Eric" <e.fraga@ucl.ac.uk>
To: reza <reza@housseini.me>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Use custom preamble from tex file for latex export
Date: Fri, 17 Feb 2023 12:49:50 +0000 [thread overview]
Message-ID: <878rgwmp75.fsf@ucl.ac.uk> (raw)
In-Reply-To: <010201865f61a60d-e0f854b4-0dfd-4f91-99bb-b43ceede27e9-000000@eu-west-1.amazonses.com> (reza@housseini.me's message of "Fri, 17 Feb 2023 12:38:00 +0000")
On Friday, 17 Feb 2023 at 12:38, reza wrote:
> Thanks for the idea, will test this, but I fear this will collide with
> the latex class provided by org?
Well, you could have just the documentclass line removed from the
preamble and define an org latex class appropriately. There's always
going to be some need to have part of the configuration within the org
file itself but it could be minimised.
The full org alternative is to customise org-latex-classes with all the
LaTeX preamble you want or need. This is what I do.
--
: Eric S Fraga, with org release_9.6.1-250-ge6353d in Emacs 30.0.50
next prev parent reply other threads:[~2023-02-17 12:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1535a463-91fd-d085-06ee-ebd816c57ec8@housseini.me>
2023-02-17 8:55 ` Use custom preamble from tex file for latex export reza
2023-02-17 10:08 ` Fraga, Eric
2023-02-17 10:28 ` Fraga, Eric
2023-02-17 10:30 ` Fraga, Eric
[not found] ` <ea7618de-c02e-ee1a-8f32-083046ac09bb@housseini.me>
2023-02-17 12:38 ` reza
2023-02-17 12:49 ` Fraga, Eric [this message]
[not found] ` <b6dad7bb-9ba2-39e9-5ad5-bbfd5c7a9d74@housseini.me>
2023-02-17 13:08 ` reza
2023-02-17 13:14 ` Ihor Radchenko
[not found] ` <4f7041fc-4d26-0308-041b-e34365613074@housseini.me>
2023-02-17 13:16 ` reza
2023-02-17 13:26 ` Ihor Radchenko
2023-02-17 13:15 ` Fraga, Eric
[not found] ` <2660604c-3d61-890b-1088-6b56d773f674@housseini.me>
2023-02-21 8:40 ` reza
2023-02-21 10:08 ` Fraga, Eric
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=878rgwmp75.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=reza@housseini.me \
/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).