Re: Add \path markup command, and use it for \eyeglasses. (issue1730044)

cool idea for a patch http://codereview.appspot.com/1730044/diff/1/2 File scm/define-markup-commands.scm (right): http://codereview.appspot.com/1730044/diff/1/2#newcode667 scm/define-markup-commands.scm:667: closepath just a random comment: while the syntax/interface makes sense for someone typ

Re: bounties

On 06/21/2010 06:37 PM, Kieren MacMillan wrote: > However, for me personally -- i.e., how I will spend my assistance and > sponsorship time, money, and effort -- trying to make Lilypond a better > *composing* tool is a total non-issue, whereas fixing the innumerable > *engraving* problems remain

Re: bounties

Hi Joseph, > it seems there are a bunch of optimizations and improvements > that would be needed to see Lilypond becoming a serious contender > on mobile or low-power devices etc. Agreed -- and I believe that should be a serious short-term objective for the community. > I'm speaking purely from

[Doc Patch] Re: (2.13.x) bottom-system-spacing

Hi, dear developers & doc reviewers, concerning the documentation of bottom-system-spacing discussed on -bug, I'd like to propose some additions/corrections to the docs. All those deal with NR 4.1.2, "Page formatting". Cheers, Alexander On 2010-06-1

Re: Add \path markup command, and use it for \eyeglasses. (issue1730044)

On 2010/06/22 04:27:22, hanwenn wrote: cool idea for a patch Interesting -- why is path given as a string instead of a list of commands, ie "moveto 0 0 rcurveto 1 2" '((moveto 0 0) (curveto 1 2)) moveto and curveto can be defined in the .scm backends appropriately -- possibly we a

q notation for repeated chords should also copy \harmonic...?

dear list, this time not being sure whether it's a bug, feature or possible enhancement, i wanted to mention that in a situation like: 1 q the second chord is missing the harmonic not head (here, i. e. 2.13.25 git from yesterday). BTW the place of documentation of the "q" thing in the no

Re: Align metronome mark at time signature or first musical element. Fixes #684. (issue1579041)

On 2010/06/20 21:57:20, Neil Puttock wrote: AARGH. Again this web interface eats my email. Is anyone using this, it is so frustrating. I'm going to try using plain email response now. http://codereview.appspot.com/1579041/show ___ lilypond-devel m

Re: Align metronome mark at time signature or first musical element. Fixes #684. (issue1579041)

Hi Neil, Not sure how to find the email address to bind this to http://codereview.appspot.com/1579041 ? http://codereview.appspot.com/1579041/diff/19001/20003#newcode82 lily/metronome-engraver.cc:82: == ly_symbol2scm ("staff-bar")) can't this be incorporated into 'break-align-symbols for Metro

Re: Align metronome mark at time signature or first musical element. Fixes #684. (issue1579041)

On 6/22/10 12:51 PM, "jan.nieuwenhui...@gmail.com" wrote: > On 2010/06/20 21:57:20, Neil Puttock wrote: > > AARGH. Again this web interface eats my email. It came fine to me, just 10 minutes later. Carl ___ lilypond-devel mailing list lilypond-

Re: Experimental support for woff fonts in svg. (issue1428042)

I'm using a 64 bit machine (Ubuntu 10.04). Me too. Fresh doc build succeeds? You still have a problem with this, is your doc build tree clean? Jan. http://codereview.appspot.com/1428042/show ___ lilypond-devel mailing list lilypond-devel@gnu.org h

Quickstart guide

On 06/21/2010 12:18 AM, I wrote: > On 06/20/2010 06:10 PM, David Kastrup wrote: > > You can't stop at selling Lilypond to somebody without having an > > answer to "how do I start this thing"? How many people are complaining > > that they double-click on the Lilypond icon and nothing happens? > >

Re: Quickstart guide

On Tue, Jun 22, 2010 at 09:16:34PM +0200, Joseph Wakeling wrote: > I was sure there was some kind of one-page quickstart guide in the > documentation, but looking on the development version doc pages at > http://kainhofer.com/~lilypond/ I can't find one -- at least, it's not > immediately apparent

