Re: [Lilypond-auto] Issue 3818 in lilypond: Patch: stencil.scm: addmake-path-stencil function

2014-01-23 Thread Paul Morris
Trevor Daniels wrote > It seems you're not authorised to change the labels, so I've done it for > you. Ok, thanks! -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/Re-Lilypond-auto-Issue-3818-in-lilypond-Patch-stencil-scm-addmake-path-stencil-function-tp158369p158

Re: [Lilypond-auto] Issue 3818 in lilypond: Patch: stencil.scm: addmake-path-stencil function

2014-01-23 Thread Trevor Daniels
> Comment #3 on issue 3818 by paulwmor...@gmail.com: Patch: stencil.scm: add > make-path-stencil function > http://code.google.com/p/lilypond/issues/detail?id=3818 > > Attempting to change label to "new" to trigger automated tests. I don't > see any interface for editing labels, just this com

Re: stencil.scm: add make-path-stencil function (issue 54050043)

2014-01-23 Thread paul
On 2014-01-23 15:50, Trevor Daniels wrote: Yes. Go to the issue tracker 3818, click in the box at the bottom to enter a comment, and set the label Patch-countdown to Patch-new, and save. Ah, that makes sense, thanks. However, when I start to enter a comment I don't see any interface for edi

Re: stencil.scm: add make-path-stencil function (issue 54050043)

2014-01-23 Thread Trevor Daniels
Paul Morris wrote Thursday, January 23, 2014 10:44 PM > This second patch set appeared successfully on Rietveld, but it looks like > the automatic test to confirm that it passes make, make check, and make docs > was not triggered: > http://code.google.com/p/lilypond/issues/detail?id=3818 > > So

Re: stencil.scm: add make-path-stencil function (issue 54050043)

2014-01-23 Thread Urs Liska
Am 23.01.2014 23:44, schrieb Paul Morris: paulwmorris wrote On 2014/01/18 04:52:51, lemzwerg wrote: A minor thing: We use two spaces after a full stop in documentation strings. (At least it should be like that in general.) Done. https://codereview.appspot.com/54050043/ This second patch se

Re: stencil.scm: add make-path-stencil function (issue 54050043)

2014-01-23 Thread Paul Morris
paulwmorris wrote > On 2014/01/18 04:52:51, lemzwerg wrote: >> A minor thing: We use two spaces after a full stop in documentation >> strings. >> (At least it should be like that in general.) > > Done. > > https://codereview.appspot.com/54050043/ This second patch set appeared successfully on Ri

Re: Shape of individual ties in chords

2014-01-23 Thread David Nalesnik
On Thu, Jan 23, 2014 at 8:01 AM, David Nalesnik wrote: > >> >>> >> There's also the attached file (which comes from >> http://www.mail-archive.com/lilypond-devel@gnu.org/msg47432/shape-tie-columns.ly) >> which will work with broken ties. >> >> > Here are some more useful values: \shapeTieColumn #

Re: midi control done twice

2014-01-23 Thread James
On 22/01/14 18:16, Devon Schudy wrote: James wrote: is this worth an @KNOWNISSUE in the midi section? I suppose so. "Changes to @code{midiInstrument} and other MIDI options at the beginning of a staff sometimes appear twice in MIDI output."? http://code.google.com/p/lilypond/issues/detail?id=3

Re: Shape of individual ties in chords

2014-01-23 Thread David Nalesnik
Hi again, On Thu, Jan 23, 2014 at 8:01 AM, David Nalesnik wrote: > Hi, > > > On Wed, Jan 22, 2014 at 4:55 PM, Thomas Morley > wrote: > > >> Below some coding just to show that it can be done. >> It's a very first sketch, several issues are present (p.e. linebreak) >> Might be a starting point,

Re: Shape of individual ties in chords

2014-01-23 Thread David Nalesnik
Hi, On Wed, Jan 22, 2014 at 4:55 PM, Thomas Morley wrote: > Below some coding just to show that it can be done. > It's a very first sketch, several issues are present (p.e. linebreak) > Might be a starting point, though. > > There's also the attached file (which comes from http://www.mail-archi