emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: reza <reza@housseini.me>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Use custom preamble from tex file for latex export
Date: Fri, 17 Feb 2023 13:08:07 +0000	[thread overview]
Message-ID: <010201865f7d3916-b563687f-f9de-4ecb-9703-6fccacb1a261-000000@eu-west-1.amazonses.com> (raw)
In-Reply-To: <878rgwmp75.fsf@ucl.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 246 bytes --]

> The full org alternative is to customise org-latex-classes with all the
> LaTeX preamble you want or need.  This is what I do.

Is there a way to extend org-latex-classes inside my org file, so I can 
keep using C-c C-e l l (export to latex)?


[-- Attachment #2: OpenPGP_0xC375C6AF05125C52.asc --]
[-- Type: application/pgp-keys, Size: 15557 bytes --]

[-- Attachment #3: OpenPGP_signature --]
[-- Type: application/pgp-signature, Size: 499 bytes --]

  parent reply	other threads:[~2023-02-17 13:08 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
     [not found]           ` <b6dad7bb-9ba2-39e9-5ad5-bbfd5c7a9d74@housseini.me>
2023-02-17 13:08             ` reza [this message]
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=010201865f7d3916-b563687f-f9de-4ecb-9703-6fccacb1a261-000000@eu-west-1.amazonses.com \
    --to=reza@housseini.me \
    --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 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).