From: Max Nikulin <manikulin@gmail.com>
To: Rudi C <rudiwillalwaysloveyou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-mode: example blocks are no longer syntax highlighted in emacs
Date: Mon, 26 Feb 2024 18:05:18 +0700 [thread overview]
Message-ID: <3aa4cfa3-9791-4b59-a891-e841facbc73f@gmail.com> (raw)
In-Reply-To: <87il2cn9ly.fsf@localhost>
On 25/02/2024 17:04, Ihor Radchenko wrote:
> Rudi C writes:
>
>> After upgrading to emacs 29.2 and org 9.7, my example blocks are no longer
>> syntax highlighted in emacs.
>
> Yet, there is no reason to remote it.
> I recovered example block fontification on main.
At least some people are against the feature:
https://list.orgmode.org/orgmode/CA+G3_PPYmiiwHYKkgiJDZQ=o7DvaG=0G3aQnPHSBKEMZsOyG-g@mail.gmail.com/T/#u
Tom Gillespie. Re: [DISCUSSION] Refactoring fontification system. Tue, 7
Jun 2022 21:23:21 -0700.
I do not mind to have syntax highlighting support for #+begin_example
blocks, but it should be coherent with ox exporters. My idea to unify
#+begin_src and #+begin_example exporters was not meet warmly.
To notify users that fontification will be lost during export, the
feature may be turned into an opt-in one by adding a defcustom user
option disabled by default and having docstring clearly describing that
language will be ignored during export and users need to suppress
`org-lint' warnings.
next prev parent reply other threads:[~2024-02-26 11:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 15:02 org-mode: example blocks are no longer syntax highlighted in emacs Rudi C
2024-02-25 10:04 ` Ihor Radchenko
2024-02-26 0:39 ` Rudi C
2024-02-26 11:05 ` Max Nikulin [this message]
2024-02-28 12:13 ` Ihor Radchenko
-- strict thread matches above, loose matches on Subject: below --
2024-02-22 15:47 Bruno Barbier
2024-02-22 20:08 ` Rudi C
2024-02-23 10:35 ` Bruno Barbier
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=3aa4cfa3-9791-4b59-a891-e841facbc73f@gmail.com \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rudiwillalwaysloveyou@gmail.com \
/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).