Lilypond 2.22 & 2.23 return 0 when a Scheme error occurs.

Hi, This very basic program reproduce the issue: #(error "test") \relative {   c'1 | } With Lilypond 2.20, the compilation produces: Processing `scheme_err.ly' Parsing... scheme_err.ly:1:2: error: GUILE signaled an error for the expression beginning here #  (error "test") scheme_err.ly:1: w

Re: Scheme parameters names lost with Lilypond 2.23.8

Thanks Jean for the detailed answer! Regarding having custom versions of functions & macros that defines functions & procedures, I would prefer avoiding doing so even though I already do so for macros and classes to attach documentation strings (https://github.com/soppera/lilypond-harmony-rule

Re: Scheme parameters names lost with Lilypond 2.23.8

Le 01/05/2022 à 20:29, Stéphane SOPPERA a écrit : Hi, While trying to make sure my automatic documentation generation code works with Lilypond 2.23.8 (and especially Guile 2.2) I noticed a bug that may be due to how Lilypond is using Guile 2.2. The current version of my code uses /(p//rocedure

Scheme parameters names lost with Lilypond 2.23.8

Hi, While trying to make sure my automatic documentation generation code works with Lilypond 2.23.8 (and especially Guile 2.2) I noticed a bug that may be due to how Lilypond is using Guile 2.2. The current version of my code uses /(p//rocedure-source)/