lilypond-devel
[Top][All Lists]
Advanced

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

Re: Issue 1471: Invalidate alterations upon key change rather than forge


From: dak
Subject: Re: Issue 1471: Invalidate alterations upon key change rather than forgetting them. (issue4384050)
Date: Tue, 12 Apr 2011 21:29:44 +0000

On 2011/04/12 18:38:11, Keith wrote:
On 2011/04/12 12:55:01, dak wrote:

Only to assure us humans that F-natural was not a mistake.

I think writing f! is a mistake then, because it assures Lilypond that
f-natural should be spelled out.  Assurances for humans belong in
comments, not in code that coincidentally happens to do nothing.

\version "2.13.60" % because 2.12.0 gets the fis wrong

> \new Staff \relative c' {
>   \key e\major
>     \clef treble
>     cis dis! f
>     \clef bass
>     <c dis fis>
> }
>
The e\major version tests less.

I was, among other things, trying to make sense of your example.  The
dis got a reminder accidental to show that an in-key explicit reminder
will also properly be forgotten and consequently not repeated later.

Whatever.  I guess I'll use your proposal without the exclamation mark.
There seems little point in haggling days on end about a regtest.

http://codereview.appspot.com/4384050/



reply via email to

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