Re: Segfault 2.13.47

This says 2.13.48. Paul Scott On 01/29/2011 09:45 PM, Jay Anderson wrote: Below is the gdb trace from the segfault: GNU gdb (GDB) 7.2-ubuntu Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: y

Segfault 2.13.47

Below is the gdb trace from the segfault: GNU gdb (GDB) 7.2-ubuntu Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent

Re: Issue 1035 in lilypond: Negative frets in fret diagrams

Updates: Labels: Patch-review Comment #2 on issue 1035 by carl.d.s...@gmail.com: Negative frets in fret diagrams http://code.google.com/p/lilypond/issues/detail?id=1035 (No comment was entered for this change.) ___ bug-lilypond mailing lis

accidental collides with articulation

Collisions of this type have become more common since 2.12.3 { c'8( g'8-> beses) } evil.12.png Description: Binary data evil.13.png Description: Binary data ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug

spacing overrides break melismata

If anyone changes the vertical spacing of lyrics using the method below, the problem reported in issue 1120 comes back. Patch at http://codereview.appspot.com/4095041/ << \context Voice = "v" { c' c' c' c' c'1 } \new Lyrics \with { \override VerticalAxisGroup #'nonstaff-relatedstaff

Issue 1497 in lilypond: Staff notation should be able to represent the notes of the predefined fret diagram.

Status: Accepted Owner: Labels: Type-Enhancement Priority-Low New issue 1497 by carl.d.s...@gmail.com: Staff notation should be able to represent the notes of the predefined fret diagram. http://code.google.com/p/lilypond/issues/detail?id=1497 Predefined fret diagrams for guitar often us

Re: Issue 1472 in lilypond: Collision between MMR and key signature

Comment #26 on issue 1472 by k-ohara5...@oco.net: Collision between MMR and key signature http://code.google.com/p/lilypond/issues/detail?id=1472 I updated the patch at http://codereview.appspot.com/4095041/, but that really addresses problems with the issue 1120 fix, not this issue. I'll

Re: Issue 1496 in lilypond: Update Pango to 1.28.3

Comment #7 on issue 1496 by percival.music.ca: Update Pango to 1.28.3 http://code.google.com/p/lilypond/issues/detail?id=1496 ok. I'll let you and Jan sort this out. Whenever you want me to test GUB master, I'm happy to do that. Otherwise, I'll focus on the lilypond patch backlog. I'm no

Re: Issue 1496 in lilypond: Update Pango to 1.28.3

Comment #6 on issue 1496 by pnorcks: Update Pango to 1.28.3 http://code.google.com/p/lilypond/issues/detail?id=1496 The "build fix" patch is completely unrelated to the Pango bump patch, so they indeed should be tested separately. To prioritize, I would rank the Pango issue above my build f

Re: Issue 1496 in lilypond: Update Pango to 1.28.3

Comment #4 on issue 1496 by percival.music.ca: Update Pango to 1.28.3 http://code.google.com/p/lilypond/issues/detail?id=1496 ok, I can now confirm that mingw::pango can build; I'm now continuing a general lilypond build. For the record, my GUB git head is: e234bcda96452a3ec38cf83e96907f1a

Re: Issue 1496 in lilypond: Update Pango to 1.28.3

Comment #3 on issue 1496 by percival.music.ca: Update Pango to 1.28.3 http://code.google.com/p/lilypond/issues/detail?id=1496 ok, g_int64_hash was introduced in glib-2.22. I'll try that other patch I saw from you. In general, I think it would be good to get the dependency-bumping patches

Re: Issue 1496 in lilypond: Update Pango to 1.28.3

Updates: Labels: Patch-new Comment #5 on issue 1496 by percival.music.ca: Update Pango to 1.28.3 http://code.google.com/p/lilypond/issues/detail?id=1496 ... and now darwin-x86::glib fails. I believe the answer is here: http://www.openldap.org/faq/data/cache/1191.html but I need to go

