Misplaced \breathe in the presence of scaled durations

2022-07-17 Thread Johannes Rohrer
Dear LilyPond developers, --- %% The \breathe mark here is not printed next to the c' note with the %% scaled duration, but gets pushed out of the measure to somewhere %% way further right on that line. \version "2.23.9" { c'2*4/5 \breathe s2*1/5 r2 | R1*20 } --- BTW I tried to search

Re: New suggestion to make Lily pond speed up on multiple CPU cores

2022-07-17 Thread Jean Abou Samra
Le 15/07/2022 à 19:10, Arno Waschk a écrit : Hi Jean, thanks for your reply! I was aware of what you demonstrate and elaborate on line breaking, but i tried to stick for pagebreaks in my statement for those very reasons. Umm, if you replace \break with \pageBreak in my example, you will

Aw: Re: New suggestion to make Lily pond speed up on multiple CPU cores

2022-07-17 Thread Arno Waschk
Well the hairpin thing mm ight be a bug for itself, as it happens with (for other reasons whatsoever) wanted pagebrakes as well. The difference I meant was that a pagebreak could in theory split a score in separated smaller scores to be compiled in parallel, and that could be done

Re: Aw: Re: New suggestion to make Lily pond speed up on multiple CPU cores

2022-07-17 Thread Jean Abou Samra
Le 17/07/2022 à 18:24, Arno Waschk a écrit : Well the hairpin thing mm ight be a bug for itself, as it happens with (for other reasons whatsoever) wanted pagebrakes as well. Why would that be a bug? It looks just as expected to me. Hairpins are not the only grobs with such behavior, e.g.,

Re: Misplaced \breathe in the presence of scaled durations

2022-07-17 Thread Jean Abou Samra
Le 17/07/2022 à 15:57, Johannes Rohrer a écrit : Dear LilyPond developers, --- %% The \breathe mark here is not printed next to the c' note with the %% scaled duration, but gets pushed out of the measure to somewhere %% way further right on that line. \version "2.23.9" { c'2*4/5

Request access issue management

2022-07-17 Thread Paulo Matos
Hi, As described in: https://lilypond.org/doc/v2.23/Documentation/contributor/introduction-to-issues My gitlab nick is pmatos, so I can be given appropriate permissions to manage issues. I have also already requests access to the lilypond group. Regards, -- Paulo Matos

Re: Request access issue management

2022-07-17 Thread Jean Abou Samra
Le 17/07/2022 à 20:26, Paulo Matos a écrit : Hi, As described in: https://lilypond.org/doc/v2.23/Documentation/contributor/introduction-to-issues My gitlab nick is pmatos, so I can be given appropriate permissions to manage issues. I have also already requests access to the lilypond group.