Maxim Gawrilow <eldrad.ulthran <at> o2online.de> writes:
> If the initial key sets a note flat (b-flat minor) and I later change this
> note
> to sharp (ges to gis), in the score I get two accidentals in a row: first a
> natural and right to it the sharp. There is no need of the natural, it only
> disturbs.
>
This has been fixed for version 2.14.2
Specifically, given input
{ \key bes\minor gis' eses' es' }
LilyPond prints single sharp for the gis, but prints a natural-flat
for the es, unless you change extraNatural to #f as David indicated.
The thinking is that classical-period music often wrote the extra natural
when a single-flat followed a double-flat, presumably because it looked
strange to write a flat alone when the pitch is /raised/ relative the last
instance of that note, especially when compared to the use of relative
accidentals in baroque music.
A sharp following a flat was much less common in the classical period,
so there is no clear standard notation for that case. I believe there
are zero users who want LilyPond to automatically insert an extra natural
between ges and gis.
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
