2012/10/4 Eluze <[email protected]>: [...] > I consider the LSR a valuable addition to the regular LilyPond and I have > used a lot of those snippets - sometimes I changed a little bit sometimes I > used the original. now if I can't use the solutions I have elaborated some > time ago - and I believe many other users have benefited from this source - > I will have to be very careful about relying to these snippets: I can't > update them with convert-ly and I have no Scheme skill to make them work > again.
Sure. The LSR is *very* useful. And ofcourse the problem of an outdated LSR _is_ relevant! > (just thinking if the LSR should not be checked against regressions > before a new version can be released - I know this would delay releases by > days or weeks, but in the end you're looking for a better release and not > for more trouble.) I don't think that this will ever work, [...] > - has anybody an idea why these strange output files are created? As I wrote before, noone on devel could help. Contacting Seba (the LSR-maintainer) wasn't succesfull. > - are there alternatives to host a collection of additional snippets - I > must confess I like the actual form, even if there are a few things to > improve. Well, I hesitate to change anything _in_ LSR until Seba replied. We could start updating as a more privat project. Means: updating the relevant files and providing them locally on our own computers. I could do that or, at least, start with it. But does this _really_ make sense? > - start a new issue? AFAIK, the LSR is an associated project, not part of the source in any way. So why start a new issue? > > Eluze -Harm _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
