Re: Issue 915 in lilypond: Multi-measure rests dependent on prefatory matter in other staves

Updates: Owner: --- Comment #5 on issue 915 by pnorcks: Multi-measure rests dependent on prefatory matter in other staves http://code.google.com/p/lilypond/issues/detail?id=915 I forgot to unmark the Owner field for this issue. I still think the commits from comment 1 are the culprit

Re: Issue 995 in lilypond: tuplets at the begin of a piece cannot begin with a \tempo indication

Updates: Summary: tuplets at the begin of a piece cannot begin with a \tempo indication Comment #3 on issue 995 by reinhold.kainhofer: tuplets at the begin of a piece cannot begin with a \tempo indication http://code.google.com/p/lilypond/issues/detail?id=995 Actually, tuplets can start

Re: Issue 995 in lilypond: tuplets cannot begin with a \tempo indication

Comment #2 on issue 995 by v.villenave: tuplets cannot begin with a \tempo indication http://code.google.com/p/lilypond/issues/detail?id=995 Here's what I said back then, but I'm not so sure now that you're asking. "I think it's probably just a limitation that needs to be documented: tuplets

Re: Issue 989 in lilypond: ensure that no information is only in the regtests

Comment #6 on issue 989 by v.villenave: ensure that no information is only in the regtests http://code.google.com/p/lilypond/issues/detail?id=989 Thanks for posting this howto, Graham. I've been ill for a few days and it's not getting any better, but I'll go on with the regtest-review as so

Re: Issue 1044 in lilypond: strip-whitespace in lily-git

Comment #2 on issue 1044 by percival.music.ca: strip-whitespace in lily-git http://code.google.com/p/lilypond/issues/detail?id=1044 I have many patches from James that contained whitespace errors. However, it's quite possible that he wasn't using the latest lily-git. Let me check and get b

Re: Issue 1044 in lilypond: strip-whitespace in lily-git

Comment #1 on issue 1044 by Carl.D.Sorensen: strip-whitespace in lily-git http://code.google.com/p/lilypond/issues/detail?id=1044 Doesn't it strip whitespace? I intended it to. Hence the command git rebase --whitespace=fix HEAD^ as part of the commit. This is supposed to fix the whitespace

Re: Issue 1042 in lilypond: Broken regtest: spanner-break-overshoot.ly

Updates: Status: Invalid Comment #2 on issue 1042 by n.puttock: Broken regtest: spanner-break-overshoot.ly http://code.google.com/p/lilypond/issues/detail?id=1042 This isn't a regression: the left-broken bracket briefly became visible with 2.13.15 following the recent patch for tupl

Re: Issue 678 in lilypond: Enhancement: Add option to make moll chords small

Comment #5 on issue 678 by n.puttock: Enhancement: Add option to make moll chords small http://code.google.com/p/lilypond/issues/detail?id=678 Hraban, this patch is incomplete, since `conditional-string-downcase' isn't defined; the following code should be added to prevent crashes: (defin

Re: Issue 669 in lilypond: \override 'bar-size + \remove Staff_symbol_engraver = mess with ties and slurs

Comment #5 on issue 669 by percival.music.ca: \override 'bar-size + \remove Staff_symbol_engraver = mess with ties and slurs http://code.google.com/p/lilypond/issues/detail?id=669 Some doc helper or bug squad person: - did Patrick add a @knownissue to the docs like he said he would, 18 mont

Re: Issue 995 in lilypond: tuplets cannot begin with a \tempo indication

Comment #1 on issue 995 by percival.music.ca: tuplets cannot begin with a \tempo indication http://code.google.com/p/lilypond/issues/detail?id=995 Why is this documentation? Is it because the problem only occurs at the beginning of a piece, i.e. it's like beginning a piece with a chord and

Re: Issue 68 in lilypond: certain \paper variables put music at the bottom of the page (easy workaround)

Updates: Owner: --- Comment #7 on issue 68 by n.puttock: certain \paper variables put music at the bottom of the page (easy workaround) http://code.google.com/p/lilypond/issues/detail?id=68 Hi James, The spacing engine has changed so much since this bug was reported, I'm not sure

Re: Issue 989 in lilypond: ensure that no information is only in the regtests

Comment #5 on issue 989 by percival.music.ca: ensure that no information is only in the regtests http://code.google.com/p/lilypond/issues/detail?id=989 Unfortunately, most of the regtests that Valentin picked out don't have anything to do with the NR, so it's not your concern. The first on

Re: Issue 989 in lilypond: ensure that no information is only in the regtests

Comment #4 on issue 989 by pkx1...@hotmail.com: ensure that no information is only in the regtests http://code.google.com/p/lilypond/issues/detail?id=989 I can help with the NR stuff. I have looked at the Wiki but don't really understand what it is that needs documenting. Sorry to be slow.

Re: Issue 68 in lilypond: certain \paper variables put music at the bottom of the page (easy workaround)

Comment #6 on issue 68 by pkx1...@hotmail.com: certain \paper variables put music at the bottom of the page (easy workaround) http://code.google.com/p/lilypond/issues/detail?id=68 hello, see attached file. The 2.13.10 code (and I assume the latest *.17) has different spacing. If someone c

Issue 1044 in lilypond: strip-whitespace in lily-git

Status: Accepted Owner: Labels: Type-Scripts Priority-High Maintainability Frog New issue 1044 by percival.music.ca: strip-whitespace in lily-git http://code.google.com/p/lilypond/issues/detail?id=1044 It would be nice if lily-git automatically called scripts/auxiliary/strip-whitespace.py b