Han-Wen Nienhuys writes:
> Concur with graham that it's all subjective and flame material.
>
> I prefer Fedora, because I like being on the bleeding edge and hurting
> myself.
Of the somewhat major distributions, I seem to remember SuSE, Mandriva
and Knoppix to have sort of closed development.
W.r.t the current discussion this might be of interest.
Werner
--- Begin Message ---
This package has been put up at tug.ctan.org and should soon be at your local
mirror
Thanks,
Jim Hefferon
Saint Michael's College
..
2009/5/7 Reinhold Kainhofer :
> 4) cresc = #(make-music 'CrescendoEvent 'span-direction START 'spanner-text
> "cresc.")
I favour this version since its the least ambiguous; there's no risk
of a user trying to make e.g. a 'CrescendoEvent with
'descrescendo-text.
> In particular, the question is
2009/5/9 Carl D. Sorensen :
> Over the past few months, several people have asked for a "N.C." notation to
> be part of the ChordNames context.
>
> It occurred to me that using r to generate a "N.C." would be logically
> consistent -- the music gets a rest, the chord name gets a "N.C.". And if a
>
On 5/9/09 1:58 PM, "Neil Puttock" wrote:
> 2009/5/9 Carl D. Sorensen :
>> Over the past few months, several people have asked for a "N.C." notation to
>> be part of the ChordNames context.
>>
>> It occurred to me that using r to generate a "N.C." would be logically
>> consistent -- the music
2009/5/9 Carl D. Sorensen :
> Similar to the Bass_Figure_engraver, I don't think I want to use
> ASSIGN_EVENT_ONCE (), because even if I have polyphonic rests, I just want
> one N.C. symbol.
<< { r4 } { r8 r } >>
will result in two no-chord symbols unless you assign it once.
> No, I'm proposin
2009/5/7 Patrick McCarty :
> Does anyone have any comments about this patch?
The SVG source is much easier to read. :)
I don't know anything about SVG, so I can only comment on the scheme code:
You're compiling the regexp each time the function's called; would it
be better to define it outside
On 5/9/09 2:44 PM, "Neil Puttock" wrote:
> 2009/5/9 Carl D. Sorensen :
>
>> Similar to the Bass_Figure_engraver, I don't think I want to use
>> ASSIGN_EVENT_ONCE (), because even if I have polyphonic rests, I just want
>> one N.C. symbol.
>
> << { r4 } { r8 r } >>
>
> will result in two no
I've got a problem with this ...
I don't know if it's been dealt with in the documentation but in the
2.12.2 manual section 4.3 (and 12.1.2), this function still uses
no-spacing-rods, which 2.12 doesn't support. I was advised to use
extra-spacing-width so I'm not affected, but anyone who copie
Please review this patch that adds N.C. notations to the ChordNames context.
Patch set 2 is the current patch set.
http://codereview.appspot.com/62076
Thanks,
Carl
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/l
10 matches
Mail list logo
