Re: Issue 602 in lilypond: Feature request: better support for Sacred Harp notation

Comment #36 on issue 602 by rbstoddard: Feature request: better support for Sacred Harp notation http://code.google.com/p/lilypond/issues/detail?id=602 Carl, I'm very happy with these improvements. Thanks for all the work you put into this -- it's a huge improvement for those of us using L

Re: Issue 75 in lilypond: Slurs cannot be nested

Updates: Summary: Slurs cannot be nested Owner: --- Comment #8 on issue 75 by pnorcks: Slurs cannot be nested http://code.google.com/p/lilypond/issues/detail?id=75 Changing the summary to make it more accurate... ___ bug-lilypond mai

Re: Issue 355 in lilypond: \repeat bar lines get messed up

Updates: Owner: --- Comment #2 on issue 355 by percival.music.ca: \repeat bar lines get messed up http://code.google.com/p/lilypond/issues/detail?id=355 Woah, wait a moment -- I'm not being responsible for this issue! We now use the "owner" to indicate "yes, I am working on it".

Re: Issue 355 in lilypond: \repeat bar lines get messed up

Updates: Owner: percival.music.ca Comment #1 on issue 355 by markpolesky: \repeat bar lines get messed up http://code.google.com/p/lilypond/issues/detail?id=355 Neither of these workarounds is fully sufficient. The \partial command seems to have the effect of nullifying the "reset" prop

Re: Issue 1031 in lilypond: constantly-changing input/regression/rest-collision-beam-note.ly

Comment #4 on issue 1031 by pnorcks: constantly-changing input/regression/rest-collision-beam-note.ly http://code.google.com/p/lilypond/issues/detail?id=1031 IIRC, in the past I've seen this happen with input/regression/dot-rest-beam-trigger.ly too. The latest example I can find is the compa

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

Updates: Status: Started Comment #9 on issue 989 by pnorcks: ensure that no information is only in the regtests http://code.google.com/p/lilypond/issues/detail?id=989 (No comment was entered for this change.) ___ bug-lilypond mailing list

Re: Issue 963 in lilypond: check dependency versions for 2.14

Updates: Status: Fixed Labels: fixed_2_13_21 Comment #11 on issue 963 by pnorcks: check dependency versions for 2.14 http://code.google.com/p/lilypond/issues/detail?id=963 Okay, I've finished checking the libraries. I only bumped two of the minimum versions: Fontconfig: 2.4.

Re: Issue 834 in lilypond: midi2ly broken on Windows systems

Updates: Labels: midi2ly Comment #4 on issue 834 by v.villenave: midi2ly broken on Windows systems http://code.google.com/p/lilypond/issues/detail?id=834 Jan, here's an example of a file that I failed to convert using Windows for my video tutorials: http://commons.wikimedia.org/wiki/F

Re: Issue 805 in lilypond: Irrelevant configure message with autoconf and gettext test

Updates: Status: Fixed Owner: pnorcks Labels: fixed_2_13_21 Comment #3 on issue 805 by pnorcks: Irrelevant configure message with autoconf and gettext test http://code.google.com/p/lilypond/issues/detail?id=805 Bumping the minimum Autoconf version appears to have fixed

Re: Issue 602 in lilypond: Feature request: better support for Sacred Harp notation

Comment #35 on issue 602 by Carl.D.Sorensen: Feature request: better support for Sacred Harp notation http://code.google.com/p/lilypond/issues/detail?id=602 The different types of heads are documented in Notation 1.1.4 Noteheads under Shape note heads. There are also regtests for the new

Re: Issue 602 in lilypond: Feature request: better support for Sacred Harp notation

Updates: Labels: -Type-Documentation Type-Enhancement Comment #34 on issue 602 by percival.music.ca: Feature request: better support for Sacred Harp notation http://code.google.com/p/lilypond/issues/detail?id=602 Vaelentin, please don't change the Type of an issue once it's been fixed

Re: Issue 602 in lilypond: Feature request: better support for Sacred Harp notation

