Re: Doc: NR 2.1.2 Lyrics and repeats, improvement proposals

On Tue 14 Dec 2010, 12:04 I wrote: On Thu 11 Nov 2010, 12:04 Xavier Scheuer wrote: Hi! Hi, Xavier! I know that NR 2.1 have been recently (is currently being?) improved. I looked only at the latest _online_ (i.e. not git) version (2.13.39 at kainhofer.com), so please excuse me if what

Re: Issue 1366 in lilypond: [Patch] Tablature: proper support for tie/slur- and tie/glissando-constellations

Updates: Status: Verified Labels: fixed_2_13_42 Comment #1 on issue 1366 by v.villenave: [Patch] Tablature: proper support for tie/slur- and tie/glissando-constellations http://code.google.com/p/lilypond/issues/detail?id=1366 Merged.

Re: Issue 1339 in lilypond: [PATCH]Tablature: proper support for tie/slur- and tie/glissando-constellations (issue2191042)

Updates: Status: Verified Labels: fixed_2_13_42 Comment #2 on issue 1339 by v.villenave: [PATCH]Tablature: proper support for tie/slur- and tie/glissando-constellations (issue2191042) http://code.google.com/p/lilypond/issues/detail?id=1339 Merged.

Re: Issue 1386 in lilypond: Tied harmonics in TabStaff

Updates: Status: Fixed Labels: fixed_2_13_42 Comment #1 on issue 1386 by v.villenave: Tied harmonics in TabStaff http://code.google.com/p/lilypond/issues/detail?id=1386 Merged. ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: bug in rest-placement in polyphonic music

ander...@notam02.no wrote in message news:87eiam1vkq@notam02.no... D == Dmytro O Redchuk brownian@gmail.com writes: D Actually, i can understand why this output is _wanted_, but can D not imagine good Summary for issue report. D Rest in lower voice should be placed above notes

Re: feature request: brackets should match size of the object theyenclose

Janek Warchoł lemniskata.bernoull...@gmail.com wrote in message news:aanlktik6jejyyemedv9zevfehs1nhz6ucupjguuwv...@mail.gmail.com... % I was very happy to find out that \parenthesize works not only with notes, but very unhappy to find out that the brackets seem to have constant size. For

Re: Issue 1437 in lilypond: [PATCH] Doc: Remove fragment option from @lilypond LM

Updates: Status: Fixed Labels: fixed_2_13_43 Comment #1 on issue 1437 by percival.music.ca: [PATCH] Doc: Remove fragment option from @lilypond LM http://code.google.com/p/lilypond/issues/detail?id=1437 This was pushed a while ago.

Re: Collision with slur in 13.40 regtests?

On Tue, Dec 14, 2010 at 3:52 PM, Phil Holmes m...@philholmes.net wrote: Phil Holmes m...@philholmes.net wrote in message news:id2jug$48...@dough.gmane.org... Please see the attached output from the 13.40 regtests.  There's a collision between the slur in the top staff and the figured bass

Issue 1450 in lilypond: Collision between slur and text in les-nereides regtest

Status: Accepted Owner: Labels: Type-Collision Priority-Low New issue 1450 by PhilEHolmes: Collision between slur and text in les-nereides regtest http://code.google.com/p/lilypond/issues/detail?id=1450 In the regtest les-nereides.ly, the slur on the first line collides with text on

Re: Collision with slur in 13.40 regtests?

Graham Percival gra...@percival-music.ca wrote in message news:aanlkti=yz=e4g8t0-sewrtxzyqgejmn3hbepeswsl...@mail.gmail.com... On Tue, Dec 14, 2010 at 3:52 PM, Phil Holmes m...@philholmes.net wrote: Phil Holmes m...@philholmes.net wrote in message news:id2jug$48...@dough.gmane.org... Please

Re: Issue 1028 in lilypond: Test failure when built without a controlling tty

Updates: Status: Verified Comment #7 on issue 1028 by PhilEHolmes: Test failure when built without a controlling tty http://code.google.com/p/lilypond/issues/detail?id=1028 Since we do have a build .37, we must assume that this is OK. ___

Re: Issue 1437 in lilypond: [PATCH] Doc: Remove fragment option from @lilypond LM

