emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Guillaume MULLER <guillaume.muller@emse.fr>
Subject: Re: How to solve "Warning (emacs): Please update the LaTeX src-block-backend to listings"
Date: Thu, 24 Aug 2023 09:23:16 +0000	[thread overview]
Message-ID: <873508kd4r.fsf@localhost> (raw)
In-Reply-To: <ae98244b-f8ff-d138-279d-5e0743966a1a@emse.fr>

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

> - Would be great to be able to set this parameter per org buffer/file, e.g. with a #+ (#+OPTIONS?) command. Indeed, using the defaults is OK most of the time for most of the users. I only need this trick when I want to force lstlistings, and I only need to force lstlistings when I want to insert a LaTeX inside a src block (it might be possible with other backends, but I don't know how to do it with the other backends, and I can look for documentations as I don't know which is the default backend)

The default backend is verbatim.
You can already set the backend on per-file basis using file-local
variables or #+BIND keywords.

We might add a dedicated Org keyword like #+LATEX_SRC_BLOCK_BACKEND though.

> - It would be great to add this "trick" (on how to change the backend) in the Docs (e.g. the page I cited in my previous email)

> - In the docs, it would also be great to tell what is the default backend (as I thought it was lstlisting and it is clearly not + the message I cited made me think it has changed recently)

Already done in on the development branch. orgmode.org will update the
manual after the next minor release.

> - Finally, when the error is raised, (Doom)Emacs goes definitively berzerck: every time I try to save the/any buffer with C-x C-s "save-buffer", it asks for the name to save to and for a confirmation for overwriting the selected file when I select the same filename as the one that was initially opened. So there might be something that is not restored correctly after the error is rasied?

What do you mean by error? What you described is a warning, not an
error. And it should have 0 effect except displaying a buffer with that warning.

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>

      parent reply	other threads:[~2023-09-09  8:11 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
     [not found]   ` <ae98244b-f8ff-d138-279d-5e0743966a1a@emse.fr>
2023-08-24  9:23     ` Ihor Radchenko [this message]

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=873508kd4r.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=guillaume.muller@emse.fr \


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