[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Option that prevents Org to add \lstset{language=⟨language⟩,...} whe
From: |
Ihor Radchenko |
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 |
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.
Confirmed.
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>
- Re: Option that prevents Org to add \lstset{language=⟨language⟩,...} when code blocks are exported to LaTeX,
Ihor Radchenko <=