This is an interesting thought, but I think it would require significant reworking of the existing regtests. One of the issues with regtests is that when a bug is found, a regtest is added to demonst
Well, yeah. Hmm... right now I'm imagining a prepsnippet.py, which copies a single snippet. makelsr.py would then call prepsnippet.py on every snippet it normally handles. Not only that, but with a m
Perfect answer -- that's much better than rewriting it for me in an email! The CG recommends using makelsr.py. But I thought than only Neil was authorized to use makelsr.py. So can I use makelsr.py o
With my trademarked "me-ness", the process is that you read the bloody CG 5. http://kainhofer.com/~lilypond/Documentation/devel/contrib-guide/Fixing-snippets-in-LilyPond-sources.html http://kainhofer
Graham Percival a écrit : Ick. Do we really need to ask casual contributors to spend 30 minutes reading how to use git? I think so, see below. Isn't there any faster way to give the instructions? Li
I distinctly remember asking you to do this in January, Too late for that. I suppose that we *could* backport everything to stable/2.12, but I can't see this being worth it. Dunno. Ask him? Umm, conv
Neil, John, Graham, how about considering an LSR upgrade now? Like, before the whole 2.13 bloody mess starts... - How involved would it be? - Do we have to download the lsr archive, update the whole
In message <address@hidden>, Graham Percival <address@hidden> writes On Fri, Feb 06, 2009 at 10:00:04PM +0000, Anthony W. Youngman wrote: In message <address@hidden>, Graham Percival <address@hidden>
Yeah? Let's consider a simple task: make a noun plural. - add an s. - if the word comes from Latin and ends with an "a", add an e. - if the word ends in "oot", add an "s". Unless it also starts with
Technically, somebody could hack into the linux machine and modify the compiler to add malicious code to windows executables. :) No, because nobody will read it. I'll do something about this on the n
Bloody Mao. I knew I couldn't trust google. :/ "... we can't accept proposals for documentation-only work at this time." SoC 2007: http://code.google.com/support/bin/answer.py?answer=60315&topic=1072
Graham, you wrote Friday, October 31, 2008 3:00 PM (why the mao do we still have that headword, anyway? Beethoven's music is some of the rhythmically most boring stuff ever invented. That example ins
No, absolutely not. Hack up the .ly file. Add some \breaks. Pick different music. Whatever. (why the mao do we still have that headword, anyway? Beethoven's music is some of the rhythmically most bor
Huh. I thought it only looked at material inside @lilypond ... oh well. Theoretically we should always add a rule, even if it's just a "cannot process automatically" rule. Practially, I'm not going t
Maybe convert-ly should handle this kind of conversion (see below); to be more explicit, maybe we forgot to add a convert-ly rule (which would have handled this conversion) for this rename. All this
Le lundi 25 février 2008 à 15:33 -0800, Graham Percival a écrit : The problem is, I make so much changes these days that it's difficult to test all of them one at a time with traditional compilati
2008/2/25, Graham Percival <address@hidden>: I'm not sure this is productive way to go about this. Why don't you work in a branch which just contains text fixes? Then you can base your work on the la
Folks, Please bloody test with GUB, especially if you're working on the makefiles and the like. I cannot build the docs now. Yes, I did another rm -rf *; git reset --hard. I am using GUB 2.11.41 and
2007/9/13, Jonas Nyström <address@hidden>: OK. Second and final draft. http://valentin.villenave.info/lilypond/suggestions/ Don't get me wrong -- I have nothing against the projects you mention; I j
I should clarify one point: in only the past three years, I've seen a lot of lilypond's documentation become out of date. That makes me look for long-term solutions for the docs. I really think of th