Re: Using \partcombine and \lyricsto

On Mon, 2005-01-24 at 01:02 +0100, Han-Wen Nienhuys wrote: > [EMAIL PROTECTED] writes: > > Does anyone have any comments or ideas for better approaches? I'm > > particularly concerned about tossing in a named staff instead of a named > > voice for \lyricsto. Is there a better way to specify this

Using \partcombine and \lyricsto

[EMAIL PROTECTED] writes: > Does anyone have any comments or ideas for better approaches? I'm > particularly concerned about tossing in a named staff instead of a named > voice for \lyricsto. Is there a better way to specify this > syntactically? > I'm still curious about your patch. Have I mis

Re: Lilypond 2.5.8 crashes with any input

It turns out that I liked lilypond so ineptly that it loaded two different versions of freetype simultaneously. When correcting this, everything ran fine. Matthias ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/lis

Re: Lilypond 2.5.8 crashes with any input

[back to ML] [EMAIL PROTECTED] writes: > > The stacktrace (with the 0x0 markup variable) looks bogus to > > me. Are you sure that Pango does work in other apps? > > It works in etherape, although that obviously doesn't exercise nearly > as much functionality. > > > What version of Pango are y

in 2.5.8 connecting arpeggioBracket not works as in 1.6 version

The code: \context PianoStaff << \set PianoStaff.connectArpeggios = ##t \new Staff { \arpeggioBracket \arpeggio } \new Staff { \arpeggioBracket \clef bass \arpeggio } >> and the code \context PianoStaff << \set PianoStaff.connectArpeggios = ##t \new Staff {

Re: lilypond ./ChangeLog Documentation/user/changin...

On 22-Jan-05, at 3:58 AM, Mats Bengtsson wrote: +This sets the vertical size of the current staff to 4 staff spaces on +either side of the center staff line. I guess that this should be "3 staff spaces" instead. Thanks; fixed in CVS. - Graham ___ lilypon

Re: feature request: tunable cresc/decresc on newline

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jan 23, 2005, at 1:51 AM, Graham Percival wrote: If a cresc or decresc ends on the first note of a system, LilyPond prints a tiny < or > on that new system. Could we make this tunable? ie provide the option to not print the cresc on the new system?

docs pointing to ly/propert-init.ly

I think we should include ly/property-init.ly in the documentation as an appendix. (something like "C.4 Predefined commands") I'm sure that there's a way to automatically generate such documentation (similar to the way the internals docs are created), but I don't have a clue how to do this. Coul

Re: example question

On 22-Jan-05, at 2:53 AM, Han-Wen Nienhuys wrote: in SATB vocal score and piano reduction why are you doing \new PianoStaff << \new Staff << \context Lyrics = tenors \lyricsto tenors \tenorWords \context Lyrics = basses \lyricsto basses \bassWords I have no idea. Those lines should

feature request: tunable cresc/decresc on newline

If a cresc or decresc ends on the first note of a system, LilyPond prints a tiny < or > on that new system. Could we make this tunable? ie provide the option to not print the cresc on the new system? I'm not certain what proper engraving practice is, but the tiny < looks a bit weird. \version "2.

Feature request: auto-indent for instrument name

I don't know how feasible this is, but it would be great if LilyPond could automatically set \layout{ indent = #x.0 } to allow space for the instrument name. \version "2.4.2" { \set Staff.instrument = "Foo foo foo bar" c'4 } ___ lilypond-devel mailin

mi2ly

mi2ly is now on savannah.nongnu.org/download/mi2ly Ciao, Antonio ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel