PATCHES: Countdown for July 30th 2014

Hello, Here is the current patch countdown list. The next countdown will be on July 30th. You can always view the most current countdown list here: http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaiting&colspec=Patch%20Owner%20ID%20Summary&sort=patch __

Issue 4019: binding-offset not properly scaled along with paper size (issue 112500043 by d...@gnu.org)

LGTM. https://codereview.appspot.com/112500043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Remove obsolete restrictions from define-*-function docstrings (issue 115840045 by d...@gnu.org)

LGTM. https://codereview.appspot.com/115840045/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Doc: NR - Pitches.itely - dodecaphonic-no-repeat text alt (issue 116990043 by pkx1...@gmail.com)

LGTM. https://codereview.appspot.com/116990043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Issue 4026: Make list of `non-staff lines' easier to find in IR. (issue 119060044 by markpole...@gmail.com)

LGTM. https://codereview.appspot.com/119060044/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

DOC: minor revisions to Easier Editing (issue 118350043 by colinpkcampb...@gmail.com)

Reviewers: , Message: This is a bit of housekeeping, coming from research for a recent presentation of LilyPond to a group of church musicians. Description: DOC: minor revisions to Easier Editing Moved tunefl per comment 1 issue 2660 Moved LilyPondTool to "No longer developed" per Bertalan Fodo

Re: [bounty] context generating function - how to get context def from its name?

Hi David & all, 2014-07-25 21:34 GMT+02:00 David Kastrup : > > Janek Warchoł writes: >> 2) i didn't manage to get midi stuff done inside the same function as >> the layout stuff - but i think that i'll be able to solve that if i >> have a solution to 1). > > You basically need to collect just the

Re: Set X-parent of TextScript to NoteColumn instead of PaperColumn (issue 106640043 by janek.lilyp...@gmail.com)

On 2014/07/26 06:49:41, janek wrote: Setting TextScript.cross-staff property to #f is required to ensure that there are no collisions between TextScripts and cross-staff notes: (see also beam-cross-staff-auto-knee.ly) As far as I can see, we don't want TextScript.cros

Re: Simplify the NullVoice context (issue 117050043 by k-ohara5...@oco.net)

Hi Keith, sorry for writing so late - i didn't notice this patch until yesterday and i didn't have time for reviewing it today... The changes looks promising! I'll give it a closer look tomorrow, hopefully in the morning. best, Janek https://codereview.appspot.com/117050043/ _

Simplify the NullVoice context (issue 117050043 by k-ohara5...@oco.net)

https://codereview.appspot.com/117050043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Have git SHA1 ID's changed in the last 5 years?

2014-07-26 20:45 GMT+02:00 Mark Polesky : > On Dec 17 2009, with commit #05eb689, I tracked down the > "birth commits" for the individual manuals in order to > establish the initial years for copyright purposes: > > http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=05eb689 > > But n

Have git SHA1 ID's changed in the last 5 years?

On Dec 17 2009, with commit #05eb689, I tracked down the "birth commits" for the individual manuals in order to establish the initial years for copyright purposes: http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=05eb689 But now I see that none of the commit numbers I documented

Re: some working grob properties are unlisted?

James wrote: >> How is that list even generated? I can't figure it out >> from the source code. > > git grep 01e371f James, I know that the IR is auto-generated, I'm actually the one who added the line you're referencing: http://git.sv.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=05eb689 What

Re: some working grob properties are unlisted?

On 26/07/14 00:33, Mark Polesky wrote: > David Nalesnik wrote: >>> I noticed that the 'baseline-skip property works with the >>> InstrumentName grob, which confuses me, because in the IR >>> entry for IntsrumentName, none of the supported interfaces >>> listed at the bottom provide the 'baseline-sk

Re: some working grob properties are unlisted?

On Sat, Jul 26, 2014 at 8:25 AM, David Nalesnik wrote: > > > I think we should also add font-interface, as InstrumentName responds to > font-shape, for example. > > Already included :) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists

Re: some working grob properties are unlisted?

On Fri, Jul 25, 2014 at 6:33 PM, Mark Polesky wrote: > David Nalesnik wrote: > >> I noticed that the 'baseline-skip property works with the > >> InstrumentName grob, which confuses me, because in the IR > >> entry for IntsrumentName, none of the supported interfaces > >> listed at the bottom prov