Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display
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 help you to upload > patch(es) to Rietveld. could you send me patch files directly? I've never used github and i must admit that i'm lost... Also, i'm not sure what should be uploaded. If you'd like, i can help you upload these patches yourself, it's not hard (the main problem is how to escape the vi-trap that other people set for us ;P). Are you using Lilydev? thanks for your work! Janek PS and thanks for pointing this to me, Graham. As you've noticed, i don't manage to read all Lily-mail... ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes
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! ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1787 in lilypond: Hide ends of barlines inside staff lines.
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://lists.gnu.org/archive/html/lilypond-devel/2011-07/msg00686.html Maybe this should be merged into issue 652. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 652 in lilypond: create glyphs dynamically instead of PS code
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-devel/2011-07/msg00686.html) or is it a slightly different issue? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: some comments do not appear in the tracker page
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 or so ago by Carl without all this fuss" > )- Carls comment, perhaps from July 25th, containing sentence "This > )proposal was based on Graham's assertion that 2.16 is 10 days away from > )release" > > Are these messages you are missing on the tracker itself (as opposed to > someone just replying to the email that the tracker generates)? Umm, i don't understand what you mean... When you go to http://code.google.com/p/lilypond/issues/detail?id=1752 , do you see any message sent by Trevor? For example "I agree. LilyPond has many glyphs. If we start using overrides to select glyphs with minor differences where might it end?" ? I don't see it there and it didn't appear in my e-mail account. The only place where i can see it is bug- archives: http://lists.gnu.org/archive/html/bug-lilypond/2011-07/msg00375.html ... oh well, i found it. I've disabled receiving e-mails from bug-lilypond, silly me. I remember now that i did this a long time ago as they seemed irrelevant to me, and i never noticed the difference... Ugh . Still, i think that it'd be better if every message related to a tracker issue appeared as a comment in the tracker. cheers, Janek ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1785 in lilypond: Compressible space before the first note of a line ?
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 depending on what is the last symbol before the notes. These properties are part of the 'space-alist's defined in define-grobs.scm and the entries can be fixed or semi-fixed. Since they are not documented you have to study staff-spacing.cc to see how they work. Also, the code has not changed much since 2002 so the way things are done might seem strange. I think we should move any discussion, about how the system works, over to lilypond-devel. I raised this bug only to warn people that I intend to restore the before-first-note space back to its former firmness. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1785 in lilypond: Compressible space before the first note of a line ?
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 would depend on what is the last symbol before notes: There are 'internal' properties (undocumented and probably not meant to be adjusted) that determine the compressibility independently depending on what is the last symbol before the notes. These properties are part of the 'space-alist's defined in define-grobs.scm and the entries can be fixed or semi-fixed. Since they are not documented you have to study staff-spacing.cc to see how they work. Also, the code has not changed much since 2002 so the way things are done might seem strange. I think we should move any discussion, about how the system works, over to lilypond-devel. I raised this bug only to warn people that I intend to restore the before-first-note space back to its former firmness. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes
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 lilypond website contacts page. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1735 in lilypond: modifying default behaviour of tremolo slashes
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 git! We can arrange an "e-mail chat" if you'd like to (i.e. we'll open mailboxes at the same time and send e-mail replies immediately, so that minor problems could be solved at once instead of waiting for hours for a hint on how to proceed). Concerning shape values - current default is not "rectangle", it's mixed (rectangle for 8ths and shorter notes, "default" for 4th and longer ones). However, changing name "default" to "parallellogram" seems like a good idea. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1767 in lilypond: Feta font - change breve vertical lines
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 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1767 in lilypond: Feta font - change breve vertical lines
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 pdf proof file. The gap in smallest font sizes was reduced according to Bertrand's suggestion, and the line height was increased just a bit according to my friend's suggestion. I don't feel strong about these changes; for me both this version and previous version is good enough (and definately better than current Lily). There are chords with seconds included, but they are broken independently of my patch. See "where X-extent of noteheads is set?" thread on devel. Attachments: new breve test.pdf 42.7 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Failing regtests because of footnotes.
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 > > Also, any new regtest introduced right now should be > \version "2.15.7" > (unless it also works in 2.15.0) > > and any convert-ly rule should be for (2, 15, 7) And the regtests also deliver things like Processing `./8a/lily-b3fc0367.ly' Parsing... Renaming input to: `footnote-auto-numbering.ly' Interpreting music... Preprocessing graphical objects... Interpreting music... Preprocessing graphical objects... Interpreting music... Preprocessing graphical objects... Finding the ideal number of pages... Fitting music on 1 or 2 pages... Drawing systems... programming error: Improbable offset for stencil: 34508321723124.855469 staff space Setting to zero. continuing, cross fingers programming error: Improbable offset for stencil: 34508321723124.855469 staff space Setting to zero. continuing, cross fingers programming error: Improbable offset for stencil: 34508321723124.855469 staff space Setting to zero. continuing, cross fingers programming error: Improbable offset for stencil: 34508321723124.855469 staff space Setting to zero. continuing, cross fingers programming error: Improbable offset for stencil: 40916551476714.671875 staff space Setting to zero. continuing, cross fingers programming error: Improbable offset for stencil: 40916551476714.671875 staff space Setting to zero. continuing, cross fingers programming error: Improbable offset for stencil: 40916551476714.671875 staff space Setting to zero. continuing, cross fingers programming error: Improbable offset for stencil: 40916551476714.671875 staff space Setting to zero. continuing, cross fingers Writing header field `texidoc' to `./8a/lily-b3fc0367.texidoc'... Layout output to `./8a/lily-b3fc0367.eps'... Layout output to `./8a/lily-b3fc0367-1.eps'... Layout output to `./8a/lily-b3fc0367-2.eps'... Writing ./8a/lily-b3fc0367-systems.texi... Writing ./8a/lily-b3fc0367-systems.tex... Writing ./8a/lily-b3fc0367-systems.count... Writing timing to 8a/lily-b3fc0367.profile... Does not look all too good. Different runs of the regtest yield different values: this reeks of uninitialized data. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1786 in lilypond: New engraver for braces
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/regression/footnote-auto-numbering.log @@ -9,28 +9,28 @@ Finding the ideal number of pages... Fitting music on 1 or 2 pages... Drawing systems... -programming error: Improbable offset for stencil: 823787934458423451582464.00 staff space +programming error: Improbable offset for stencil: 68178455185675213864960.00 staff space Setting to zero. continuing, cross fingers -programming error: Improbable offset for stencil: 823787934458423451582464.00 staff space +programming error: Improbable offset for stencil: 68178455185675213864960.00 staff space Setting to zero. continuing, cross fingers -programming error: Improbable offset for stencil: 823787934458423451582464.00 staff space +programming error: Improbable offset for stencil: 68178455185675213864960.00 staff space Setting to zero. etc. -snip- ../input/regression/footnote-auto-numbering.log ../input/regression/footnote-auto-numbering-page-reset.log ../input/regression/footnote-footer-padding.log ___ 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
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 #f or (format #t in the .ly files in the patch first of all, and see how it behaves on a Guile V1.8 and Guile V2 system. Cheers, Ian ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1786 in lilypond: New engraver for braces
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 add braces the same way as arpeggios. Very useful for complex organ music. Check this out, there is several examples: http://imslp.org/wiki/12_Pi%C3%A8ces_pour_Orgue_(Gigout,_Eug%C3%A8ne) For the moment, the new engraver is a clone of Arpeggio_engraver. But I would like to add a command to attach text directly to braces (see IMSLP's score). Since there's many cases for the text attachment points, I think a new engraver is required. Done with Mike's help. The regression test is temporary. Regards, Bertrand PS: Li Jie Wong requested this last year : http://lists.gnu.org/archive/html/lilypond-user/2010-11/msg00361.html --snip--- ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1567 in lilypond: Add documentation for footnotes
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 about them exists in the two new regtests (233aad0ba9781e43424c4e77a859e42b660210e6). The most important thing to note is that, if people want to use non-automatic footnotes, they must now add footnote-auto-numbering=##f in the paper block. Otherwise, Lily will attempt to do auto numbering and erase whatever numbering scheme the person is manually using. --snip-- ___ 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
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? (I don't remember the policy about format, so this may be completely silly) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Failing regtests because of footnotes.
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 now should be \version "2.15.7" (unless it also works in 2.15.0) and any convert-ly rule should be for (2, 15, 7) Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Failing regtests because of footnotes.
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.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1503 in lilypond: Feature request: simplify jazz chord display
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. Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1765 in lilypond: Clean up regtest mozart-hrn-3
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 it through a countdown. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Wrong link on German Home Page
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 links (although the link text >> is now different for the new version 2.15.6). > > Seems it won't come online until lilypond 2.16 will be released. Website is > only changed with a new stable release. Not exactly. Website is built hourly from Master branch. I have just arrived from Madrid and will merge lilypond/translation into master soon. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1765 in lilypond: Clean up regtest mozart-hrn-3
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 previous version - there are very slight spacing changes and the use of \afterGrace places the grace notes very slightly differently. It also gets rid of the warnings. PDF attached. I suspect there's not a line in the regtests unchanged. How should we proceed with using the new version? Attachments: mozart-hrn-3.pdf 643 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Wrong link on German Home Page
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 the new version 2.15.6). Seems it won't come online until lilypond 2.16 will be released. Website is only changed with a new stable release. Till Best Urs please cherry-pick for 2.14 as well. As for the bug mentioned by James it is not existent anymore in 2.14 as far as I can tell so I would suggest closing the issue. Greetings Till Am 20.07.11 00:33, schrieb Francisco Vila: 2011/7/19 James Lowe: Hello, From: bug-lilypond-bounces+james.lowe=datacore@gnu.org [bug-lilypond-bounces+james.lowe=datacore@gnu.org] on behalf of Urs Liska [lilyli...@googlemail.com] Sent: 18 July 2011 10:55 To: bug-lilypond@gnu.org Subject: Wrong link on German Home Page Hi list, in the German version of the front page the direct links to the development version are broken. They point to community.de.html instead of development.de.html. I think this keeps many people from downloading the development version or even look at their manuals. http://code.google.com/p/lilypond/issues/detail?id=1656 James Thanks. Till, could you please try to fix this? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1765 in lilypond: Clean up regtest mozart-hrn-3
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 bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 732 in lilypond: Alignment problems when vertically stacking horizontally centered stencils.
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 a43a9465fda1728a64fae3619c3f936589dbbdf0 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1744 in lilypond: \once \set behavior should be documented
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 there is no need to document any unexpected behavior any more, since \once \set works just as expected. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 153 in lilypond: \once \set fails to restore previous setting
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 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Collision between figures and tie
> > 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/bug-lilypond
Re: Issue 1111 in lilypond: Allow manual directions on dynamics to break alignment spanner automatically
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 d959f8d548dc073c162c4599cfef2a596f9b66db ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1433 in lilypond: \breakDynamicSpan breaks with \break ("bounds of spanner are invalid")
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 cf3642858a2340bb39ee56739f34c799946d4454
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1259 in lilypond: DynamicTextSpanner #'style = #'none doesn't work over \break
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 cf3642858a2340bb39ee56739f34c799946d4454 ___ 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
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 while this should be read by the Lilypond parser. No idea what this is. I suppose we should close this particular report for now (not least of all since it was not supposed to happen in the first place) and merge this into the issue for guilev2 in general. ___ 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
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 with Guile V1.87. It looks like Guile V2 is not picking up the superseded definition of (format) from the Guile (lily) module, but is falling back to calling the (ice-9 format) direct. Cheers, Ian ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Slurs and PhrasingSlurs with simultaneous start or end
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 in the second bar
> where the PhrasingSlur has been tweaked so that it doesn't intersect
> the slur:
I guess this is 304:
http://code.google.com/p/lilypond/issues/detail?id=304
And may be related to:
http://code.google.com/p/lilypond/issues/detail?id=163
> \version "2.14.0"
>
> offsetPhrasingSlurPos =
> #(define-music-function (parser location offsets) (pair?)
> #{
>\once \override PhrasingSlur #'positions = #(lambda (grob)
> `(,(+ (car $offsets) (cdar
> (ly:phrasingslur::calc-control-points grob))) .
>,(+ (cdr $offsets) (cdr (cadddr
> (ly:phrasingslur::calc-control-points grob))
> #})
>
> \relative c'' {
> \time 3/4
> \slurDashed
> c16\(( d) e f g8\) c,8 d16\(( c) b a\)
> \offsetPhrasingSlurPos #'(0.3 . 0) c16\(( d) e f g8\) c,8
> \offsetPhrasingSlurPos #'(0.3 . 0) d16\(( c) b a\)
> }
>
>
> Nick
--
Dmytro O. Redchuk"Easy to use" is easy to say.
Bug Squad -- Jeff Garbers
___
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 #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 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1663 in lilypond: Images missing on web site
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) has a similar problem. Browse big-contributor and we see the images; browse split contributor and they're not there: http://lilypond.org/doc/v2.15/Documentation/contributor/overview-of-lilypond-architecture ___ 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
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 ...) statement still happens, but there's no deprecation warning
(see first log). I then tried working around by changing the call in
titling-init.ly to
tagline = \markup {
\with-url
#"http://lilypond.org/";
\line {
%% 2014 = em dash.
#(ly:export
Before fix
(format "Music engraving by LilyPond ~a~awww.lilypond.org"
(lilypond-version)
(ly:wide-char->utf-8 #x2014)
))
(string-concatenate
(list "Music engraving by LilyPond ~a~awww.lilypond.org"
(lilypond-version)
(ly:wide-char->utf-8 #x2014)
)))
with patch and work-round
}
}
This changed the signal from Guile to another spot in titling-init.ly (see
second log).
Cheers Ian
Attachments:
testv2withpatch1.log 10.2 KB
testv2withpatch2.log 9.1 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1572 in lilypond: Enhancement req: Change chord name separator and inversion separator, separately
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 https://github.com/aspiers/lilypond soon) and will submit this and other patches for formal review soon. ___ 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:
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 before your change
caused Guile to signal a deprecation warning from (ice-9 format), before
causing Lilypond to abort the compilation completely.
tagline = \markup {
\with-url
#"http://lilypond.org/";
\line {
%% 2014 = em dash.
#(ly:export
Before fix
(format "Music engraving by LilyPond ~a~awww.lilypond.org"
(format #f "Music engraving by LilyPond ~a~awww.lilypond.org"
(lilypond-version)
(ly:wide-char->utf-8 #x2014)
))
}
}
Here's a log from firing up lily to compile a simple file before applying
your patch. Thanks for your work so far in helping to trace this, I'll add
some more information shortly,
Cheers Ian
Attachments:
2-15-6-crash.log 10.5 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1572 in lilypond: Enhancement req: Change chord name separator and inversion separator, separately
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-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
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, but fit_factor can indeed
change the numerical result exactly.
I put a pretty print right after the calculation of height on line 166 of
slur-configure.cc that gets the results below:
\version "2.11.4"
\layout{ragged-right=##t}
\relative c {
\clef bass
c8( d' a d c, d' a d)
c,( des' as des c, des' as des)
}
WITH ACCIDENTAL (first 8 notes):
HEIGHT 7.5342
HEIGHT 7.5966
HEIGHT 7.6652
HEIGHT 7.7397
HEIGHT 7.8201
HEIGHT 7.9061
HEIGHT 7.8044
HEIGHT 7.5583
HEIGHT 7.4280
HEIGHT 7.4779
HEIGHT 7.5342
HEIGHT 7.5966
HEIGHT 7.6652
HEIGHT 7.7397
HEIGHT 7.6593
HEIGHT 7.3961
HEIGHT 7.1501
HEIGHT 7.3845
HEIGHT 7.4280
HEIGHT 7.4779
HEIGHT 7.5342
HEIGHT 7.5966
HEIGHT 7.4747
HEIGHT 7.1942
HEIGHT 6.9335
HEIGHT 6.6900
HEIGHT 7.3476
HEIGHT 7.3845
HEIGHT 7.4280
HEIGHT 7.4779
HEIGHT 7.2252
HEIGHT 6.9293
HEIGHT 6.6558
HEIGHT 6.4015
HEIGHT 6.1639
HEIGHT 7.3172
HEIGHT 7.3476
HEIGHT 7.2056
HEIGHT 6.8719
HEIGHT 6.5664
HEIGHT 6.2850
HEIGHT 6.0243
HEIGHT 5.7814
HEIGHT 5.5541
HEIGHT 7.0555
HEIGHT 6.6905
HEIGHT 6.3589
HEIGHT 6.0555
HEIGHT 5.7762
HEIGHT 5.5174
HEIGHT 5.2764
HEIGHT 5.0510
HEIGHT 4.8391
HEIGHT 5.9249
HEIGHT 5.6170
HEIGHT 5.3338
HEIGHT 5.0718
HEIGHT 4.8281
HEIGHT 4.6003
HEIGHT 4.3863
HEIGHT 4.1845
HEIGHT 3.9936
HEIGHT 4.5814
HEIGHT 4.3399
HEIGHT 4.1138
HEIGHT 3.9011
HEIGHT 3.7002
HEIGHT 3.5096
HEIGHT 3.3284
HEIGHT 3.1554
HEIGHT 2.9897
HEIGHT 3.0476
HEIGHT 2.8713
HEIGHT 2.7021
HEIGHT 2.5392
HEIGHT 2.3822
HEIGHT 2.2302
HEIGHT 2.0830
HEIGHT 1.9401
HEIGHT 1.8010
WITHOUT ACCIDENTAL (last 8 notes):
HEIGHT 5.1913
HEIGHT 4.9759
HEIGHT 4.7668
HEIGHT 4.5637
HEIGHT 4.3661
HEIGHT 4.1736
HEIGHT 3.9859
HEIGHT 3.8028
HEIGHT 4.8371
HEIGHT 4.6237
HEIGHT 4.4165
HEIGHT 4.2149
HEIGHT 4.0185
HEIGHT 3.8270
HEIGHT 3.6401
HEIGHT 3.4575
HEIGHT 3.2791
HEIGHT 4.2132
HEIGHT 4.0101
HEIGHT 3.8120
HEIGHT 3.6187
HEIGHT 3.4299
HEIGHT 3.2452
HEIGHT 3.0645
HEIGHT 2.8875
HEIGHT 2.7140
HEIGHT 3.5412
HEIGHT 3.3490
HEIGHT 3.1609
HEIGHT 2.9765
HEIGHT 2.7956
HEIGHT 2.6181
HEIGHT 2.4438
HEIGHT 2.2726
HEIGHT 2.1043
HEIGHT 2.8225
HEIGHT 2.6414
HEIGHT 2.4631
HEIGHT 2.2876
HEIGHT 2.1147
HEIGHT 1.9442
HEIGHT 1.7762
HEIGHT 1.6613
HEIGHT 1.6639
HEIGHT 2.0611
HEIGHT 1.8902
HEIGHT 1.7211
HEIGHT 1.6510
HEIGHT 1.6526
HEIGHT 1.6545
HEIGHT 1.6566
HEIGHT 1.6588
HEIGHT 1.6613
HEIGHT 1.6469
HEIGHT 1.6475
HEIGHT 1.6485
HEIGHT 1.6496
HEIGHT 1.6510
HEIGHT 1.6526
HEIGHT 1.6545
HEIGHT 1.6566
HEIGHT 1.6588
HEIGHT 1.6465
HEIGHT 1.6469
HEIGHT 1.6475
HEIGHT 1.6485
HEIGHT 1.6496
HEIGHT 1.6510
HEIGHT 1.6526
HEIGHT 1.6545
HEIGHT 1.6566
HEIGHT 1.6464
HEIGHT 1.6465
HEIGHT 1.6469
HEIGHT 1.6475
HEIGHT 1.6485
HEIGHT 1.6496
HEIGHT 1.6510
HEIGHT 1.6526
HEIGHT 1.6545
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
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://codereview.appspot.com/4817048) by only checking for height problems when extra encompasses are involved. 100% of the problems are from the way that extra encompasses are handled. The problem could potentially be coming from the function fit_factor in slur-configuration.cc. This is the function that would modify the curve w/ respect to the extra encompass objects. I'll do some snooping... ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
