Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation
Updates: Labels: -Patch-new Patch-review Comment #5 on issue 1873 by pkx1...@gmail.com: Added glyphs for Kievan Notation http://code.google.com/p/lilypond/issues/detail?id=1873 Passes make and reg tests ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented
Comment #35 on issue 1776 by n.putt...@gmail.com: Doc: NR - Polymetric Notation \compoundMeter isn't documented http://code.google.com/p/lilypond/issues/detail?id=1776 Neil can you check this is ok? There's a bit of a mix-up between removal and deprecation. For the deprecated snippet, you should leave the texidoc string as it is, but remove the code below the \markup block (take a look at one of the snippets already deprecated for 2.14 to see what I mean). Once you've done this, run makelsr.py to copy the new contents from snippets/new to snippets/. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented
Comment #34 on issue 1776 by pkx1...@gmail.com: Doc: NR - Polymetric Notation \compoundMeter isn't documented http://code.google.com/p/lilypond/issues/detail?id=1776 New patch loaded with snippet removed and makelsr.py run. http://codereview.appspot.com/4837050/ Neil can you check this is ok? Else I have another patch - before the move of the snippet and the makelsr.py that I can apply (this is effectively Patch Set 7) of the Rietveld issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display
Comment #11 on issue 1503 by janek.li...@gmail.com: Feature request: simplify jazz chord display http://code.google.com/p/lilypond/issues/detail?id=1503 Patch by Adam here: http://codereview.appspot.com/4981052/ ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1572 in lilypond: Change chord name separator and inversion separator, separately
Comment #5 on issue 1572 by janek.li...@gmail.com: Change chord name separator and inversion separator, separately http://code.google.com/p/lilypond/issues/detail?id=1572 Patch by Adam here: http://codereview.appspot.com/4981052/ ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1193 in lilypond: Enhancement: internal ledger lines
Comment #16 on issue 1193 by colinpkc...@gmail.com: Enhancement: internal ledger lines http://code.google.com/p/lilypond/issues/detail?id=1193 @Neil and Piers: Can we merge issues 1193 (Internal Leger Lines) and 1292 (Twelve-Notation Support)? It seems to me that 1292 is a special case of which 1193 is the general. Cheers, Colin ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented
Comment #33 on issue 1776 by n.putt...@gmail.com: Doc: NR - Polymetric Notation \compoundMeter isn't documented http://code.google.com/p/lilypond/issues/detail?id=1776 OK, I'll get in touch with Seba to organize things. TBH, I'd like to monitor it more carefully this time since the last update was a disaster. We ended up with duplicated docstrings which I had to remove manually. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented
Comment #32 on issue 1776 by percival.music.ca: Doc: NR - Polymetric Notation \compoundMeter isn't documented http://code.google.com/p/lilypond/issues/detail?id=1776 2.14.2, and then clear out everything in Documentation/snippets/new/ that can live on 2.14. Feel free to recruit volunteers to add those snippets. By the time you (and/or volunteers) have finished that, it'll probably be time to bump it up to 2.16.1 or so. I don't recommend waiting; the task is less daunting if you do it in increments. And ideally, you should add instructions on upgrading LSR to a new version to the CG, and then we could try to get somebody else to do the 2.16 upgrade (following those instructions). Reinhold has some effort to build LSR locally, but I don't have the url handy, and in any case that's still weeks away so I think it's worth upgrading the current LSR. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1193 in lilypond: Enhancement: internal ledger lines
Comment #15 on issue 1193 by pkx1...@gmail.com: Enhancement: internal ledger lines http://code.google.com/p/lilypond/issues/detail?id=1193 Colin, http://codereview.appspot.com/4974075/ is for this issue (as well as issue 1292) James ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented
Comment #31 on issue 1776 by pkx1...@gmail.com: Doc: NR - Polymetric Notation \compoundMeter isn't documented http://code.google.com/p/lilypond/issues/detail?id=1776 Neil, thanks. Can you change the 'texidoc' string in the LSR so that at least that way the people with the older code can still use the old function? It isn't so much the old function is deprecated (well it is) but what I mean is that the old way still works, we have just made a proper function and so the 'tweak/hack' isn't necessary anymore. The hack still works with the current 2.15 tree no problems. For my patch, I'll change the snippet in git as per Carl's note - thanks Carl I see I still am using CG 2.15.5 for my reference so missed this relatively recent addition to CG 10.x. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented
Comment #30 on issue 1776 by n.putt...@gmail.com: Doc: NR - Polymetric Notation \compoundMeter isn't documented http://code.google.com/p/lilypond/issues/detail?id=1776 Of course, I'm including myself in the list of people who could've removed them. :) Do you want LSR on 2.14 or 2.16? I'm happy to liaise with Seba to sort it out. I did have a look at Jon's script a few weeks ago (y'know, the snippet checker), and have a few improvements to add to the CG when I get the chance, since it doesn't pick up all failures. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented
Comment #29 on issue 1776 by percival.music.ca: Doc: NR - Polymetric Notation \compoundMeter isn't documented http://code.google.com/p/lilypond/issues/detail?id=1776 oh, I remember all right. That's why I was sending all of those "nobody loves LSR" emails over the summer. If nobody is interested in maintaining LSR, then obviously the "snippets in the documentation" effort will be stalled. 2.16 will be out soon, and LSR still hasn't been updated to 2.14. I hate seeing routine maintenance being ignore until it piles up to become a huge problem, but since there's a huge outpouring of emails in support of LSR whenever I suggest that we drop it, I'm buggered if I'll be the person to take responsibility for it. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1193 in lilypond: Enhancement: internal ledger lines
Comment #14 on issue 1193 by n.putt...@gmail.com: Enhancement: internal ledger lines http://code.google.com/p/lilypond/issues/detail?id=1193 Neil, should http://codereview.appspot.com/1855056/ be closed, then? I guess so. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented
Comment #28 on issue 1776 by n.putt...@gmail.com: Doc: NR - Polymetric Notation \compoundMeter isn't documented http://code.google.com/p/lilypond/issues/detail?id=1776 True, it does recommend that, but nobody remembers to do it when there's a new release. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented
Comment #27 on issue 1776 by carl.d.s...@gmail.com: Doc: NR - Polymetric
Notation \compoundMeter isn't documented
http://code.google.com/p/lilypond/issues/detail?id=1776
CG section 10.9.5 describes the process:
Where snippets in Documentation/snippets are made obsolete, the snippet
should be copied to Documentation/snippets/new. The comments and texidoc
strings should be removed as described above. Then the body of the snippet
should be changed to:
\markup {
This snippet is deprecated as of version X.Y.Z and
will be removed from the documentation.
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1193 in lilypond: Enhancement: internal ledger lines
Comment #13 on issue 1193 by colinpkc...@gmail.com: Enhancement: internal ledger lines http://code.google.com/p/lilypond/issues/detail?id=1193 @12: James, is this this this this or this one? @11: Neil, should http://codereview.appspot.com/1855056/ be closed, then? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented
Comment #26 on issue 1776 by n.putt...@gmail.com: Doc: NR - Polymetric Notation \compoundMeter isn't documented http://code.google.com/p/lilypond/issues/detail?id=1776 It's easiest to remove both snippets manually. If you run makelsr.py it won't remove the snippet copied from /new unless you do a full update and the LSR snippet's `doc' tag's been removed. I've disabled the tag in LSR so it won't cause the snippet to return like a bad penny. :) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented
Updates: Labels: -Patch-needs_work Patch-review Comment #25 on issue 1776 by pkx1...@gmail.com: Doc: NR - Polymetric Notation \compoundMeter isn't documented http://code.google.com/p/lilypond/issues/detail?id=1776 Hello, new patch uploaded - as I had to redo it completely I felt it appropriate to make a new patch for review. It compiles fine. http://codereview.appspot.com/4837050/ This patch does not remove the snippet itself and the CG doesn't really go into detail on what to do when one wants to remove a snippet from git that is in the LSR. 1. Do I just remove the ly files from ..\snippets\.. and ..\snippets\new\... and then make a new patch, or do I also need to run a makelsr.py as well and THEN make a new patch or something else? 2. Does someone also need to remove this from the LSR as well - I don't know how or, I think, have permissions to do that. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2
Updates: Labels: -Patch-review Patch-new Comment #13 on issue 1780 by pkx1...@gmail.com: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2 http://code.google.com/p/lilypond/issues/detail?id=1780 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2
Updates: Labels: Patch-review Comment #12 on issue 1780 by ianhuli...@gmail.com: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2 http://code.google.com/p/lilypond/issues/detail?id=1780 Hi all, A patch is available for review at http://codereview.appspot.com/4974078 Regression tests showed some performance improvements. Cheers Ian Hulin ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation
Updates: Owner: janek.li...@gmail.com Comment #4 on issue 1873 by percival.music.ca: Added glyphs for Kievan Notation http://code.google.com/p/lilypond/issues/detail?id=1873 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display
Updates: Owner: janek.li...@gmail.com Labels: -Priority-Medium Comment #10 on issue 1503 by percival.music.ca: Feature request: simplify jazz chord display http://code.google.com/p/lilypond/issues/detail?id=1503 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1228 in lilypond: \override RestCollision #'positioning-done = #merge-rests-on-positioning
Updates: Status: Accepted Labels: -Priority-Low Comment #11 on issue 1228 by percival.music.ca: \override RestCollision #'positioning-done = #merge-rests-on-positioning http://code.google.com/p/lilypond/issues/detail?id=1228 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1572 in lilypond: Change chord name separator and inversion separator, separately
Updates: Owner: janek.li...@gmail.com Labels: -Priority-Low Comment #4 on issue 1572 by percival.music.ca: Change chord name separator and inversion separator, separately http://code.google.com/p/lilypond/issues/detail?id=1572 could we always have an Owner for a "started" thing? In the case of frogs / casual contributors, mark them as Janek. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation
Updates: Labels: -Patch-needs_work Patch-new Comment #3 on issue 1873 by pkx1...@gmail.com: Added glyphs for Kievan Notation http://code.google.com/p/lilypond/issues/detail?id=1873 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1852 in lilypond: manuals needs more explicit dependencies
Updates: Status: Started Labels: -Patch-needs_work Patch-review Comment #7 on issue 1852 by pkx1...@gmail.com: manuals needs more explicit dependencies http://code.google.com/p/lilypond/issues/detail?id=1852 Passes make and reg test - took patch from http://codereview.appspot.com/4996044/ rather than the last comment. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1572 in lilypond: Change chord name separator and inversion separator, separately
Updates: Summary: Change chord name separator and inversion separator, separately Status: Started Comment #3 on issue 1572 by pkx1...@gmail.com: Change chord name separator and inversion separator, separately http://code.google.com/p/lilypond/issues/detail?id=1572 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display
Updates: Status: Started Comment #9 on issue 1503 by pkx1...@gmail.com: Feature request: simplify jazz chord display http://code.google.com/p/lilypond/issues/detail?id=1503 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1741 in lilypond: Tablature Bug when pitch is higher then beh in a quarter-tone string
Updates: Owner: d...@gnu.org Labels: -Patch-review Patch-push Comment #13 on issue 1741 by percival.music.ca: Tablature Bug when pitch is higher then beh in a quarter-tone string http://code.google.com/p/lilypond/issues/detail?id=1741 this is simple enough that we can go straight to push. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 380 in lilypond: cycling markup reference segfaults
Updates: Labels: -Patch-new Patch-review Comment #17 on issue 380 by pkx1...@gmail.com: cycling markup reference segfaults http://code.google.com/p/lilypond/issues/detail?id=380 Passes make and reg tests :) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1193 in lilypond: Enhancement: internal ledger lines
Updates: Summary: Enhancement: internal ledger lines Owner: --- Labels: -Patch-abandoned -Priority-Medium Patch-review Comment #12 on issue 1193 by pkx1...@gmail.com: Enhancement: internal ledger lines http://code.google.com/p/lilypond/issues/detail?id=1193 According to this http://codereview.appspot.com/4974075/ this addresses this. This passes make and reg tests ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1878 in lilypond: Add support for custom ledger positions, using two new staff-symbol properties
Updates: Labels: -Patch-new Patch-review Comment #1 on issue 1878 by pkx1...@gmail.com: Add support for custom ledger positions, using two new staff-symbol properties http://code.google.com/p/lilypond/issues/detail?id=1878 passes make and reg tests ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 380 in lilypond: cycling markup reference segfaults
Updates: Labels: -Patch-needs_work Patch-new Comment #16 on issue 380 by reinhold...@gmail.com: cycling markup reference segfaults http://code.google.com/p/lilypond/issues/detail?id=380 Oops, last-second changes before uploading are never a good idea :( Patch corrected. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1292 in lilypond: Enhancement: twelve-notation support
Updates: Labels: -Patch-new Patch-review Comment #4 on issue 1292 by pkx1...@gmail.com: Enhancement: twelve-notation support http://code.google.com/p/lilypond/issues/detail?id=1292 Passes make and reg tests ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1741 in lilypond: Tablature Bug when pitch is higher then beh in a quarter-tone string
Updates: Labels: -Patch-new Patch-review Comment #12 on issue 1741 by pkx1...@gmail.com: Tablature Bug when pitch is higher then beh in a quarter-tone string http://code.google.com/p/lilypond/issues/detail?id=1741 The patch file attached passes make and reg test. (See comment 10) There is no Rietveld for this though. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation
Comment #2 on issue 1873 by lemzw...@googlemail.com: Added glyphs for Kievan Notation http://code.google.com/p/lilypond/issues/detail?id=1873 There is a misunderstanding: The current MF code works just fine (as far as I can see), and as a quick solution to have Kievan glyphs in LilyPond it is OK. Note that all font editors work the way Aleksandr has implemented the glyphs. However, as a long-term solution, there are possibilities for improvements. In particular, contrary to other Emmentaler glyphs, the design size isn't taken into account. I don't object at all to a review. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1876 in lilypond: MusicXML: fix case when some elements have a staff number, while others don't
Updates: Labels: -Patch-new Patch-review Comment #1 on issue 1876 by pkx1...@gmail.com: MusicXML: fix case when some elements have a staff number, while others don't http://code.google.com/p/lilypond/issues/detail?id=1876 passes make and reg tests ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1877 in lilypond: parser.yy et al: Turn \transpose into a music function, make other music functions use ly:pitch?
Updates: Labels: -Patch-new Patch-review Comment #1 on issue 1877 by pkx1...@gmail.com: parser.yy et al: Turn \transpose into a music function, make other music functions use ly:pitch? http://code.google.com/p/lilypond/issues/detail?id=1877 passes make and reg tests ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 380 in lilypond: cycling markup reference segfaults
Updates:
Labels: -Patch-new Patch-needs_work
Comment #15 on issue 380 by pkx1...@gmail.com: cycling markup reference
segfaults
http://code.google.com/p/lilypond/issues/detail?id=380
Passes make but fails reg test check:
Failed files: (f2/lily-1e1652fb.ly)
fatal error: Children (4) exited with errors.
command failed: /home/jlowe/lilypond-git/build/out/bin/lilypond -I
/home/jlowe/lilypond-git/input/regression/ -I ./out-test -I
/home/jlowe/lilypond-git/input -I /home/jlowe/lilypond-git/Documentation -I
/home/jlowe/lilypond-git/Documentation/snippets -I
/home/jlowe/lilypond-git/input/regression/ -I
/home/jlowe/lilypond-git/Documentation/included/ -I
/home/jlowe/lilypond-git/build/mf/out/ -I
/home/jlowe/lilypond-git/build/mf/out/ -I
/home/jlowe/lilypond-git/Documentation/pictures -I
/home/jlowe/lilypond-git/build/Documentation/pictures/./out-test
-dbackend=eps --formats=ps -djob-count=7 -dseparate-log-files
-dinclude-eps-fonts -dgs-load-lily-fonts --header=texidoc -I
/home/jlowe/lilypond-git/Documentation/included/ -ddump-profile
-dcheck-internal-types -ddump-signatures -danti-alias-factor=1
-I "/home/jlowe/lilypond-git/build/out/lybook-testdb"
-I "/home/jlowe/lilypond-git/build/input/regression"
-I "/home/jlowe/lilypond-git/input/regression"
-I "/home/jlowe/lilypond-git/build/input/regression/out-test"
-I "/home/jlowe/lilypond-git/input"
-I "/home/jlowe/lilypond-git/Documentation"
-I "/home/jlowe/lilypond-git/Documentation/snippets"
-I "/home/jlowe/lilypond-git/input/regression"
-I "/home/jlowe/lilypond-git/Documentation/included"
-I "/home/jlowe/lilypond-git/build/mf/out"
-I "/home/jlowe/lilypond-git/build/mf/out"
-I "/home/jlowe/lilypond-git/Documentation/pictures"
-I "/home/jlowe/lilypond-git/build/Documentation/pictures/out-test"
--formats=eps -deps-box-padding=3.00 -dread-file-list
-dno-strip-output-dir "/home/jlowe/lilypond-git/build/out/lybook-testdb/snippet-names-1064022268.ly"
Child returned 1
make[2]: *** [out-test/collated-files.texi] Error 1
rm out-test/weblinks.itexi
make[2]: Leaving directory `/home/jlowe/lilypond-git/build/input/regression'
make[1]: *** [local-test] Error 2
make[1]: Leaving directory `/home/jlowe/lilypond-git/build/input/regression'
make: *** [test] Error 2
jlowe@jlowe-lilybuntu2:~/lilypond-git/build$ ^C
jlowe@jlowe-lilybuntu2:~/lilypond-git/build$
Fails on this file:
--snip--
\sourcefilename
"/home/jlowe/lilypond-git/input/regression/header-cyclic-reference.ly"
\sourcefileline 0
\version "2.15.11"
#(ly:set-option 'warning-as-error #f)
\header {
texidoc = "Cyclic references in header fields should cause a warning, but
not crash LilyPond with an endless loop"
title = \markup {Cyclic reference to \fromproperty #'header:title}
}
\score {
{ c' d' e' f' }
}
--snip--
James
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 456 in lilypond: \laissezVibrer in chords
Updates: Labels: -Patch-new Patch-review Comment #4 on issue 456 by pkx1...@gmail.com: \laissezVibrer in chords http://code.google.com/p/lilypond/issues/detail?id=456 Passes make and reg tests ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1873 in lilypond: Added glyphs for Kievan Notation
Updates: Labels: -Patch-new Patch-needs_work Comment #1 on issue 1873 by pkx1...@gmail.com: Added glyphs for Kievan Notation http://code.google.com/p/lilypond/issues/detail?id=1873 Based on Werner's last comment I think this isn't quite ready for a proper review yet. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1248 in lilypond: GUB produces a random "unbound open-file" in regtests
Updates: Status: Fixed Labels: fixed_2_15_11 Comment #11 on issue 1248 by reinhold...@gmail.com: GUB produces a random "unbound open-file" in regtests http://code.google.com/p/lilypond/issues/detail?id=1248 Pushed as d6bfed981f663c440475b56995c7f965af16589d ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1691 in lilypond: Ugly bars in PDF documents
Comment #43 on issue 1691 by philehol...@googlemail.com: Ugly bars in PDF documents http://code.google.com/p/lilypond/issues/detail?id=1691 I would expect the changes you made to -book will have fixed almost all of these, although I've not checked. As you say, there are a few left-over, which I hope to look at in the not-too-distant future. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
