[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: |
Graham Percival |
Subject: |
Re: Issue 1971 in lilypond: Slashed flags no longer work |
Date: |
Mon, 17 Oct 2011 11:41:35 +0100 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
On Mon, Oct 17, 2011 at 08:09:02AM +0100, Neil Puttock wrote:
> On 17 Oct 2011 07:56, "Peekay Ex" <address@hidden> wrote:
>
> > 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.
>
> The CG's pretty clear on this. If the snippets are still valid, the correct
> approach is to move them to snippets/new, with appropriate changes for new
> syntax.
If the snippets can be automatically converted by convert-ly, then
don't touch snippets/new/. We run convert-ly for every lsr import
for precisely this reason.
Mike: did you read the maoing contributor's guide?
"If the modification changes the input syntax, a convert-ly rule
should be written to automatically update input files from older
versions."
http://lilypond.org/doc/v2.15/Documentation/contributor/write-convert_002dly-rule
"
"convert-ly should be used to update the documentation, the
snippets, and the regression tests. This not only makes the
necessary syntax changes, it also tests the convert-ly rules."
http://lilypond.org/doc/v2.15/Documentation/contributor/automatically-update-documentation
"Where the convert-ly rule is not able to automatically update the
inline lilypond code in the documentation (i.e. if a NOT_SMART
rule is used), the documentation must be manually updated."
http://lilypond.org/doc/v2.15/Documentation/contributor/manually-update-documentation
- Graham
- Re: Issue 1971 in lilypond: Slashed flags no longer work, (continued)
Re: Issue 1971 in lilypond: Slashed flags no longer work, address@hidden, 2011/10/17
Re: Issue 1971 in lilypond: Slashed flags no longer work,
Graham Percival <=
Re: Issue 1971 in lilypond: Slashed flags no longer work, Neil Puttock, 2011/10/17
Re: Issue 1971 in lilypond: Slashed flags no longer work, address@hidden, 2011/10/17
Re: Issue 1971 in lilypond: Slashed flags no longer work, address@hidden, 2011/10/17
Re: Issue 1971 in lilypond: Slashed flags no longer work, address@hidden, 2011/10/17
Re: Issue 1971 in lilypond: Slashed flags no longer work, lilypond, 2011/10/17
Re: Issue 1971 in lilypond: Slashed flags no longer work, lilypond, 2011/10/28
Re: Issue 1971 in lilypond: Slashed flags no longer work, lilypond, 2011/10/28
Re: Issue 1971 in lilypond: Slashed flags no longer work, lilypond, 2011/10/29
Re: Issue 1971 in lilypond: Slashed flags no longer work, lilypond, 2011/10/29
Re: Issue 1971 in lilypond: Slashed flags no longer work, lilypond, 2011/10/29