On Fri, Mar 19, 2021, 7:09 PM Knut Petersen
wrote:
> Now the second part of my tests. A score typical for my usage of
> lilypond. 96 bars, SATB divisi, 13 pages A4.
>
I wonder what the Carver MSDM score would look like. Searching the
archives, it's seemingly become an informal standard for larg
Le 17/03/2021 à 20:10, Jonas Hahnfeld a écrit :
Hi all,
there are currently 1066 open issues at LilyPond's GitLab repository:
https://gitlab.com/lilypond/lilypond/-/issues
I'd like to reduce this number: In the short term, I propose to close
issues with ~Patch::abandoned (69 open issues) and ~
Hi everybody,
Indeed. I understand memory usage has been higher for LilyPond with post-1.8
guile versions. Was any of that notable in these tests?
I only measured execution time, sorry. Memory is not a scarce resource on my
system.
Now the second part of my tests. A score typical for my usa
Am Freitag, dem 19.03.2021 um 10:41 -0500 schrieb Karlin High:
> On 3/19/2021 8:03 AM, Knut Petersen wrote:
> > Building lilypond 'master' with guile 'master' looks promising:
>
> Indeed. I understand memory usage has been higher for LilyPond with
> post-1.8 guile versions. Was any of that notabl
Am Freitag, dem 19.03.2021 um 08:32 +0100 schrieb Jonas Hahnfeld:
> Hi all,
>
> for your information and to prevent others from wondering: The bug fix
> release 1.48.3 of Pango breaks LilyPond's processing with multiple
> jobs. See https://gitlab.gnome.org/GNOME/pango/-/issues/542 and
> https://gi
On 3/19/2021 8:03 AM, Knut Petersen wrote:
Building lilypond 'master' with guile 'master' looks promising:
Indeed. I understand memory usage has been higher for LilyPond with
post-1.8 guile versions. Was any of that notable in these tests?
--
Karlin High
Missouri, USA
On 10.03.21 05:45, Dr. Arne Babenhauserheide wrote:
Hi, there’s a Guile 3.0.6 release planned that includes a rewrite of the reader in Scheme. It has speed in the same order of magnitude as the previous reader but might have different performance characteristics. If I remember correctly, lilypond
Hi all,
for your information and to prevent others from wondering: The bug fix
release 1.48.3 of Pango breaks LilyPond's processing with multiple
jobs. See https://gitlab.gnome.org/GNOME/pango/-/issues/542 and
https://gitlab.com/lilypond/lilypond/-/issues/6105 for more details.
Arch Linux already
