[Top][All Lists]

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

Re: Issue 1971 in lilypond: Slashed flags no longer work

From: Peekay Ex
Subject: Re: Issue 1971 in lilypond: Slashed flags no longer work
Date: Mon, 17 Oct 2011 07:56:33 +0100

Mike, Phil,

On Mon, Oct 17, 2011 at 7:16 AM, address@hidden
<address@hidden> wrote:
> On Oct 16, 2011, at 12:06 PM, address@hidden wrote:
>> Status: Accepted
>> Owner: ----
>> Labels: Type-Critical Regression
>> New issue 1971 by address@hidden: Slashed flags no longer work
>> http://code.google.com/p/lilypond/issues/detail?id=1971
>> The NR 
>> (http://lilypond.org/doc/v2.15/Documentation/notation/special-rhythmic-concerns)says:
>> "The slash through the stem found in acciaccaturas can be applied in other 
>> situations
>> \relative c'' {
>>  \override Stem #'stroke-style = #"grace"
>>  c8( d2) e8( f4)
>> }"
>> However, between 2.15.7 and 15.9 the slash has disappeared.  Labelling this 
>> as critical, even if it might have been intended, since if there is an 
>> alternative we should document it in the appropriate place.

> I believe this problem can't be fixed, as all the files to which you're 
> referring are on the LSR, which (I think) uses a pre-flag-grob version of 
> LilyPond.  Thus, if they were changed on the LSR, they would run into compile 
> problems.
> I can, however, manually edit the docs (in spite of the fact that the files 
> in question have comments saying that they should not be manually edited).
> What would be nice is to have the LSR completely decoupled from the doc build 
> so that this sorta thing didn't come up.  I have not followed the discussions 
> on the list about the LSR as actively as I could have, so I'm sorry if I'm 
> covering old turf!

You are (Hi Graham!) :)

However, and this is for Phil: could we not simply 'deprecate' the
snippet(s) like we do with any that won't work (properly) in later
versions, and actually I think it was Mike that a week or so ago
pointed one out to me that was deprecated as of 2.14.x, because the
snippet said 'I am deprecated' in the compiled the docs. Then
eventually I just went back and removed the @snippet ref.

Sounds pretty standard stuff.


reply via email to

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