Re: Issue 1496 in lilypond: Update Pango to 1.28.3

Comment #2 on issue 1496 by percival.music.ca: Update Pango to 1.28.3 http://code.google.com/p/lilypond/issues/detail?id=1496 Does this mean anything to you off the top of your head? /main/src/gub/target/mingw/src/pango-1.28.3/modules/basic/basic-win32.c: In function 'itemize_shape_and_place'

Re: Issue 814 in lilypond: warning-as-error should be enabled when compiling the regtests

Updates: Labels: Patch-new Comment #2 on issue 814 by percival.music.ca: warning-as-error should be enabled when compiling the regtests http://code.google.com/p/lilypond/issues/detail?id=814 (No comment was entered for this change.) ___ bu

Re: Issue 816 in lilypond: Accidentals should use the normal fontsize in figured bass

Updates: Labels: Patch-abandoned Comment #2 on issue 816 by percival.music.ca: Accidentals should use the normal fontsize in figured bass http://code.google.com/p/lilypond/issues/detail?id=816 scm/translate-functions.scm does not contain this patch. I have a vague recollection of s

Re: Issue 839 in lilypond: Enhancement: improving midi2ly conversion

Updates: Labels: -abandoned_patch Patch-abandoned Comment #9 on issue 839 by percival.music.ca: Enhancement: improving midi2ly conversion http://code.google.com/p/lilypond/issues/detail?id=839 (No comment was entered for this change.) ___

Re: Issue 908 in lilypond: ImageMagick `compare' commands need some investigating

Updates: Labels: fixed_2_13_45 Comment #10 on issue 908 by percival.music.ca: ImageMagick `compare' commands need some investigating http://code.google.com/p/lilypond/issues/detail?id=908 I pushed this in 49dc60e9593bb088f436be8b49e2417aba6c123c

Re: Issue 971 in lilypond: SVG backend: problem with memory usage and multi-page SVG output

Updates: Labels: Patch-abandoned Comment #2 on issue 971 by percival.music.ca: SVG backend: problem with memory usage and multi-page SVG output http://code.google.com/p/lilypond/issues/detail?id=971 (No comment was entered for this change.) __

Re: Issue 1073 in lilypond: convert-ly and accented characters

Updates: Labels: -abandoned_patch Patch-abandoned Comment #5 on issue 1073 by percival.music.ca: convert-ly and accented characters http://code.google.com/p/lilypond/issues/detail?id=1073 (No comment was entered for this change.) ___ bug-l

Re: Issue 1229 in lilypond: Notes on ledger lines with stems pointed away from the staff overlap clef and staff ends in tight layouts

Updates: Labels: Patch-new Comment #8 on issue 1229 by percival.music.ca: Notes on ledger lines with stems pointed away from the staff overlap clef and staff ends in tight layouts http://code.google.com/p/lilypond/issues/detail?id=1229 (No comment was entered for this change.) ___

Re: Issue 1228 in lilypond: \override RestCollision #'positioning-done = #merge-rests-on-positioning

Updates: Labels: Patch-abandoned Comment #9 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.)

Re: Issue 1193 in lilypond: [PATCH] Enhancement: internal ledger lines

Updates: Labels: -Abandoned_patch Patch-abandoned Comment #9 on issue 1193 by percival.music.ca: [PATCH] Enhancement: internal ledger lines http://code.google.com/p/lilypond/issues/detail?id=1193 (No comment was entered for this change.) _

Re: Issue 1234 in lilypond: Fill-line should not use word space, but should use springs-and-rods

Updates: Labels: fixed_2_13_31 Comment #2 on issue 1234 by percival.music.ca: Fill-line should not use word space, but should use springs-and-rods http://code.google.com/p/lilypond/issues/detail?id=1234 This was pushed in d3d40f3469eda2cb327bebbd392c1ce88b114394 ___

Re: Issue 1470 in lilypond: Change keep-inside-line defaults to true

