Re: calculation in scheme causes "assertion failed" as of Ly 2.25.11

2024-04-11 Thread Aaron Hill via bug-lilypond
On 2024-04-11 10:12 am, K. Blum via bug-lilypond wrote: Starte lilypond.exe 2.25.14 [mwe scheme.ly]... »C:/Users/Flower/Desktop/mwe scheme.ly« wird verarbeitet Analysieren.../home/lily/lilypond-2.25.14/release/binaries/mingw/dependencies/src/guile-3.0.9/libguile/integers.c:115: assertion failed W

Re: Snippet 960 fails with Ly 2.25

2024-04-01 Thread Aaron Hill via bug-lilypond
On 2024-04-01 3:20 pm, K. Blum via bug-lilypond wrote: Hello, LSR snippet 960 works alright with LilyPond 2.24.3 and earlier. Ly 2.25.1 (and later) aborts with an error message, see below. In the docs I haven't found any changes to the functions in use. Also tried convert-ly, but it did not chan

Re: Chord names collide with span bar

2024-03-20 Thread Aaron Hill via bug-lilypond
On 2024-03-20 9:01 am, Werner LEMBERG wrote: I remembered that you can add the Bar_engraver to ChordNames. Making them transparent so they do not visually interfere with the SpanBar, but they still take up space. Nice! This begs the question whether we have a real bug or 'just' insufficient do

Re: Chord names collide with span bar

2024-03-20 Thread Aaron Hill via bug-lilypond
On 2024-03-20 8:14 am, Knute Snortum wrote: Ah, I see this is just for debugging. Thank you. Your solution helps when put into my bigger project. Some -- but not all -- of the bars are now wide enough. Oh, I think I found another option: \version "2.25.13" #(ly:set-option 'debug-sky

Re: Chord names collide with span bar

2024-03-20 Thread Aaron Hill via bug-lilypond
On 2024-03-20 8:07 am, Jean Abou Samra wrote: Le mercredi 20 mars 2024 à 15:56 +0100, Jean Abou Samra a écrit : Le mercredi 20 mars 2024 à 07:51 -0700, Knute Snortum a écrit : > Your solution requires version 2.22 and I'm using 2.24 > (with the \alternative command so it's not easy to change) T

Re: Chord names collide with span bar

2024-03-20 Thread Aaron Hill via bug-lilypond
On 2024-03-20 7:51 am, Knute Snortum wrote: Thank you so much for this fix and for entering an issue! There is just one thing that is a problem for me. Your solution requires version 2.22 and I'm using 2.24 (with the \alternative command so it's not easy to change). When I your solution conv

Re: Chord names collide with span bar

2024-03-20 Thread Aaron Hill via bug-lilypond
On 2024-03-20 1:45 am, Werner LEMBERG wrote: In some situations, chord names collide with the span bar of a Grand or Piano Staff. Here is an example: [...] [...] Still sounds like a defect of some sort, as the default behavior should probably be handling things. Aaron, please file an issue,

Re: Chord names collide with span bar

2024-03-19 Thread Aaron Hill via bug-lilypond
On 2024-03-19 2:29 pm, Knute Snortum wrote: I ran into something today -- it's not quite a bug; more of an "ugly." In some situations, chord names collide with the span bar of a Grand or Piano Staff. Here is an example: \version "2.25.13" \score { \new GrandStaff << \new Staff \relati

Re: Distance between top margin and title text in 25.2.+

2024-03-02 Thread Aaron Hill via bug-lilypond
On 2024-03-02 1:32 am, Anbo via bug-lilypond wrote: Hello, I don't know if this is a bug, but with the very latest Lilypond versions (2.25.+) the distance between the top margin and the title text does not match the value I specified, in this case 5 millimeters. The distance is always signifi

Re: old \alternative-syntax in documentation

2024-02-04 Thread Aaron Hill via bug-lilypond
Sorry, I thought the bug alias was still on the CC line. Resending to ensure broad visibility. On 2024-02-04 4:37 am, Aaron Hill wrote: On 2024-02-04 12:40 am, Rudi Radler wrote: it shows german to me. Okay, this section of the documentation is out-of-date for some translations. For ref

Re: old \alternative-syntax in documentation

2024-02-03 Thread Aaron Hill via bug-lilypond
On 2024-02-03 6:42 am, Rudi Radler via bug-lilypond wrote: https://lilypond.org/doc/v2.25/Documentation/notation/normal-repeats Is this an orphaned doc page? It shows French for me with no option to see the English version. Navigating up one level to the parent index page shows no correspon