unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Jonas Damm <mailing@jonas-damm.de>
Cc: 63579@debbugs.gnu.org
Subject: bug#63579: org-babal-lilypond fontification error
Date: Fri, 19 May 2023 09:09:02 +0000	[thread overview]
Message-ID: <87mt20g029.fsf@localhost> (raw)
In-Reply-To: <87mt21xp28.fsf@jonas-damm.de>

Jonas Damm <mailing@jonas-damm.de> writes:

> User-agent: mu4e 1.8.13; emacs 29.0.91
> Example:
>
> Hi,
> I am using org-babel to create music sheets with lilypond.
> For some reason the fontification is not working anymore:
>
> [2. text/x-org]
> #+begin_src lilypond
>
>   \relative c' {
>     c d e f g
>     }
>
> #+end_src

This is a problem with lilypond:

Debugger entered--Lisp error: (void-variable font-lock-reference-face)
  (eval font-lock-reference-face t)
  (#f(compiled-function (highlight) "Apply HIGHLIGHT following a match.\nHIGHLIGHT should be of the form MATCH-HIGHLIGHT, see `font-lock-keywords'." #<bytecode -0xf53eae0ec5f928c>) (0 font-lock-reference-face t))
  (font-lock-fontify-keywords-region 1 42 nil)
  (font-lock-default-fontify-region 1 42 nil)
  (font-lock-fontify-region 1 42)
  (#f(compiled-function (beg end) #<bytecode -0x19f31ec42bd98447>) 1 42)
  (font-lock-ensure)

`font-lock-reference-face' is an obsolete variable that has been removed
in Emacs 29.

Please report this issue to Lilypond developers. See
https://lilypond.org/bug-reports.html

-- 
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-05-19  9:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18 22:17 bug#63579: org-babal-lilypond fontification error Jonas Damm
2023-05-19  9:09 ` Ihor Radchenko [this message]
2023-05-19 10:59   ` Eli Zaretskii
2023-05-19 15:17   ` Jonas Damm

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mt20g029.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=63579@debbugs.gnu.org \
    --cc=mailing@jonas-damm.de \
    /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.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).