|
From: | James |
Subject: | Re: [LSR-v2.18] "Changing stems direction without affecting rests" |
Date: | Fri, 14 Feb 2014 08:37:56 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 |
On 14/02/14 08:27, David Kastrup wrote:
James <address@hidden> writes:On 14/02/14 06:42, David Kastrup wrote:Thomas Morley <address@hidden> writes:Regarding the snippet: Because it is _not_ tagged docs I'd simply delete it.Uh, the snippets tagged "docs" are all imported in LilyPond anyway, so one should just take them from Documentation/snippets/new (if they required changes more than running convert-ly).What I suggest is that instead of doing this piecemeal (one-at-time-as-you-find-them), make a list of the snippets that you are having issues with, then provide them to the group enmasse (use the link or if possible use the name of the snippet - Changing stems direction without affecting rests - for example, as that makes it quicker to find in git and remove them all at once.Well, one problem we definitely have is that a) Documentation/snippets is at version 2.19.2 b) the versions have been upgraded at least to 2.16.0 Actually 2.16 is what we want, so we get lucky here. But the point is that most snippets will not be what is wanted. What one can do for any particular snippet is something like git log -S '\version "2.16.0"' -p Documentation/snippets/new/chant-or-psalms-notation.ly which shows when and how the snippet passed into 2.16.0 and beyond it.
What would one be looking for as such when looking at these snippets found in git log?
Yes, but it's all relative, that is I find what you do in terms of parser/lexer 'tedious' :)It will get very tedious. I have the suspicion that it will be tedious anyway.
Whereas I am sure you trying to make sure that each @node has correct @seealso sections tedious
It's like doing the washing up. http://www.flickr.com/photos/brushbin/12237121625/ ;) I had a postcard of this framed and by my desk for a long time. james
[Prev in Thread] | Current Thread | [Next in Thread] |