Re: addlyrics does not work with an ossia staff

[David Kastrup]

"Phil Holmes"  writes:

> "David Kastrup"  wrote in message
> news:87iny2shdo@fencepost.gnu.org...
>> Simon Albrecht  writes:
>>
>>> Hello Ansgar,
>>>
>>> this is a bug which was fixed in the 2.19 development series, I think
>>> quite early. Anyway, it’s often recommendable to upgrade to current
>>> development versions – a great many advantages have been added since
>>> the last stable release.
>>
>> Maybe we should bite the bullet and just go for 2.20 now.  It's been
>> long enough, and I fear that Guile 2.0 compatibility is not in a state
>> where we could hope to get 2.20 out with it within a narrow time frame.
>> Not least of all because Guile 2.0.12 (containing LilyPond-relevant
>> fixes) has not yet been released.
>>
>
> I think the current issue Knut and James have with compiling the docs
> would prevent 2.20, but I don't see any other reason for not proposing
> a new stable.

2.20 would not happen before at least another month of maturing time, so
for one thing we still have time getting behind this problem.  And if we
don't in a timely manner, 2.20 would not include the commits Knut
identified as being problematic for him.

-- 
David Kastrup

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: addlyrics does not work with an ossia staff

[Phil Holmes]

"David Kastrup"  wrote in message 
news:87iny2shdo@fencepost.gnu.org...

Simon Albrecht  writes:


Hello Ansgar,

this is a bug which was fixed in the 2.19 development series, I think
quite early. Anyway, it’s often recommendable to upgrade to current
development versions – a great many advantages have been added since
the last stable release.


Maybe we should bite the bullet and just go for 2.20 now.  It's been
long enough, and I fear that Guile 2.0 compatibility is not in a state
where we could hope to get 2.20 out with it within a narrow time frame.
Not least of all because Guile 2.0.12 (containing LilyPond-relevant
fixes) has not yet been released.

--
David Kastrup


I think the current issue Knut and James have with compiling the docs would 
prevent 2.20, but I don't see any other reason for not proposing a new 
stable.


--
Phil Holmes



___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: addlyrics does not work with an ossia staff

[David Kastrup]

Simon Albrecht  writes:

> Hello Ansgar,
>
> this is a bug which was fixed in the 2.19 development series, I think
> quite early. Anyway, it’s often recommendable to upgrade to current
> development versions – a great many advantages have been added since
> the last stable release.

Maybe we should bite the bullet and just go for 2.20 now.  It's been
long enough, and I fear that Guile 2.0 compatibility is not in a state
where we could hope to get 2.20 out with it within a narrow time frame.
Not least of all because Guile 2.0.12 (containing LilyPond-relevant
fixes) has not yet been released.

-- 
David Kastrup

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: addlyrics does not work with an ossia staff

[Simon Albrecht]

Hello Ansgar,

this is a bug which was fixed in the 2.19 development series, I think 
quite early. Anyway, it’s often recommendable to upgrade to current 
development versions – a great many advantages have been added since the 
last stable release.


Best, Simon

On 24.05.2016 23:35, Ansgar wrote:

If the overall value of the second staff exhaustes the length of the part
above the following parts are spoiled:


%---
% This one works, but the added staff has only notes of value 1/2
%---

\new Staff \relative c'

{ e4 e e e
   
	<<	

{ e2 e  }
\new Staff { c2  }
\addlyrics{ Ooops! }
>>

{d4 d d d  }

}


%---
% Now an r is added after the c2 and that spoils the following parts
%---

\new Staff \relative c'

{ e4 e e e
   
	<<	

{ e2 e  }
\new Staff { c2 r }
\addlyrics{ Ooops! }
>>

{d4 d d d }

}

\version "2.18.2"
  



___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond



___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond