Thank you for all your replies, very helpful,
Richard
On Fri, 2025-01-10 at 11:44 -0800, Knute Snortum wrote:
> On Fri, Jan 10, 2025 at 10:27 AM William Rehwinkel via LilyPond user
> discussion wrote:
> > Dear Richard,
> >
> > I don't know if I can help with what to do to make this warning not
On Fri, Jan 10, 2025 at 10:27 AM William Rehwinkel via LilyPond user
discussion wrote:
> Dear Richard,
>
> I don't know if I can help with what to do to make this warning not
> appear, but my advice to you is, as long as the output looks good don't
> worry about it.
Agreed. And if you just wan
It's very difficult to troubleshoot without narrowing down the code causing
the error, but look for grobs where the typesetting depends on line
breaking, especially cross-staff grobs.
On Fri, Jan 10, 2025 at 1:04 PM Richard Shann
wrote:
> In a large file a programming error message is emitted:
>
Dear Richard,
I don't know if I can help with what to do to make this warning not
appear, but my advice to you is, as long as the output looks good don't
worry about it.
In my experience I usually come across these peculiar warnings/errors
when I try to do really specific weird things, such
From: Knute Snortum
Hmmm... I still get the programming errors in 2.25.21.
As do I - on Windows, in case it's relevant.
Paul
On Fri, Nov 8, 2024 at 7:57 AM Zvony Nagy wrote:
> Your code snippet compiles without programming errors in version 2.25.6.
>
Hmmm... I still get the programming errors in 2.25.21.
--
Knute Snortum
Your code snippet compiles without programming errors in version 2.25.6.
>
> On Nov 8, 2024 at 09:50 , < Richard Shann > wrote:
>
>
> Moving the Mark Engraver to a RhythmicStaff placed above another staff
> throws a programming error when a rehearsal mark is set in version
> 2.24, but not in ve
Le 26/10/2022 à 09:11, Jean Abou Samra a écrit :
Could you send the file to me?
Thanks for sending, I've minimized it and opened
https://gitlab.com/lilypond/lilypond/-/issues/6447
Best,
Jean
> Le 26 oct. 2022 à 07:07, Federico Bruni a écrit :
>
> Hi all
>
> I'm testing 2.23.80 on my private sheets and I'm looking for errors... I
> don't know if this occurred with previous versions. Probably it did but I
> didn't notice it as I use a build system to compile multiple files and
>
