Re: [BUG] WORG example for ob-lilypond is no longer working as described (was: Moving some lisp/ob-*.el files to org-contrib - your advice?)

[Jonathan Gregory <jgrg@autistici.org>]

Hi

On 13 Jul 2023, Ihor Radchenko wrote:

> Jonathan Gregory <jgrg@autistici.org> writes:
>
>> Can you check if adding:
>>
>> \version "2.24.1"
>> #(ly:set-option 'use-paper-size-for-page #f)
>> #(ly:set-option 'tall-page-formats 'pdf)
>>
>> to the version-and-paper block fixes the issue.
>
> Yes, except that I have lilypond 2.24.0, which failed until I 
> changed the version to fit my lilypond version.
>
> Do you happen to know the minimal required version needed for 
> your change to work? And do we need that \version line at all?

I'd keep the version in sync with the stable release, but I guess 
that's up to the maintainer. The documentation says that "Every 
LilyPond file should contain a version statement":

The version statement is important for at least two reasons. 
First, it allows automatic updating of the input file as LilyPond 
syntax changes. Second, it describes the version of LilyPond 
needed to compile the file.

If the version statement is omitted from an input file, LilyPond 
prints a warning during the compilation of the file. 

-- 
Jonathan