Paul Scott wrote:
J L wrote:
Hi,
Is there any historical reasons why LilyPond places a natural before a sharp?
i.e. going from A-flat to A-sharp.
\set Staff.extraNatural = ##f
will stop this.
A similar thing happened with a key signature change.
i.e. G major to A major resulted in F-natural + F-sharp & C-sharp & G-sharp
It would be good if there was a way to prohibit this.
\set Staff.printKeyCancellation = ##f
does that.
This is at least true for 2.4.2 and is documented in lilypond-internals and can be accessed from Section 5.6.1 Automatic accidentals in the manual only after choosing one of these links:
See also
Program reference: Accidental_engraver (lilypond-internals) <cid:[EMAIL PROTECTED]> , Accidental (lilypond-internals) <cid:[EMAIL PROTECTED]> , and AccidentalPlacement (lilypond-internals) <cid:[EMAIL PROTECTED]> .
Paul
_______________________________________________ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user
