Issue 340 in lilypond: \harmonic only works inside chords

Comment #2 on issue 340 by reinhold.kainhofer: \harmonic only works inside chords http://code.google.com/p/lilypond/issues/detail?id=340 If I understand it correctly, this is because the New_fingering_engraver (absolutely bad name, we should rename it; the documentation even says that this

Re: Harmonic question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 29. Dezember 2008 22:28:13 schrieb Johan Vromans: > Hi, > > I'm trying the TAB \harmonic feature of 2.12. > > Am I right that to get a harmonic, you always need a chord? > > E.g. This works: > > > > but this doesn't: > > e''\harmoni

late instrumentSwitch in MIDI output

In this example, the MIDI output does not switch instruments properly at the beginning of measure five. I'm sorry this is not a very simple example, but small alterations make the problem disappear. (Yes, I realize that this is an abuse of instrumentCueName, but I see no reason why the MIDI outpu

Issue 391 in lilypond: using relative filepath in \include "foo.ly"

Comment #8 on issue 391 by v.villenave: using relative filepath in \include "foo.ly" http://code.google.com/p/lilypond/issues/detail?id=391 I'm concerned that this may break existing code in large projects (such as Nicolas'). Would it be possible to have a switch to enable and disable this

Issue 391 in lilypond: using relative filepath in \include "foo.ly"

Updates: Cc: hanwenn Comment #7 on issue 391 by joeneeman: using relative filepath in \include "foo.ly" http://code.google.com/p/lilypond/issues/detail?id=391 Any opinion on this, Han-Wen? I'm pretty sure this new behaviour would be the cpp behaviour. -- You received this message

Issue 718 in lilypond: it would be nice to have german minor chords

Updates: Status: Duplicate Comment #1 on issue 718 by v.villenave: it would be nice to have german minor chords http://code.google.com/p/lilypond/issues/detail?id=718 Thanks for the request, but see Issue 678 :-) -- You received this message because you are listed in the owner or CC

Issue 716 in lilypond: --disable-optimising causes `Parsed object should be dead'

Updates: Summary: --disable-optimising causes `Parsed object should be dead' Comment #2 on issue 716 by nicolas.sceaux: --disable-optimising causes `Parsed object should be dead' http://code.google.com/p/lilypond/issues/detail?id=716 The problem was indeed introduced by commit b6c67

Issue 718 in lilypond: it would be nice to have german minor chords

Status: New Owner: New issue 718 by jameselihubailey: it would be nice to have german minor chords http://code.google.com/p/lilypond/issues/detail?id=718 In german, minor chords are often notated as lowercase. E.g., "c" instead of "Cm". It would be nice if lilypond supported this. -- Yo