[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bugs with \set Staff.whichBar
From: |
Thomas Morley |
Subject: |
Re: Bugs with \set Staff.whichBar |
Date: |
Sun, 25 Nov 2012 01:44:15 +0100 |
2012/11/25 Keith OHara <address@hidden>:
> Ben Rudiak-Gould <benrudiak <at> gmail.com> writes:
>
>> The 2.16 documentation says that \set Staff.whichBar = "|:" "will create a
>> start-repeat bar in this staff only".
>
> I suppose desired behavior is to have at least one way to change one bar-line
> in one staff, preferably the way it was done in version 2.14
> << { R1
> \once\set Staff.whichBar = "|:"
> R1*3 }
> R1*4 >>
> and to have the documentation describe the way that actually works.
>
> Of course the work-around is to explicitly change back
> << { R1
> \set Staff.whichBar = "|:"
> R1
> \unset Staff.whichBar
> R1*2 }
> R1*4 >>
>
>
> _______________________________________________
> bug-lilypond mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
Using code:
<< {
R1
\once \set Staff.whichBar = ".|:"
R1*3
\break
R1*4
}
{
R1
R1*3
\break
R1*4
}
>>
compiles fine with 2.12.3, 2.14.2, 2.16.0 and, after converting (\bar
"|:" -> \bar ".|:") with 2.17.8
But code
<< {
\once \set Staff.whichBar = "|:"
R1*3
\break
R1*4
}
{
R1*3
\break
R1*4
}
>>
works as expected with 2.12.3 and 2.14.2 but gives a segfault with
2.16.0 and 2.17.8 (again after converting)
log:
GNU LilyPond 2.17.8
Processing `atest-01.ly'
Parsing...
Interpreting music...
warning: forced break was overridden by some other event, should you
be using bar checks?
warning: forced break was overridden by some other event, should you
be using bar checks?
Preprocessing graphical objects...
programming error: Multi_measure_rest::get_rods (): I am not spanned!
continuing, cross fingers
Segmentation fault
Regards,
Harm