lilypond-auto
[Top][All Lists]
Advanced

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

Re: [Lilypond-auto] Issue 3663 in lilypond: Crash with \repeat ... \alte


From: lilypond
Subject: Re: [Lilypond-auto] Issue 3663 in lilypond: Crash with \repeat ... \alternative and \remove "Bar_engraver"
Date: Fri, 22 Nov 2013 15:10:07 +0000

Updates:
        Status: Fixed
        Labels: -Backport_2_18_0 Fixed_2_17_96

Comment #9 on issue 3663 by address@hidden: Crash with \repeat ... \alternative and \remove "Bar_engraver"
http://code.google.com/p/lilypond/issues/detail?id=3663

Pushed to stable/2.18 as
commit e833fd19fca656dd026e5dc57f98be13f11cbd5f
Author: David Kastrup <address@hidden>
Date:   Sun Nov 17 19:29:06 2013 +0100

Issue 3663: Crash with \repeat ... \alternative and \remove "Bar_engraver"

    This approach is just poking around in the dark and removing Scheme
    error messages.  In particular substituting the original glyph for
    left-bar-line and right-bar-line (when missing) in calls to
    span-bar::compound-bar-line seems fishy, and the original logic
    for setting left-bar-broken if left-bar-line is not even present
    is also not clear to me.

    The results for the example in the bug report:
    form = \new Staff \with {
      \remove "Bar_engraver"
    } \repeat volta 2 {
        s1
    } \alternative {
        s1 % first ending
        s1 % second ending
    } % form

    \score {
      <<
        \form
      >>
    } % score
    are also not identical with the 2.16 results: the volta brackets now
    run into each other; before there was a gap.

    It fixes the crash.  I have no idea what a proper fix would look like.


--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings



reply via email to

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