Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display

2011-07-28 Thread Janek Warchoł
Hi Adam, 2011/7/28 Graham Percival : > On Thu, Jul 28, 2011 at 08:41:31AM +, lilyp...@googlecode.com wrote: >> >> Patches are available here, although some are still a work in progress: >> >> https://github.com/aspiers/lilypond/commits/master > > Thanks for the programming work!  Janek will he

Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes

2011-07-28 Thread lilypond
Comment #17 on issue 1735 by lemniska...@gmail.com: modifying default behaviour of tremolo slashes http://code.google.com/p/lilypond/issues/detail?id=1735 New patch set uploaded. Graham, i've never used IRC, but this might be a very good idea! __

Issue 1787 in lilypond: Hide ends of barlines inside staff lines.

2011-07-28 Thread lilypond
Status: Started Owner: Labels: Type-Enhancement Priority-Low Patch-new New issue 1787 by lemniska...@gmail.com: Hide ends of barlines inside staff lines. http://code.google.com/p/lilypond/issues/detail?id=1787 Patch here http://codereview.appspot.com/4809057/ More discussion here http:

Re: Issue 652 in lilypond: create glyphs dynamically instead of PS code

2011-07-28 Thread lilypond
Comment #5 on issue 652 by lemniska...@gmail.com: create glyphs dynamically instead of PS code http://code.google.com/p/lilypond/issues/detail?id=652 Is this what we are discussing now in "Postscript printer errors with rounded barlines?" thread (http://lists.gnu.org/archive/html/lilypond

Re: some comments do not appear in the tracker page

2011-07-28 Thread Janek Warchoł
James, 2011/7/27 James Lowe : > Janek > > )On Behalf Of Janek Warchol: > )there is a problem with comments in the tracker.  At least 2 comments > )didn't make it to the "changing G clef" issue page: > )- Trevor's comment from July 26th, containing sentence "The G clef font > )was changed 18 months

Re: Issue 1785 in lilypond: Compressible space before the first note of a line ?

2011-07-28 Thread lilypond
Comment #6 on issue 1785 by k-ohara5...@oco.net: Compressible space before the first note of a line ? http://code.google.com/p/lilypond/issues/detail?id=1785 There are 'internal' properties (undocumented and probably not meant to be adjusted) that determine the compressibility independently

Re: Issue 1785 in lilypond: Compressible space before the first note of a line ?

2011-07-28 Thread Keith OHara
On Wed, 27 Jul 2011 23:12:04 -0700, wrote: Comment #4 on issue 1785 by lemniskata.bernoullego: Compressible space before the first note of a line ? http://code.google.com/p/lilypond/issues/detail?id=1785 Can we make it compressible, but less than now? It would be perfect if the compressibility

Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes

2011-07-28 Thread lilypond
Comment #16 on issue 1735 by percival.music.ca: modifying default behaviour of tremolo slashes http://code.google.com/p/lilypond/issues/detail?id=1735 there's also the lilypond IRC channel, if you want actual realtime chat. Address, and a web client (no need to install software!) is on the

Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes

2011-07-28 Thread lilypond
Comment #15 on issue 1735 by lemniska...@gmail.com: modifying default behaviour of tremolo slashes http://code.google.com/p/lilypond/issues/detail?id=1735 James: i've checked and it doesn't change anything with cross-staff and repeat tremolos. Xavier: i'll gladly help you with setting up

Re: Issue 1767 in lilypond: Feta font - change breve vertical lines

2011-07-28 Thread lilypond
Comment #14 on issue 1767 by bordage@gmail.com: Feta font - change breve vertical lines http://code.google.com/p/lilypond/issues/detail?id=1767 Looks Good To Me. (These collisions are really ugly :o\ Need to fix this quickly...) Bertrand ___

Re: Issue 1767 in lilypond: Feta font - change breve vertical lines