Updates: Labels: -Type-Enhancement Type-Documentation Comment #33 on issue 602 by v.villenave: Feature request: better support for Sacred Harp notation http://code.google.com/p/lilypond/issues/detail?id=602 FTR, the Funk heads stuff is now discussed in issue 1060. Carl, I couldn't f

Re: Issue 943 in lilypond: input/regression/slur-broken-trend.ly broken

Updates: Status: Verified Comment #27 on issue 943 by v.villenave: input/regression/slur-broken-trend.ly broken http://code.google.com/p/lilypond/issues/detail?id=943 Although I certainly cannot claim to have understand all of it, the 2.13.20 output now looks correct in both slur-br

Re: Issue 1025 in lilypond: Lyrics with alignAboveContext are not taken into account in Vertical spacing

Updates: Status: Verified Comment #5 on issue 1025 by v.villenave: Lyrics with alignAboveContext are not taken into account in Vertical spacing http://code.google.com/p/lilypond/issues/detail?id=1025 Great job Joe! The output is now excellent. __

Re: Issue 1027 in lilypond: LSR: minimum-Y-extent snippets need to be updated

Updates: Status: Verified Comment #10 on issue 1027 by v.villenave: LSR: minimum-Y-extent snippets need to be updated http://code.google.com/p/lilypond/issues/detail?id=1027 (No comment was entered for this change.) ___ bug-lilypond maili

Re: Issue 1064 in lilypond: Feature request: binding-gutter

Updates: Status: Verified Comment #5 on issue 1064 by v.villenave: Feature request: binding-gutter http://code.google.com/p/lilypond/issues/detail?id=1064 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@g

Re: Issue 1066 in lilypond: postfix \cresc needs to be documented

Updates: Summary: postfix \cresc needs to be documented Status: Verified Labels: -Type-Enhancement Type-Documentation Comment #3 on issue 1066 by v.villenave: postfix \cresc needs to be documented http://code.google.com/p/lilypond/issues/detail?id=1066 I'm closing this

Re: Issue 1071 in lilypond: [PATCH] Parser docfix for tokenization of music function signatures

Updates: Status: Verified Comment #2 on issue 1071 by v.villenave: [PATCH] Parser docfix for tokenization of music function signatures http://code.google.com/p/lilypond/issues/detail?id=1071 (No comment was entered for this change.) ___ b

Re: Issue 1072 in lilypond: PATCH: Doc: Clarify \relative inside \repeat issue.

Updates: Labels: -fixed_2_13_20 fixed_2_13_21 Comment #3 on issue 1072 by v.villenave: PATCH: Doc: Clarify \relative inside \repeat issue. http://code.google.com/p/lilypond/issues/detail?id=1072 The change doesn't appear yet on the online 2.13.20-numbered docs.

Re: Issue 1070 in lilypond: [PATCH] Fix #915 (faulty full-bar rest positioning with clef). (issue931041)

Updates: Status: Verified Mergedinto: -915 Comment #2 on issue 1070 by v.villenave: [PATCH] Fix #915 (faulty full-bar rest positioning with clef). (issue931041) http://code.google.com/p/lilypond/issues/detail?id=1070 (No comment was entered for this change.) ___

Re: Issue 1069 in lilypond: [PATCH] Fix #943 (issue956051)

Updates: Status: Verified Mergedinto: -943 Comment #3 on issue 1069 by v.villenave: [PATCH] Fix #943 (issue956051) http://code.google.com/p/lilypond/issues/detail?id=1069 (No comment was entered for this change.) ___ bug-lilypond mai

Re: Issue 1067 in lilypond: Postfix syntax for repeats

Updates: Status: Verified Comment #3 on issue 1067 by v.villenave: Postfix syntax for repeats http://code.google.com/p/lilypond/issues/detail?id=1067 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.or

Re: Issue 1036 in lilypond: Links to accented anchors

Updates: Status: Started Owner: paconet.org Labels: -Priority-Postponed Priority-High Comment #1 on issue 1036 by percival.music.ca: Links to accented anchors http://code.google.com/p/lilypond/issues/detail?id=1036 Good news: I think the problem is in the xrefs, which mea