From: Ihor Radchenko <yantar92@posteo.net>
To: emacs-orgmode@gnu.org
Subject: [PATCH] doc/org-manual.org: Document `org-latex-src-block-backend'
Date: Fri, 12 May 2023 13:24:58 +0000 [thread overview]
Message-ID: <87wn1dznpx.fsf@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 239 bytes --]
Attaching tentative manual patch that explains about
`org-latex-src-block-backend'. There was no explanation about different
ways to export colored source blocks in the past.
Please try to read and let me know if anything is confusing.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-doc-org-manual.org-Document-org-latex-src-block-back.patch --]
[-- Type: text/x-patch, Size: 2026 bytes --]
From fb77ae66d4d9c01a350140481bcb0f030a45fb69 Mon Sep 17 00:00:00 2001
Message-Id: <fb77ae66d4d9c01a350140481bcb0f030a45fb69.1683897756.git.yantar92@posteo.net>
From: Ihor Radchenko <yantar92@posteo.net>
Date: Fri, 12 May 2023 15:21:59 +0200
Subject: [PATCH] doc/org-manual.org: Document `org-latex-src-block-backend'
* doc/org-manual.org (Source blocks in LaTeX export): Explain possible
LaTeX export options for source blocks.
---
doc/org-manual.org | 31 +++++++++++++++++++++++++++++++
1 file changed, 31 insertions(+)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index ba9fdaf20..4e56a1e00 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -14181,6 +14181,37 @@ *** Source blocks in LaTeX export
#+cindex: source blocks, in @LaTeX{} export
#+cindex: @samp{ATTR_LATEX}, keyword
+#+vindex: org-latex-src-block-backend
+LaTeX export backend provides multiple ways to render src blocks in
+LaTeX, according to the value of ~org-latex-src-block-backend~:
+
+- =verbatim= (default) ::
+
+ Use =verbatim= LaTeX environment with no language-specific
+ fontification.
+
+- =listings= ::
+
+ Use =listings= environment provided by the corresponding LaTeX
+ package. Org will not add the =listings= package to LaTeX preamble,
+ users need to customize ~org-latex-packages-alist~ or LaTeX headers
+ manually.
+
+- =minted= ::
+
+ Use more syntax-aware =minted= package. Note that in addition to
+ customizing the LaTeX preamble, [[https://pygments.org][pygments]]
+ program should be installed and ~org-latex-pdf-process~ should pass
+ =-shell-escape= option to LaTeX executable.
+
+- =engraved= ::
+
+ Use =fvextra= LaTeX package and Emacs package
+ [[https://elpa.gnu.org/packages/engrave-faces][engrave-faces]]
+ available on GNU Elpa. =engrave-faces= will use Emacs fontification
+ to colorize the source blocks in LaTeX output.
+
+
The LaTeX export backend can make source code blocks into floating
objects through the attributes =:float= and =:options=. For =:float=:
--
2.40.0
[-- Attachment #3: Type: text/plain, Size: 224 bytes --]
--
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 reply other threads:[~2023-05-12 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 13:24 Ihor Radchenko [this message]
2023-05-24 4:03 ` [PATCH] doc/org-manual.org: Document `org-latex-src-block-backend' Nick Dokos
2023-05-30 15:27 ` [PATCH v2] " Ihor Radchenko
2023-05-31 2:50 ` Nick Dokos
2023-06-03 8:33 ` Ihor Radchenko
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=87wn1dznpx.fsf@localhost \
--to=yantar92@posteo.net \
--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).