2011-07-28 Thread lilypond
Updates: Labels: -Patch-needs_work Patch-review Comment #13 on issue 1767 by lemniska...@gmail.com: Feta font - change breve vertical lines http://code.google.com/p/lilypond/issues/detail?id=1767 New version uploaded to Rietveld (http://codereview.appspot.com/4748044), i attach a pd

Re: Failing regtests because of footnotes.

2011-07-28 Thread David Kastrup
Graham Percival writes: > On Thu, Jul 28, 2011 at 07:40:07PM +0200, David Kastrup wrote: >> >> I am reasonably sure that this is not a result of my own work. >> >> [/usr/local/tmp/lilypond/out/share/lilypond/current/ly/paper-defaults-init.lyERROR: >> Unbound variable: numbered-footnotes > > Als

Re: Issue 1786 in lilypond: New engraver for braces

2011-07-28 Thread lilypond
Updates: Labels: -Patch-new Patch-needs_work Comment #1 on issue 1786 by pkx1...@gmail.com: New engraver for braces http://code.google.com/p/lilypond/issues/detail?id=1786 Make is ok, but reg test gives me a few warnings on some reg tests. --snip-- /home/jlowe/lilypond-git/input/regre

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

2011-07-28 Thread lilypond
Comment #9 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 I think this may be a good catch, Nicolas. I'll try substituting the (ly:format for (format #

Issue 1786 in lilypond: New engraver for braces

2011-07-28 Thread lilypond
Status: Accepted Owner: Labels: Type-Enhancement Patch-new Priority-Medium New issue 1786 by pkx1...@gmail.com: New engraver for braces http://code.google.com/p/lilypond/issues/detail?id=1786 http://codereview.appspot.com/4807053/ from Bertrand Bordage --snip-- Hi! This patchs allows to

Re: Issue 1567 in lilypond: Add documentation for footnotes

2011-07-28 Thread lilypond
Updates: Labels: -Patch-review Patch-needs_work Comment #8 on issue 1567 by pkx1...@gmail.com: Add documentation for footnotes http://code.google.com/p/lilypond/issues/detail?id=1567 note from Mike --snip-- I just pushed a patch for automatic footnotes. Everything you need to know

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

2011-07-28 Thread lilypond
Comment #8 on issue 1780 by nicolas@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, Isn't ly:format supposed to be used instead of format, when the format string is basic

Re: Failing regtests because of footnotes.

2011-07-28 Thread Graham Percival
On Thu, Jul 28, 2011 at 07:40:07PM +0200, David Kastrup wrote: > > I am reasonably sure that this is not a result of my own work. > > [/usr/local/tmp/lilypond/out/share/lilypond/current/ly/paper-defaults-init.lyERROR: > Unbound variable: numbered-footnotes Also, any new regtest introduced right

Failing regtests because of footnotes.

2011-07-28 Thread David Kastrup
I am reasonably sure that this is not a result of my own work. [/usr/local/tmp/lilypond/out/share/lilypond/current/ly/paper-defaults-init.lyERROR: Unbound variable: numbered-footnotes -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu

Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display

2011-07-28 Thread Graham Percival
On Thu, Jul 28, 2011 at 08:41:31AM +, lilyp...@googlecode.com wrote: > > Patches are available here, although some are still a work in progress: > > https://github.com/aspiers/lilypond/commits/master Thanks for the programming work! Janek will help you to upload patch(es) to Rietveld. Chee

Re: Issue 1765 in lilypond: Clean up regtest mozart-hrn-3

2011-07-28 Thread lilypond
Comment #3 on issue 1765 by percival.music.ca: Clean up regtest mozart-hrn-3 http://code.google.com/p/lilypond/issues/detail?id=1765 Regardless of the number of lines changed, please upload a patch to rietveld. I'd offer to push it directly, but there's no urgency, so we might as well send

Re: Wrong link on German Home Page

2011-07-28 Thread Francisco Vila
2011/7/28 Till Paala : > Am 27.07.11 12:09, schrieb Urs Liska: >> >> Am 26.07.2011 21:30, schrieb Till Paala: >>> >>> Hi, >>> >>> finally corrected in lilypond/translation, >> >> When will this be visible? When displaying the German version of. >> http://www.lilypond.org, I still get the wrong link

Re: Issue 1765 in lilypond: Clean up regtest mozart-hrn-3

2011-07-28 Thread lilypond
Comment #2 on issue 1765 by philehol...@googlemail.com: Clean up regtest mozart-hrn-3 http://code.google.com/p/lilypond/issues/detail?id=1765 I now have an updated version of this which (I believe) now uses correct layout conventions, updated syntax and _almost_ exactly matches the previo

Re: Wrong link on German Home Page

2011-07-28 Thread Till Paala
Am 27.07.11 12:09, schrieb Urs Liska: Am 26.07.2011 21:30, schrieb Till Paala: Hi, finally corrected in lilypond/translation, When will this be visible? When displaying the German version of. http://www.lilypond.org, I still get the wrong links (although the link text is now different for th

Re: Issue 1765 in lilypond: Clean up regtest mozart-hrn-3

2011-07-28 Thread lilypond
Updates: Status: Started Comment #1 on issue 1765 by philehol...@googlemail.com: Clean up regtest mozart-hrn-3 http://code.google.com/p/lilypond/issues/detail?id=1765 (No comment was entered for this change.) ___ bug-lilypond mailing list

Re: Issue 732 in lilypond: Alignment problems when vertically stacking horizontally centered stencils.

2011-07-28 Thread lilypond
Updates: Status: Fixed Labels: -Patch-review fixed_2_15_7 Comment #10 on issue 732 by reinhold...@gmail.com: Alignment problems when vertically stacking horizontally centered stencils. http://code.google.com/p/lilypond/issues/detail?id=732 Pushed as commit a43a9465fda1728a64fa

Re: Issue 1744 in lilypond: \once \set behavior should be documented

2011-07-28 Thread lilypond
Updates: Status: Fixed Labels: fixed_2_15_7 Comment #6 on issue 1744 by reinhold...@gmail.com: \once \set behavior should be documented http://code.google.com/p/lilypond/issues/detail?id=1744 Issue 153 was fixed with commit d1db9b1d6ebb1014429974f22162b44bf9a03533 So now ther

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

2011-07-28 Thread lilypond
Updates: Status: Fixed Labels: -Patch-needs_work fixed_2_15_7 Comment #18 on issue 153 by reinhold...@gmail.com: \once \set fails to restore previous setting http://code.google.com/p/lilypond/issues/detail?id=153 Pushed as commit d1db9b1d6ebb1014429974f22162b44bf9a03533

Re: Collision between figures and tie

2011-07-28 Thread Bertrand Bordage
> > Is this possibly related to > http://code.google.com/p/lilypond/issues/detail?id=1277 ? Probably. 'Tis difficult to say without some code browsing. Bertrand ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/b

Re: Issue 1111 in lilypond: Allow manual directions on dynamics to break alignment spanner automatically

2011-07-28 Thread lilypond
Updates: Status: Fixed Labels: -Patch-review fixed_2_15_7 Comment #5 on issue by reinhold...@gmail.com: Allow manual directions on dynamics to break alignment spanner automatically http://code.google.com/p/lilypond/issues/detail?id= Pushed as commit d959f8d548dc073c16

Re: Issue 1433 in lilypond: \breakDynamicSpan breaks with \break ("bounds of spanner are invalid")

2011-07-28 Thread lilypond
Updates: Status: Fixed Labels: -Patch-review fixed_2_15_7 Comment #8 on issue 1433 by reinhold...@gmail.com: \breakDynamicSpan breaks with \break ("bounds of spanner are invalid") http://code.google.com/p/lilypond/issues/detail?id=1433 Pushed as commit cf3642858a2340bb39ee5673

Re: Issue 1259 in lilypond: DynamicTextSpanner #'style = #'none doesn't work over \break

2011-07-28 Thread lilypond
Updates: Status: Fixed Labels: -Patch-review fixed_2_15_7 Comment #9 on issue 1259 by reinhold...@gmail.com: DynamicTextSpanner #'style = #'none doesn't work over \break http://code.google.com/p/lilypond/issues/detail?id=1259 Pushed as commit cf3642858a2340bb39ee56739f34c79994

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

2011-07-28 Thread lilypond
Comment #7 on issue 1780 by d...@gnu.org: Scheme format functions with no destination parameter cause deprecation warnings in Guile V2 http://code.google.com/p/lilypond/issues/detail?id=1780 testv2withpatch2.log looks like the Scheme interpreter is trying to interpret #print-all-headers wh

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

2011-07-28 Thread lilypond
Comment #6 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 By the way, David's patch successfully does a make and passes regression tests when running

Re: Slurs and PhrasingSlurs with simultaneous start or end

2011-07-28 Thread Dmytro O. Redchuk
On Thu 28 Jul 2011, 13:49 Nick Payne wrote: > The automatic positioning of Slurs and PhrasingSlurs that both > either start or finish on the same note is not very good. See below. > Commercial scores that I have where this happens position the two > slurs so that they don't intersect or touch, as i

Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display

2011-07-28 Thread lilypond
Comment #7 on issue 1503 by adam.spi...@gmail.com: Feature request: simplify jazz chord display http://code.google.com/p/lilypond/issues/detail?id=1503 Patches are available here, although some are still a work in progress: https://github.com/aspiers/lilypond/commits/master ___

Re: Issue 1663 in lilypond: Images missing on web site

2011-07-28 Thread lilypond
Comment #13 on issue 1663 by philehol...@googlemail.com: Images missing on web site http://code.google.com/p/lilypond/issues/detail?id=1663 FWIW, it's not just a problem with web. It seems that any web page where there are included pictures (not included images of lily-produced music) ha

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

2011-07-28 Thread lilypond
Comment #5 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 Attached are two logs with the patch applied. The Guile signal for for the (format #f ...)

Re: Issue 1572 in lilypond: Enhancement req: Change chord name separator and inversion separator, separately

2011-07-28 Thread lilypond
Comment #2 on issue 1572 by adam.spi...@gmail.com: Enhancement req: Change chord name separator and inversion separator, separately http://code.google.com/p/lilypond/issues/detail?id=1572 I have incorporated this patch into the master branch of my git repository (which will be available at

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

2011-07-28 Thread lilypond
Updates: Cc: d...@gnu.org Comment #4 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 On a system with Guile V2, the call from titling-init.ly bef

Re: Issue 1572 in lilypond: Enhancement req: Change chord name separator and inversion separator, separately

2011-07-28 Thread lilypond
Comment #1 on issue 1572 by adam.spi...@gmail.com: Enhancement req: Change chord name separator and inversion separator, separately http://code.google.com/p/lilypond/issues/detail?id=1572 See also issue 1503. ___ bug-lilypond mailing list bug-lily

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

2011-07-28 Thread lilypond
Comment #22 on issue 163 by mts...@gmail.com: huge (ugly) slur (both phrasing and normal) http://code.google.com/p/lilypond/issues/detail?id=163 The difference in the height of generated curves is relatively drastic when you remove the accidental. I'm not sure if this is a good or bad thing

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

2011-07-28 Thread lilypond
Comment #21 on issue 163 by mts...@gmail.com: huge (ugly) slur (both phrasing and normal) http://code.google.com/p/lilypond/issues/detail?id=163 I changed my patch (no need to run regtests) that diminishes the changes in the regtests and still solves all the problem cases (http://coderevi