emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: "Denis Bitouzé" <denis.bitouze@univ-littoral.fr>,
	"Daniel Fleischer" <danflscr@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Option that prevents Org to add \lstset{language=⟨language⟩,...} when code blocks are exported to LaTeX
Date: Tue, 18 Oct 2022 04:14:20 +0000	[thread overview]
Message-ID: <87mt9thioz.fsf@localhost> (raw)
In-Reply-To: <87zgmda67z.fsf@example.com>

Denis Bitouzé <denis.bitouze@univ-littoral.fr> writes:

> here is a feature request about the LaTeX export.
> With ~(setq org-latex-listings t)~, code blocks such as:
>   ┌────
>   │ #+BEGIN_SRC ⟨language⟩ :exports code
>   │ ...
>   │ #+END_SRC
>   └────
> are exported to LaTeX into:
>   ┌────
>   │ \lstset{language=⟨language⟩,label= ,caption= ,captionpos=b,numbers=none}
>   │ \begin{lstlisting}
>   │ ...
>   │ \end{lstlisting}
>   └────
> But the:
>   ┌────
>   │ \lstset{language=⟨language⟩,label= ,caption= ,captionpos=b,numbers=none}
>   └────
> systematically added before each of the ~lstlisting~ LaTeX environments
> is not always desirable and let me explain why.

Is there a way to apply \lstset locally for the environment?

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>

  reply	other threads:[~2022-10-18  4:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-26 17:27 Option that prevents Org to add \lstset{language=⟨language⟩,...} when code blocks are exported to LaTeX Denis Bitouzé
2022-10-18  4:14 ` Ihor Radchenko [this message]
2022-10-18  7:32   ` Denis Bitouzé
2022-10-18  8:11     ` Ihor Radchenko
2022-10-31  8:19       ` 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:

  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=87mt9thioz.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=danflscr@gmail.com \
    --cc=denis.bitouze@univ-littoral.fr \
    --cc=emacs-orgmode@gnu.org \


* 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


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