Updates: Status: Verified Comment #2 on issue 1437 by PhilEHolmes: [PATCH] Doc: Remove fragment option from @lilypond LM http://code.google.com/p/lilypond/issues/detail?id=1437 (No comment was entered for this change.) ___ bug-lilypond

Re: Issue 810 in lilypond: Improving tablatures support (rhythm notation, etc.)

Updates: Labels: -fixed_2_13_3 fixed_2_13_41 Comment #3 on issue 810 by pnorcks: Improving tablatures support (rhythm notation, etc.) http://code.google.com/p/lilypond/issues/detail?id=810 This appears to have landed in 2.13.41. ___

Re: Issue 810 in lilypond: Improving tablatures support (rhythm notation, etc.)

Updates: Labels: -fixed_2_13_41 fixed_2_13_3 Comment #4 on issue 810 by pnorcks: Improving tablatures support (rhythm notation, etc.) http://code.google.com/p/lilypond/issues/detail?id=810 Oops, sorry for the confusion... ___ bug-lilypond

Issue 1451 in lilypond: \parenthesize should enclose entire objects

Status: Accepted Owner: Labels: Type-Enhancement Priority-Medium New issue 1451 by pnorcks: \parenthesize should enclose entire objects http://code.google.com/p/lilypond/issues/detail?id=1451 Original report: http://lists.gnu.org/archive/html/bug-lilypond/2010-10/msg00386.html Parenthesis

Re: feature request: brackets should match size of the object theyenclose

On Tue, Dec 14, 2010 at 8:04 AM, Phil Holmes m...@philholmes.net wrote: Janek Warchoł lemniskata.bernoull...@gmail.com wrote in message news:aanlktik6jejyyemedv9zevfehs1nhz6ucupjguuwv...@mail.gmail.com... % I was very happy to find out that \parenthesize works not only with notes, but very

Re: Issue 1451 in lilypond: \parenthesize should enclose entire objects

Comment #1 on issue 1451 by pnorcks: \parenthesize should enclose entire objects http://code.google.com/p/lilypond/issues/detail?id=1451 (No comment was entered for this change.) Attachments: parenthesize.preview.png 669 bytes ___

Re: Issue 1451 in lilypond: \parenthesize should enclose entire objects

Comment #2 on issue 1451 by pnorcks: \parenthesize should enclose entire objects http://code.google.com/p/lilypond/issues/detail?id=1451 See also issue 155 and issue 868. ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: Issue 1410 in lilypond: Rest in lower voice should be placed above notes in in upper if voices are crossed.

Updates: Labels: Priority-Medium Comment #1 on issue 1410 by PhilEHolmes: Rest in lower voice should be placed above notes in in upper if voices are crossed. http://code.google.com/p/lilypond/issues/detail?id=1410 (No comment was entered for this change.) Attachments:

Re: Issue 1431 in lilypond: Enhancement - add spiccato articulation symbol

Updates: Labels: Priority-Medium Comment #1 on issue 1431 by PhilEHolmes: Enhancement - add spiccato articulation symbol http://code.google.com/p/lilypond/issues/detail?id=1431 (No comment was entered for this change.) ___ bug-lilypond

Re: Issue 1442 in lilypond: staff-staff padding all appears after the last nonstaff

Updates: Labels: Priority-High Comment #2 on issue 1442 by PhilEHolmes: staff-staff padding all appears after the last nonstaff http://code.google.com/p/lilypond/issues/detail?id=1442 (No comment was entered for this change.) ___

Re: Issue 1443 in lilypond: bookTitleMarkup to fill exactly one page (with stretching!) and contain page breaks

Updates: Labels: Priority-Medium Comment #1 on issue 1443 by PhilEHolmes: bookTitleMarkup to fill exactly one page (with stretching!) and contain page breaks http://code.google.com/p/lilypond/issues/detail?id=1443 (No comment was entered for this change.) Attachments:

Re: Issue 1452 in lilypond: asldjf

Comment #1 on issue 1452 by palmer.r.violin: asldjf http://code.google.com/p/lilypond/issues/detail?id=1452 Hmm. I was trying to start the entry process for a non-existent issue, so that I could see what the choices for categories are. I did not intend to actually submit this issue.

