Re: Issue 1471 in lilypond: accidentals after a clef change are not printed

Updates: Status: Verified Comment #15 on issue 1471 by philehol...@googlemail.com: accidentals after a clef change are not printed http://code.google.com/p/lilypond/issues/detail?id=1471 (No comment was entered for this change.) ___ bug-li

Re: Issue 1471 in lilypond: accidentals after a clef change are not printed

Updates: Status: Fixed Labels: -Patch-review fixed_2_13_60 Comment #14 on issue 1471 by percival.music.ca: accidentals after a clef change are not printed http://code.google.com/p/lilypond/issues/detail?id=1471 pushed in 9ee41ab7352ca3df7aa2ddd8e7097660924f3e36 _

Re: Issue 1471 in lilypond: accidentals after a clef change are not printed

Updates: Labels: -Patch-needs_work Patch-review Comment #13 on issue 1471 by percival.music.ca: accidentals after a clef change are not printed http://code.google.com/p/lilypond/issues/detail?id=1471 The difference is that now I can say that you've done absolutely everything that we

Re: Issue 1471 in lilypond: accidentals after a clef change are not printed

Comment #12 on issue 1471 by d...@gnu.org: accidentals after a clef change are not printed http://code.google.com/p/lilypond/issues/detail?id=1471 I can't really see that this makes any sense or difference, but in order not to be declared the cause for bit rot, here you are. http://codere

Re: Issue 1471 in lilypond: accidentals after a clef change are not printed

Updates: Labels: -Patch-review Patch-needs_work Comment #11 on issue 1471 by percival.music.ca: accidentals after a clef change are not printed http://code.google.com/p/lilypond/issues/detail?id=1471 In light of the confusion about call_context_property_on_children (), and the lack

Re: Issue 1471 in lilypond: accidentals after a clef change are not printed

Comment #10 on issue 1471 by d...@gnu.org: accidentals after a clef change are not printed http://code.google.com/p/lilypond/issues/detail?id=1471 There is no function call_context_property_on_children. There is no evaluation of "the function" (by which you probably mean SCM fun), just a

Re: Issue 1471 in lilypond: accidentals after a clef change are not printed

Comment #9 on issue 1471 by n.putt...@gmail.com: accidentals after a clef change are not printed http://code.google.com/p/lilypond/issues/detail?id=1471 +static void apply_on_children (Context *context, SCM fun) This evaluates the function each time it's recursed; why not instead use call_

Re: Issue 1471 in lilypond: accidentals after a clef change are not printed

Updates: Labels: -Patch-new Patch-review Comment #8 on issue 1471 by colinpkc...@gmail.com: accidentals after a clef change are not printed http://code.google.com/p/lilypond/issues/detail?id=1471 Clean compile and regtest. ___ bug-lilypond

Re: Issue 1471 in lilypond: accidentals after a clef change are not printed

Updates: Labels: Patch-new Comment #7 on issue 1471 by percival.music.ca: accidentals after a clef change are not printed http://code.google.com/p/lilypond/issues/detail?id=1471 A countdown is the appropriate way to absolve yourself of any possible complaint from people who didn't h

Re: Issue 1471 in lilypond: accidentals after a clef change are not printed

Comment #6 on issue 1471 by d...@gnu.org: accidentals after a clef change are not printed http://code.google.com/p/lilypond/issues/detail?id=1471 Due to me messing up with git, you can now conveniently apply the above patch using git cherry-pick 197e3ae339 and take a look at it using g

Re: Issue 1471 in lilypond: accidentals after a clef change are not printed

Comment #5 on issue 1471 by d...@gnu.org: accidentals after a clef change are not printed http://code.google.com/p/lilypond/issues/detail?id=1471 Ok, I think I have a candidate for merging. I made use of the infrastructure for accidentals tied into a new bar (which also need a repetition

Re: Issue 1471 in lilypond: accidentals after a clef change are not printed

Comment #4 on issue 1471 by d...@gnu.org: accidentals after a clef change are not printed http://code.google.com/p/lilypond/issues/detail?id=1471 Ok, here is the full job which passes the regtest without difference in output, but produces the following image for the test file of this bug

Re: Issue 1471 in lilypond: accidentals after a clef change are not printed

Comment #3 on issue 1471 by k-ohara5...@oco.net: accidentals after a clef change are not printed http://code.google.com/p/lilypond/issues/detail?id=1471 The concept behind the half patch is described at : http://lists.gnu.org/archive/html/lilypond-user/2011-04/msg00038.html Myself, I won't

Re: Issue 1471 in lilypond: accidentals after a clef change are not printed

Comment #2 on issue 1471 by d...@gnu.org: accidentals after a clef change are not printed http://code.google.com/p/lilypond/issues/detail?id=1471 Here is a patch that should do half the job. Can anybody make it do the full job? Attachments: invalidate-alterations-on-clef-change.p

Re: Issue 1471 in lilypond: accidentals after a clef change are not printed

Comment #1 on issue 1471 by brownian.box: accidentals after a clef change are not printed http://code.google.com/p/lilypond/issues/detail?id=1471 (for the record) Keith also pointed to the discussion: http://lists.gnu.org/archive/html/bug-lilypond/2010-12/msg00403.html _

Issue 1471 in lilypond: accidentals after a clef change are not printed

Status: Accepted Owner: Labels: Type-Defect Priority-Low New issue 1471 by jameseli...@googlemail.com: accidentals after a clef change are not printed http://code.google.com/p/lilypond/issues/detail?id=1471 Accidentals after a clef change are not printed and should be. \version "2.12.3"