Issue 1779 in lilypond: accidentaled notes too far from the barline

2011-07-25 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect Priority-Low Patch-new New issue 1779 by k-ohara5...@oco.net: accidentaled notes too far from the barline http://code.google.com/p/lilypond/issues/detail?id=1779 Note-columns should be spaced so their main column of note-heads is close to

New install problem

2011-07-25 Thread Brian Galliford
Dear Lilyponders, I've been using Lilypond with no problems (and many thanks) for a couple of years on my old MacBookPro 17inch. I have just tried installing it from a clean download from your site on my new MacBookPro 15inch. On starting up the program however I get the following error

Issue 1780 in lilypond: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2

2011-07-25 Thread lilypond
Status: Started Owner: ianhuli...@gmail.com CC: pnorcks Labels: Type-Enhancement Priority-Medium Maintainability New issue 1780 by ianhuli...@gmail.com: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2

Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond 2.14.x

2011-07-25 Thread lilypond
Status: New Owner: Labels: OpSys-OSX Type-Build Priority-High New issue 1781 by pkx1...@gmail.com: Mac OS X 10.7 (Lion) cannot run LilyPond 2.14.x http://code.google.com/p/lilypond/issues/detail?id=1781 Reported by 3 users so far: --snip-- On starting up the program however I get the

RE: New install problem

2011-07-25 Thread James Lowe
Hello, )-Original Message- )From: Floris van Manen [mailto:v...@klankschap.nl] )Sent: 25 July 2011 11:38 )To: James Lowe )Cc: bug-lilypond@gnu.org bug )Subject: Re: New install problem )Importance: Low ) ) )On Jul 25, 2011, at 12:03, James Lowe wrote: ) ) What version of Mac OS are you

Issue 1782 in lilypond: avoid-slur should have a setting `best' to avoid huge slurs with key signatures

2011-07-25 Thread lilypond
Status: Accepted Owner: mts...@gmail.com Labels: Type-Defect Priority-Medium New issue 1782 by mts...@gmail.com: avoid-slur should have a setting `best' to avoid huge slurs with key signatures http://code.google.com/p/lilypond/issues/detail?id=1782 \relative c''' { e f \acciaccatura { fis }

Re: New install problem

2011-07-25 Thread Trevor Bača
On Mon, Jul 25, 2011 at 7:03 AM, James Lowe james.l...@datacore.com wrote: Hello, )-Original Message- )From: Floris van Manen [mailto:v...@klankschap.nl] )Sent: 25 July 2011 11:38 )To: James Lowe )Cc: bug-lilypond@gnu.org bug )Subject: Re: New install problem )Importance: Low )

Re: New install problem

2011-07-25 Thread Floris van Manen
On Jul 25, 2011, at 17:12, Trevor Bača wrote: FWIW, running 2.5.15 *from the commandline* under Lion works great for me. not here... $ Downloads/LilyPond.app/Contents/MacOS/LilyPond Traceback (most recent call last): File

Re: New install problem

2011-07-25 Thread Trevor Bača
On Mon, Jul 25, 2011 at 11:20 AM, Floris van Manen v...@klankschap.nl wrote: On Jul 25, 2011, at 17:12, Trevor Bača wrote: FWIW, running 2.5.15 *from the commandline* under Lion works great for me. not here... $ Downloads/LilyPond.app/Contents/MacOS/LilyPond Ah: it's

Re: Issue 1673 in lilypond: patch Allows glissandi to span multiple lines.

2011-07-25 Thread lilypond
Updates: Status: Fixed Comment #8 on issue 1673 by k-ohara5...@oco.net: patch Allows glissandi to span multiple lines. http://code.google.com/p/lilypond/issues/detail?id=1673 should this issue (1673) also be marked fixed? This tracker item won't help anything anymore, so let's

Re: Issue 1779 in lilypond: accidentaled notes too far from the barline

2011-07-25 Thread lilypond
Updates: Labels: -Patch-new Patch-review Comment #1 on issue 1779 by pkx1...@gmail.com: accidentaled notes too far from the barline http://code.google.com/p/lilypond/issues/detail?id=1779 Passes make and there are lots (lots) of reg test differences but as keith says many 'small'

Re: Issue 621 in lilypond: Dynamics should avoid cross-staff BarLines (e.g. GrandStaff, PianoStaff etc)