Re: Issue 1440 in lilypond: \book(part) containing page-marker as only element segfaults

Updates: Status: Verified Comment #6 on issue 1440 by Carl.D.Sorensen: \book(part) containing page-marker as only element segfaults http://code.google.com/p/lilypond/issues/detail?id=1440 Verified, and a regtest has been pushed (although it didn't make it in the 2.13.43 release).

Re: Issue 1336 in lilypond: skipTypesetting segfaults when set during a skipBars-induced MultiMeasureRest spanner

Updates: Status: Verified Comment #34 on issue 1336 by Carl.D.Sorensen: skipTypesetting segfaults when set during a skipBars-induced MultiMeasureRest spanner http://code.google.com/p/lilypond/issues/detail?id=1336 Verified, and regression tests pushed. Regtests are not part of .43,

Re: Issue 1363 in lilypond: Language links in manual pages should be right from start and kept intact by web_post.py

Updates: Status: Verified Comment #8 on issue 1363 by Carl.D.Sorensen: Language links in manual pages should be right from start and kept intact by web_post.py http://code.google.com/p/lilypond/issues/detail?id=1363 Verified for the reported links. Thanks, Carl

Re: Issue 1386 in lilypond: Tied harmonics in TabStaff

Comment #4 on issue 1386 by Carl.D.Sorensen: Tied harmonics in TabStaff http://code.google.com/p/lilypond/issues/detail?id=1386 A regression test input/regression/tablature-harmonic-tie.ly has been pushed. The regtest is part of .44, but the fix is part of .42 Someone other than me should

Re: Issue 1407 in lilypond: Glyphs with an extra Y-offset are not positioned correctly

Comment #5 on issue 1407 by percival.music.ca: Glyphs with an extra Y-offset are not positioned correctly http://code.google.com/p/lilypond/issues/detail?id=1407 If right now you mean in the next 2-6 weeks until 2.14 is released, then yes. If you'd mentioned it earlier (or later), then

Re: Issue 1407 in lilypond: Glyphs with an extra Y-offset are not positioned correctly

Comment #7 on issue 1407 by pnorcks: Glyphs with an extra Y-offset are not positioned correctly http://code.google.com/p/lilypond/issues/detail?id=1407 Oh man, I wish this tracker warned about new comments being added at the same time by different users. :) Graham, it's not a problem.

Re: Issue 1407 in lilypond: Glyphs with an extra Y-offset are not positioned correctly

Updates: Status: Verified Comment #8 on issue 1407 by Carl.D.Sorensen: Glyphs with an extra Y-offset are not positioned correctly http://code.google.com/p/lilypond/issues/detail?id=1407 Verified. THanks, Patrick Attachments: Verify-1407.png 2.0 KB

Re: Issue 1249 in lilypond: Avoid compilation errors using Guile V2 during initialization - Part 1 ly-syntax-constructors.scm

Updates: Status: Verified Comment #5 on issue 1249 by pnorcks: Avoid compilation errors using Guile V2 during initialization - Part 1 ly-syntax-constructors.scm http://code.google.com/p/lilypond/issues/detail?id=1249 (No comment was entered for this change.)

Re: Issue 1265 in lilypond: Avoid compilation and run-time deprecation warnnings from Guile V2

Updates: Status: Verified Comment #7 on issue 1265 by pnorcks: Avoid compilation and run-time deprecation warnnings from Guile V2 http://code.google.com/p/lilypond/issues/detail?id=1265 (No comment was entered for this change.) ___

Re: Issue 1383 in lilypond: Make error when invoking `make maintainerclean'

Updates: Status: Verified Comment #2 on issue 1383 by Carl.D.Sorensen: Make error when invoking `make maintainerclean' http://code.google.com/p/lilypond/issues/detail?id=1383 (No comment was entered for this change.) ___ bug-lilypond

Re: bug in rest-placement in polyphonic music

On Wed 17 Nov 2010, 16:18 Ralph Palmer wrote: Greetings, Anders Vinjar - [...] Thank you for your email. This has been added as issue # 1410 : http://code.google.com/p/lilypond/issues/detail?id=1410 Pondly, Ralph On Tue 14 Dec 2010, 16:02 Phil Holmes wrote: Bump. Could a