Now I realize what you mean, sorry. I forward it to bug-lilypond as a bug
report/feature request. As a musician, I completely agree that this should
be done for clarity, still I have seen many printed scores that do not print
out the additional accidentals.
A possible workaround for you is to do
   \clef bass \set Staff.localKeySignature = #'()
or maybe even define a \myclef function that does both in a single call.

  /Mats

Edward Neeman wrote:



*/Mats Bengtsson <[EMAIL PROTECTED]>/* wrote:
If you take a look at the program reference for the Key_engraver, you will
find a property to set to get what you want:
http://lilypond.org/doc/v2.6/Documentation/user/out-www/lilypond-internals/Key_005fengraver.html#Key_005fengraver

/Mats

I checked the key signature page but it doesn't seem to answer my problem. Maybe I should have explained better. When I say the accidentals should be reset after a key change, I mean the first bar in this example should, by default look exactly like the second:

=========================================

\version "2.7.12"
\new Staff \relative c' {
    \clef treble
    cis dis fis
    \clef bass
%% Accidentals are not reset for this chord
    <cis dis fis gis>
    \clef treble
    cis dis fis
    \clef bass
    <cis! dis! fis! gis>
}

\layout {raggedright = ##t}

====================================

I would consider it a bug that lilypond doesn't do this by default.

Cheers,
Edward Neeman

------------------------------------------------------------------------
Do you Yahoo!?
Yahoo! Photos: Now with unlimited storage <http://us.rd.yahoo.com/mail/au/photos/**http%3A%2F%2Fau.photos.yahoo.com%2F>



--
=============================================
        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Sweden
        Phone: (+46) 8 790 8463                         
       Fax:   (+46) 8 790 7260
        Email: [EMAIL PROTECTED]
        WWW: http://www.s3.kth.se/~mabe
=============================================



_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to