bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ping] extraNatural and key changes


From: Phil Holmes
Subject: Re: [Ping] extraNatural and key changes
Date: Fri, 14 Jan 2011 09:47:22 -0000

"Keith OHara" <address@hidden> wrote in message news:address@hidden
On Mon, 13 Dec 2010 14:34:43 -0800, Graham Percival <address@hidden> wrote:

On Mon, Dec 13, 2010 at 10:26 PM, Keith OHara <address@hidden> wrote:
P.S. I would be easily capable of this patch once I figure out git:

I hope that you have read
http://lilypond.org/doc/v2.13/Documentation/contributor/using-lily_002dgit


Dear BugSquad,
The code causing this behavior appeared with git commit "Fix #94. Added support for extraNatural" so the behavior I dislike would have first appeared in 2.10.3. Fixing issue 94 was in the same part of the code, but is logically distinct. Issue 94 concerned where to place cancellation accidentals, not which ones to place.

% extraNatural (controlling naturals before noteheads) and
% printKeyCancellation (affecting groups of naturals before key changes)
% should act independently.
% If the KeyCancellation is printed, as by default, it should contain
% a natural for d and g.
%
\version "2.13.43"
\relative c''{
 \set Staff.extraNatural = ##f
  \key cis\minor des1 \bar "||" \key des\major
}

% Examples Debussy Claire de Lune (Peters Edition 1904)
% Chopin Op10 No6 (Klindworth, Bote&Bock 1880;
%     Hermann Scholtz uses same notation in Peters 1880)


--------------------------------------------------------------------------------


Keith,

You say this appeared in 2.10.3. In which stable release was the behaviour correct?

--
Phil Holmes
Bug Squad






reply via email to

[Prev in Thread] Current Thread [Next in Thread]