2011-07-25 Thread lilypond
Updates: Owner: k-ohara5...@oco.net Cc: v.villen...@gmail.com Labels: -Patch-new Patch-review Comment #10 on issue 621 by pkx1...@gmail.com: Dynamics should avoid cross-staff BarLines (e.g. GrandStaff, PianoStaff etc)

Re: Issue 631 in lilypond: Dynamics collide with cross-staff barlines when attached to skips

2011-07-25 Thread lilypond
Updates: Owner: k-ohara5...@oco.net Labels: -Type-Defect -Collision Type-Collision Patch-review Comment #4 on issue 631 by pkx1...@gmail.com: Dynamics collide with cross-staff barlines when attached to skips http://code.google.com/p/lilypond/issues/detail?id=631 Passes Make

Re: Issue 1752 in lilypond: redesigning G clef in our Feta font

2011-07-25 Thread lilypond
Comment #27 on issue 1752 by k-ohara5...@oco.net: redesigning G clef in our Feta font http://code.google.com/p/lilypond/issues/detail?id=1752 How do you like it? I would never notice the difference between the old and new glyphs. Adding \override Staff.Clef #'style = xx complicates

Re: Issue 1752 in lilypond: redesigning G clef in our Feta font

2011-07-25 Thread lilypond
Comment #28 on issue 1752 by lemniska...@gmail.com: redesigning G clef in our Feta font http://code.google.com/p/lilypond/issues/detail?id=1752 2011/7/25 k-ohara5...@oco.net: I would never notice the difference between the old and new glyphs. :-) Adding \override Staff.Clef #'style =

Re: Issue 1752 in lilypond: redesigning G clef in our Feta font

2011-07-25 Thread Graham Percival
On Sun, Jul 24, 2011 at 11:43:02PM +, lilyp...@googlecode.com wrote: However, I am aghast that the font switching architecture is going nowhere. As far as I understand it, 1. we can switch to a different OTF font. (aka gonville) Everything that i see on this topic is here

Re: Issue 1752 in lilypond: redesigning G clef in our Feta font

2011-07-25 Thread Carl Sorensen
On 7/24/11 2:19 PM, lilyp...@googlecode.com lilyp...@googlecode.com wrote: Comment #25 on issue 1752 by percival.music.ca: redesigning G clef in our Feta font http://code.google.com/p/lilypond/issues/detail?id=1752 The critical regression thing was a complete brain fart from me and

Re: Issue 1752 in lilypond: redesigning G clef in our Feta font

2011-07-25 Thread Carl Sorensen
On 7/24/11 5:43 PM, lilyp...@googlecode.com lilyp...@googlecode.com wrote: Comment #26 on issue 1752 by lemniska...@gmail.com: redesigning G clef in our Feta font http://code.google.com/p/lilypond/issues/detail?id=1752 In order to address the difference of opinion, we have two

Re: Issue 1752 in lilypond: redesigning G clef in our Feta font

2011-07-25 Thread lilypond
Comment #29 on issue 1752 by k-ohara5...@oco.net: redesigning G clef in our Feta font http://code.google.com/p/lilypond/issues/detail?id=1752 Today, if I wanted to, I could \set Staff.clefGlyph = #clefs.petrucci.g However, i was unable to apply this override to a change clef - how it's

Re: Issue 153 in lilypond: \once \set fails to restore previous setting

2011-07-25 Thread lilypond
Updates: Labels: -Patch-review -CD-110725 Patch-needs_work Comment #16 on issue 153 by colinpkc...@gmail.com: \once \set fails to restore previous setting http://code.google.com/p/lilypond/issues/detail?id=153 Still under discussion. ___

Re: Issue 620 in lilypond: It should be possible to specify more specific spanner bounds.

2011-07-25 Thread lilypond
Updates: Labels: -Patch-review -CD-110725 Patch-needs_work Comment #7 on issue 620 by colinpkc...@gmail.com: It should be possible to specify more specific spanner bounds. http://code.google.com/p/lilypond/issues/detail?id=620 Still under discussion.

Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

2011-07-25 Thread lilypond
Updates: Labels: -Patch-review Patch-needs_work Comment #15 on issue 163 by colinpkc...@gmail.com: huge (ugly) slur (both phrasing and normal) http://code.google.com/p/lilypond/issues/detail?id=163 Mike feels this needs more work. ___