emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: LaTeX src block export
Date: Sat, 10 Dec 2022 12:37:49 +0100	[thread overview]
Message-ID: <CAO48Bk_LB7omfWf+AaMFmvEMDL6yYUMOYHFE5zz-Xdrn+Gc4Uw@mail.gmail.com> (raw)

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

Hi

I was wondering if there is a way to control which parameters are exported
when translating a src block to LaTeX in a document-wide fashion. I.e. with
a directive at the beginning of the .org file.

The background:

I have 'listings' to export src and example blocks and use
```
#+LATEX_HEADER: \\usepackage{upquote}
#+LATEX_HEADER: \\RequirePackage{fancyvrb}
#+LATEX_HEADER:
\\DefineVerbatimEnvironment{verbatim}{Verbatim}{fontsize=\footnotesize}
#+LATEX_HEADER:
\\DefineVerbatimEnvironment{lstlisting}{Verbatim}{fontsize=\scriptsize}
```
because this greatly improves the copy-and-paste behaviour of my PDFs. Now,
when exporting to laTeX, there are some extra parameters included, which
are not supported by fancyvrb. namely
`language=`
and
`caption.*= (take .* as a regexp)`

I have included a filter to get rid of the offending parameters in my
.emacs.d org configuration, but this is difficult to port to other emacs
setups (e.g. other co-workers).

Thanks, /PA
-- 
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler

Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet

[-- Attachment #2: Type: text/html, Size: 1737 bytes --]

next             reply	other threads:[~2022-12-10 11:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-10 11:37 Pedro Andres Aranda Gutierrez [this message]
2022-12-10 11:53 ` LaTeX src block export 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=CAO48Bk_LB7omfWf+AaMFmvEMDL6yYUMOYHFE5zz-Xdrn+Gc4Uw@mail.gmail.com \
    --to=paaguti@gmail.com \
    --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

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).