Re: Lilypond benchmarking
Keith OHara k-ohara5a5a at oco.net writes: Phil Holmes mail at philholmes.net writes: With ragged-bottom set and annotate spacing, on one of my scores 17.19 shows 49.07 space left and the next system having an extent of 44.7. The next system extent is (-44.70, 4.34) which is a height of 49.04, Given that the first-page extents plus copyright line would leave an estimated (at page-breaking time) space left somewhat less than 49 spaces, I see why LilyPond put the next system on the next page. If I revert the 'clarify' patch, http://codereview.appspot.com/13768045 that extent goes down to (-44.70, 1.31) There are three removed-as-empty staves at the top of that system, so it looks like the 'clarified' code accidentally includes 1.01 staff-space per removed line. Walking through the code and comparing its calculations with hand calculations, I found the problems with the 'clarify' patch and noted them at the Reitveld link above. I do not have time to get a patch to the patch reviewed, and the 'clarify' patch was intended only to make the code easier to understand, so I will revert that patch shortly. The corrected patch can wait until after the next stable release. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: we now have lilypond organization on GitHub
Joseph Rushton Wakeling writes: No doubt about that, but we're not in the situation to fix Windows. Is the problem Windows, or that many of the GNU dependencies are difficult to install on Windows? The biggest problem as I see it, is illustrated by this very thread. Talk, talk, talk, complain, find a hypothetical problem that is not even yours but of a hypothetical contributor, and suggest fixes for others to implement. Investment: time of core contributors, return until now: 0 lines of code. Please stop it. Send a patch that fixes something for you, or not. Greetings, Jan -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
enhancement request - new header field: movement
I've been wanting a movement field in LilyPond's headers. I've managed to make something for myself that is working, more or less, but I'm sure it could be done much better by someone who actually knows what he's doing. My idea is that it should be centered horizontally and be lower on the page than the other fields. That is, the last header field before the printed music. I think having the font the same as the title or maybe on size smaller would work well. I think this would be of general utility for others as well. -David ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: enhancement request - new header field: movement
Hi David, lilypond has a header field piece, which is meant for movement names. To have this field centered - default is left above the score - one has to modify scoreTitleMarkup in paper. Perhaps other markups would be nice. (a markup is a template by itself, because it gets its title/coposer/etc names via \getProperty #'header:...) HTH Best, Jan-Peter On 25.09.2013 13:39, bobr...@centrum.is wrote: I've been wanting a movement field in LilyPond's headers. I've managed to make something for myself that is working, more or less, but I'm sure it could be done much better by someone who actually knows what he's doing. My idea is that it should be centered horizontally and be lower on the page than the other fields. That is, the last header field before the printed music. I think having the font the same as the title or maybe on size smaller would work well. I think this would be of general utility for others as well. -David ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Let make-music accept existing music or alists as source (issue 13904043)
LGTM https://codereview.appspot.com/13904043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Let make-music accept existing music or alists as source (issue 13904043)
2013/9/26 thomasmorle...@gmail.com: LGTM https://codereview.appspot.com/13904043/ Let me add: I started custom-scheme-coding with LilyPond 2.12.3 and found it _very_ difficult to modify music-arguments those days, whereas affecting grobs was quite easy. Now we have 2.17 and after all your work in this area, modifying music has become _much_ easier and so it'll continue with this patch. Simply: Thanks a lot. Harm ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