Updates: Labels: Patch-new Comment #8 on issue 1470 by percival.music.ca: Change keep-inside-line defaults to true http://code.google.com/p/lilypond/issues/detail?id=1470 (No comment was entered for this change.) ___ bug-lilypond mailing l

Re: Issue 1481 in lilypond: key cancellations at key changes are not complete when using extraNatural = ##f

Updates: Labels: Patch-new Comment #2 on issue 1481 by percival.music.ca: key cancellations at key changes are not complete when using extraNatural = ##f http://code.google.com/p/lilypond/issues/detail?id=1481 (No comment was entered for this change.) ___

Re: incorrect displaying of Arabic text

>> I tried this on 2.12.3-1 (MacOS 10.6) and 2.13.47 (MacOS 10.6). I >> see the same problem in both versions. > > The 2.14 release is coming soon (hopefully), and the current 2.13 > releases have beta status (more or less). Please use 2.13.47 and try > again whether you still experience problems

Re: incorrect displaying of Arabic text

>> Which version of LilyPond are you using? The 2.13 series has many, >> many improvements in font/text handling that may not have been >> backported to 2.12. > > I tried this on 2.12.3-1 (MacOS 10.6) and 2.13.47 (MacOS 10.6). I > see the same problem in both versions. The 2.14 release is comin

Re: incorrect displaying of Arabic text

> Which version of LilyPond are you using? The 2.13 series has many, > many improvements in font/text handling that may not have been > backported to 2.12. I tried this on 2.12.3-1 (MacOS 10.6) and 2.13.47 (MacOS 10.6). I see the same problem in both versions. -Samir __

Re: incorrect displaying of Arabic text

> The first thing to do is to run the specified command from a terminal > window: > > lilypond -dshow-available-fonts x > > You said before that "it didn't work". We don't know what that means, so we > can't help you. This is what it means: Zamzam:bin samir$ ./lilypond -dshow-available-fonts x

Re: Issue 1454 in lilypond: lilybuntu 3

Updates: Status: Fixed Labels: fixed_2_13_48 Comment #27 on issue 1454 by percival.music.ca: lilybuntu 3 http://code.google.com/p/lilypond/issues/detail?id=1454 Thanks, checked in virtualbox and updated in CG. ___ bug-lilypond mailing

Re: Issue 37 in lilypond: collision notehead and beams

Updates: Labels: -Patch-needs_work Patch-review Comment #13 on issue 37 by percival.music.ca: collision notehead and beams http://code.google.com/p/lilypond/issues/detail?id=37 LGTM. I won't bother changing the tag on issue 400, since it's the same patch as this one so reviewers don't

Re: Issue 1268 in lilypond: [PATCH] span-bar problem

Updates: Labels: -Patch-needs_work Patch-review Comment #18 on issue 1268 by percival.music.ca: [PATCH] span-bar problem http://code.google.com/p/lilypond/issues/detail?id=1268 New patch looks good. ___ bug-lilypond mailing list bug-lilypond@

Re: Status of break-align-symbol vs. break-align-symbols

Neil Puttock wrote quite some time ago http://lists.gnu.org/archive/html/bug-lilypond/2009-09/msg00039.html Thanks, I'll sort this out. I have just noticed that LSR 377 is still suffering from the convert problem (re issue 97) described in http://lists.gnu.org/archive/html/lilypond-devel/200

Re: > I'm not top posting. colour setting problem with connected arpeggio? v 2.12.2

Esa Erola wrote: > >> I'm not top posting. > > Hi, > > I would like to ask about an issue, maybe not a big one, but I got stuck > to this > for some reason. > > My use case: I would like to use connected arpeggio bracket in one meaning > with > a color and unconnected arpeggio in default colo

> I'm not top posting. colour setting problem with connected arpeggio? v 2.12.2

> I'm not top posting. Hi, I would like to ask about an issue, maybe not a big one, but I got stuck to this for some reason. My use case: I would like to use connected arpeggio bracket in one meaning with a color and unconnected arpeggio in default color and format. Running the script below set