From: Ihor Radchenko <yantar92@posteo.net>
To: "Pedro Prieto Alarcón" <pedpral@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] ox-latex does not read EXPORT_LATEX_CLASS property from subtree [9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/org/)]
Date: Tue, 10 Oct 2023 15:59:06 +0000 [thread overview]
Message-ID: <87v8be8o51.fsf@localhost> (raw)
In-Reply-To: <CAK69_dRos4rv6g_pQGxee2zG1bmjCqb1wXnQuG4tZ_wdSAvqNA@mail.gmail.com>
Pedro Prieto Alarcón <pedpral@gmail.com> writes:
> I can't make ox-latex use a different class for a subtree using
> EXPORT_LATEX_CLASS, as stated in the docs:
> https://orgmode.org/manual/LaTeX-header-and-sectioning.html
>
> I am trying to change a specific subtree to a different layout (using
> tcolorbox) than the one provided in the main document class (sections)
I am not sure if Latex class is what you want. LATEX_CLASS defines how
Org parses the document structure and what to put into \documentclass -
it is defined once at the beginning of export. When you set
EXPORT_LATEX_CLASS for a subtree, it will be used when you export that
subtree as a separate document.
If you want to change the latex environment used during export, I
recommend using special block instead.
Not a bug.
Canceled.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-10-10 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 1:37 [BUG] ox-latex does not read EXPORT_LATEX_CLASS property from subtree [9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/org/)] Pedro Prieto Alarcón
2023-10-10 15:59 ` Ihor Radchenko [this message]
2023-10-10 16:18 ` Pedro Prieto Alarcón
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=87v8be8o51.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=pedpral@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).