emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Guillaume MULLER <guillaume.muller@emse.fr>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: How to solve "Warning (emacs): Please update the LaTeX src-block-backend to listings"
Date: Thu, 24 Aug 2023 07:39:43 +0000	[thread overview]
Message-ID: <87il947utc.fsf@localhost> (raw)
In-Reply-To: <b5c056cb-3258-4a11-2d9b-33c97b112d62@emse.fr>

Guillaume MULLER <guillaume.muller@emse.fr> writes:

> I'm trying to create a code block with some latex code to be interpreted inside. I only knew lstlistings until now. Page https://orgmode.org/manual/Source-blocks-in-LaTeX-export.html lists Engraved and Minted as possible backend. https://list.orgmode.org/87wnf1z1w8.fsf@gmail.com/T/ also lists verbatim.
>
> So from what I understand, of the message "Warning (emacs): Please update the LaTeX src-block-backend to listings", is that the default backend is not lstlistings and that there is a variable somewhere that should be set to lstlistings.

Yes. `org-latex-src-block-backend'.
I now updated the warning to be more explicit.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=85c94ecfc

-- 
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:[~2023-08-24  7:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-23 16:24 How to solve "Warning (emacs): Please update the LaTeX src-block-backend to listings" Guillaume MULLER
2023-08-24  7:39 ` Ihor Radchenko [this message]
     [not found]   ` <ae98244b-f8ff-d138-279d-5e0743966a1a@emse.fr>
2023-08-24  9:23     ` 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=87il947utc.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=guillaume.muller@emse.fr \
    /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).