> So if you have some manner of reproducing the problem it would be
> nice if you could check against something like version 2.19.40 so
> that we can at least figure out whether it is the most recent batch
> of changes which is responsible here.
Yes, we need that. A quick look at the recent font handling changes
doesn't show up a modification that would make lilypond suddenly
iterate over all system fonts.
Please provide a minimum example.
Do you have time to bisect the problem?
Werner
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
