From: "Denis Bitouzé" <denis.bitouze@univ-littoral.fr>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "Denis Bitouzé" <denis.bitouze@univ-littoral.fr>,
"Daniel Fleischer" <danflscr@gmail.com>,
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 09:32:05 +0200 [thread overview]
Message-ID: <87pmepvb7u.fsf@example.com> (raw)
In-Reply-To: <87mt9thioz.fsf@localhost> (Ihor Radchenko's message of "Tue, 18 Oct 2022 04:14:20 +0000")
Le 18/10/22 à 04h14, Ihor Radchenko a écrit :
> 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?
It is enough to put it in a group:
┌────
│ \bgroup
│ \lstset{...}
│ \begin{lstlisting}
│ ...
│ \end{lstlisting}
│ \egroup
└────
Otherwise, all the options specified by `\lstset` can be applied as an
option of the `lstlisting` environment:
┌────
│ \begin{lstlisting}[language=⟨language⟩,...]
└────
--
Denis
next prev parent reply other threads:[~2022-10-18 7:41 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
2022-10-18 7:32 ` Denis Bitouzé [this message]
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:
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=87pmepvb7u.fsf@example.com \
--to=denis.bitouze@univ-littoral.fr \
--cc=danflscr@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).