RE: q notation for repeated chords should also copy \harmonic...?

Hello, -Original Message- From: bug-lilypond-bounces+james.lowe=datacore@gnu.org on behalf of Arno Waschk Sent: Tue 22/06/2010 19:17 To: Lilypond Bugreports; lilypond-devel@gnu.org Subject: q notation for repeated chords should also copy \harmonic...? --snip--- BTW the place of doc

Re: Experimental support for woff fonts in svg. (issue1428042)

On 2010/06/22 19:09:43, jan.nieuwenhuizen wrote: You still have a problem with this, is your doc build tree clean? I'm just starting a completely clean build. Will report back as soon as it's finished. Cheers, Neil http://codereview.appspot.com/1428042/show

Re: Fix 1112. (issue1670042)

On 2010/06/21 18:28:52, joeneeman wrote: We read it in several places, but we never set it to anything other than zero. So it's ready to be used as soon as we decide to set it to something better than zero, but I don't know what that is yet... Ah, I see. So the same applies to between_sys

Re: q notation for repeated chords should also copy \harmonic...?

On 22 June 2010 19:17, Arno Waschk wrote: > this time not being sure whether it's a bug, feature or possible > enhancement, i wanted to mention that in a situation like: > > 1 q > > the second chord is missing the harmonic not head (here, i. e. 2.13.25 git > from yesterday). It's intended behavi

Re: tablature: ties and harmonics (issue1669041)

On 2010/06/21 19:06:52, marc wrote: Now I *must* overlook the obvious, because the fret numbers still disappear, even if they are not tied together. Remember what I said about 'layer? Both TabNoteHead and HarmonicParenthesesItem have the same default layer (1), but the latter is likely to b

New vertical spacing: congratulations!

Hi! I have seen for weeks the new vertical spacing system being implemented all along this version 2.13. I managed to (try to) understand it correctly, I used it with default values and I also tried it with modifying values of vertical variables. Right now I see many recently-opened bugs related t

Re: q notation for repeated chords should also copy \harmonic...?

On 6/22/10 3:28 PM, "Neil Puttock" wrote: > On 22 June 2010 19:17, Arno Waschk wrote: > >> this time not being sure whether it's a bug, feature or possible >> enhancement, i wanted to mention that in a situation like: >> >> 1 q >> >> the second chord is missing the harmonic not head (here,

Re: q notation for repeated chords should also copy \harmonic...?

On Tue, 22 Jun 2010 22:59:05 +0200, James Lowe wrote: Hello, -Original Message- From: bug-lilypond-bounces+james.lowe=datacore@gnu.org on behalf of Arno Waschk Sent: Tue 22/06/2010 19:17 To: Lilypond Bugreports; lilypond-devel@gnu.org Subject: q notation for repeated chords sh

Re: Revised autobeam settings patch -- cleaned up debug comments (issue1667044)

Hi Carl, Here are some preliminary comments. I'll try to give the patch a more thorough going over at the weekend. The indentation for the alist in time-signature-settings.scm is a bit compressed (particularly for beam-settings). Here's a sample of how it looks after reindentation: (define-pu

Re: Experimental support for woff fonts in svg. (issue1428042)

On 2010/06/22 21:06:16, Neil Puttock wrote: I'm just starting a completely clean build. Will report back as soon as it's finished. OK, I cleaned my local repo out, rm -rf * git reset --hard origin and rebuilt from scratch. The clean build completed without a hitch, so it looks like a di

Re: Revised autobeam settings patch -- cleaned up debug comments (issue1667044)

THanks for the review, Neil. As far as the indentation on the alist goes, did you reindent the whole list, or just the beam-settings part? I ask this, because the sample you gave has different indentation for beam-settings than for the time signature. Thanks, Carl http://codereview.appspot.

Re: [frogs] Re: tablature: ties and harmonics (issue1669041)

n.putt...@gmail.com schrieb: On 2010/06/21 19:06:52, marc wrote: Now I *must* overlook the obvious, because the fret numbers still disappear, even if they are not tied together. Remember what I said about 'layer? Yes, of course, but since the HarmonicParenthesesItem *did* work before witho