Re: Issue 3720: Built-in templates for SATB vocal scores (issue 41990043)

2014-01-06 Thread David Kastrup
David Kastrup writes: > And I am not really convinced that if we move to local-eval at some > point of time that we'll be able to get `#{ ... #,... #} to work in a > reasonable time frame. Maybe that will be considered a show stopper > anyway, so we'll stay with the lambda implementation which m

Re: Issue 3720: Built-in templates for SATB vocal scores (issue 41990043)

2014-01-06 Thread David Kastrup
Devon Schudy writes: > dak wrote: >> https://codereview.appspot.com/41990043/diff/60001/ly/satb.ly#newcode97 >> ly/satb.ly:97: \new Staff = #(identity ,name) \with { >> Why #(identity ,name) here instead of #,name ? > > #,name didn't work for some reason, so I wrapped it with identity as a > work

Re: Add Changes entries for bare rhythms and \beamExceptions (issue 47850043)

2014-01-06 Thread tdanielsmusic
On 2014/01/06 18:31:46, dak wrote: >> Ah, but they won't. It's only during scorification that the missing >> pitches get filled in. Now of course there is little point in trying to >> pick a wording that is technically more accurate without the reader >> having a chance to guess that until

Re: Issue 3720: Built-in templates for SATB vocal scores (issue 41990043)

2014-01-06 Thread Devon Schudy
dak wrote: > https://codereview.appspot.com/41990043/diff/60001/ly/satb.ly#newcode97 > ly/satb.ly:97: \new Staff = #(identity ,name) \with { > Why #(identity ,name) here instead of #,name ? #,name didn't work for some reason, so I wrapped it with identity as a workaround. ...but I just tried it a

Re: Add Changes entries for bare rhythms and \beamExceptions (issue 47850043)

2014-01-06 Thread David Kastrup
James writes: > On 06/01/14 18:12, d...@gnu.org wrote: >> On 2014/01/06 16:24:24, t.daniels_treda.co.uk wrote: >>> mailto:d...@gnu.org wrote Monday, January 06, 2014 3:27 PM >> >>> > Maybe one should not try finding a term at all? One might write >>> > something like >>> > >>> > Durations ca

Re: Add Changes entries for bare rhythms and \beamExceptions (issue 47850043)

2014-01-06 Thread dak
On 2014/01/06 16:24:24, t.daniels_treda.co.uk wrote: mailto:d...@gnu.org wrote Monday, January 06, 2014 3:27 PM > Maybe one should not try finding a term at all? One might write > something like > > Durations can now be written in music expressions without an > immediately preceding p

Re: Add Changes entries for bare rhythms and \beamExceptions (issue 47850043)

2014-01-06 Thread James
On 06/01/14 18:12, d...@gnu.org wrote: On 2014/01/06 16:24:24, t.daniels_treda.co.uk wrote: mailto:d...@gnu.org wrote Monday, January 06, 2014 3:27 PM > Maybe one should not try finding a term at all? One might write > something like > > Durations can now be written in music expressions

Re: Add Changes entries for bare rhythms and \beamExceptions (issue47850043)

2014-01-06 Thread Trevor Daniels
d...@gnu.org wrote Monday, January 06, 2014 3:27 PM > Maybe one should not try finding a term at all? One might write > something like > > Durations can now be written in music expressions without an > immediately preceding pitch or chord. In the score, the missing > pitches will b

Re: Add Changes entries for bare rhythms and \beamExceptions (issue 47850043)

2014-01-06 Thread dak
https://codereview.appspot.com/47850043/diff/40001/Documentation/changes.tely File Documentation/changes.tely (right): https://codereview.appspot.com/47850043/diff/40001/Documentation/changes.tely#newcode69 Documentation/changes.tely:69: Well, the original is already in (since it really should g

Re: Double G clef, tenor G clef, varpercussion clef and varC clef (issue 47840043)

2014-01-06 Thread James
On 06/01/14 12:07, Joram Berger wrote: Am 06.01.2014 12:17, schrieb lemzw...@googlemail.com: I've now had some time to check the glyphs. Here my comments. 1. Please make all corners round in `clefs.varC' and `clefs.tenorG'. 2. In `clefs.tenorG', I'm not sure that the left `slanted' end of the

Re: Double G clef, tenor G clef, varpercussion clef and varC clef (issue 47840043)

2014-01-06 Thread Joram Berger
Am 06.01.2014 12:17, schrieb lemzw...@googlemail.com: > I've now had some time to check the glyphs. Here my comments. > > 1. Please make all corners round in `clefs.varC' and `clefs.tenorG'. > > 2. In `clefs.tenorG', I'm not sure that the left `slanted' end of the > top horizontal bar should rea

Re: Double G clef, tenor G clef, varpercussion clef and varC clef (issue 47840043)

2014-01-06 Thread lemzwerg
I've now had some time to check the glyphs. Here my comments. 1. Please make all corners round in `clefs.varC' and `clefs.tenorG'. 2. In `clefs.tenorG', I'm not sure that the left `slanted' end of the top horizontal bar should really look like that. IMHO, it's simply a standard horizontal bar

Re: NR: Update percussion section to make use of issue 3648 (issue 47960043)

2014-01-06 Thread tdanielsmusic
LGTM Trevor https://codereview.appspot.com/47960043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Double G clef, tenor G clef, varpercussion clef and varC clef (issue 47840043)

2014-01-06 Thread Marc Hohl
Am 05.01.2014 11:40, schrieb Werner LEMBERG: [...] Well, you *should* use tabs, so this deserves a new patch set anyway. [...] Done. Marc ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Doc: simplify \score description, matching its current syntax (issue 47900043)

2014-01-06 Thread tdanielsmusic
One suggested improvement, otherwise LGTM Trevor https://codereview.appspot.com/47900043/diff/1/Documentation/learning/fundamental.itely File Documentation/learning/fundamental.itely (right): https://codereview.appspot.com/47900043/diff/1/Documentation/learning/fundamental.itely#newcode271 Do