James pkx1...@gmail.com writes:
--snip--
james@jameslilydev2:~/Desktop/patchy$ ./run-lilypond-staging.sh
remote: Counting objects: 83, done.
remote: Compressing objects: 100% (57/57), done.
remote: Total 57 (delta 45), reused 0 (delta 0)
Unpacking objects: 100% (57/57), done.
From
Reviewers: ,
Message:
The idea here is to create a generic framework that allows for
modifications to note lengths (i.e. swing) in the MIDI without having a
typographical impact on the score.
Description:
Creates a MIDI note length formatter
Please review this at
David,
On 29 January 2012 08:48, David Kastrup d...@gnu.org wrote:
James pkx1...@gmail.com writes:
--snip--
james@jameslilydev2:~/Desktop/patchy$ ./run-lilypond-staging.sh
remote: Counting objects: 83, done.
remote: Compressing objects: 100% (57/57), done.
remote: Total 57 (delta 45),
David,
On 29 January 2012 02:26, David Kastrup d...@gnu.org wrote:
Nicolas Sceaux nicolas.sce...@gmail.com writes:
Le 26 janv. 2012 à 11:00, David Kastrup a écrit :
The bad news is that absolute pitch friends would have to call the \q
function (any better name for it?) explicitly. Since q
James pkx1...@gmail.com writes:
So we need to make any tweaks to the NR since
...There is no longer any relation of
the implementation to \relative...
http://lilypond.org/doc/v2.14/Documentation/notation/single-voice#chord-repetition
an @warning or @knownissue?
It is more like removing
Phil Holmes m...@philholmes.net wrote in message
news:jfsl4j$1su$1...@dough.gmane.org...
Janek Warchol janek.lilyp...@gmail.com wrote in message
news:CANYDDppbpzXAeepYCZ24rpu+RVQm21gO9beMCw357jxj_w=g...@mail.gmail.com...
Hi,
i think the output of beam-shortened-lengths.ly doesn't look good,
http://codereview.appspot.com/5520056/diff/7001/Documentation/notation/rhythms.itely
File Documentation/notation/rhythms.itely (right):
http://codereview.appspot.com/5520056/diff/7001/Documentation/notation/rhythms.itely#newcode1358
Documentation/notation/rhythms.itely:1358: The @var{duration}
I'm suspicious about collision-dots-move.ly. Look at the penultimate set of
notes - is it the quaver or the crochet that's dotted? (Well - I know it's
obvious from the context, but the new dotting algorithm makes this much more
difficult to tell - even though the others are generally better).
Got no answers on -devel, so I forward here (probably more appropriate
place).
Thanks,
Federico
Il 05/01/2012 13:44, Federico Bruni ha scritto:
Issue 1721 reported that @rlsr{Name} keeps the text in english but
translates the link in the translated manuals (no idea where the
translation comes
James pkx1...@gmail.com writes:
Hello,
On 24 January 2012 22:20, David Kastrup d...@gnu.org wrote:
Janek Warchoł janek.lilyp...@gmail.com writes:
Keeping the staging-merge going would be about five people
committing to 50€ a month. That is, of course, not enough for me to
live on. It
- Original Message -
From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
Sent: Sunday, January 29, 2012 2:34 PM
Subject: Re: somebody needs to run staging before 29 Jan
James pkx1...@gmail.com writes:
Hello,
On 24 January 2012 22:20, David Kastrup d...@gnu.org wrote:
Janek
On Jan 29, 2012, at 3:46 PM, Phil Holmes wrote:
- Original Message - From: David Kastrup d...@gnu.org
To: lilypond-devel@gnu.org
Sent: Sunday, January 29, 2012 2:34 PM
Subject: Re: somebody needs to run staging before 29 Jan
James pkx1...@gmail.com writes:
Hello,
On 24
On Sun, Jan 29, 2012 at 03:34:45PM +0100, David Kastrup wrote:
Patchy has been running for about 6 hours on my laptop trying to get the
current staging (which is one trivial commit ahead of master) checked.
And is still on it.
??? if you look in the build dir, what logs does it have? I
mean,
Graham Percival gra...@percival-music.ca writes:
On Sun, Jan 29, 2012 at 03:34:45PM +0100, David Kastrup wrote:
Patchy has been running for about 6 hours on my laptop trying to get the
current staging (which is one trivial commit ahead of master) checked.
And is still on it.
??? if you
I am not sure whether the q stuff should be slated for 2.16. It
greatly simplifies things and decreases potential for problems, but
I don't see people reporting any test results, and it certainly has
seen less user contact than my totally new code.
As soon it is in master, I'll check it.
Werner LEMBERG w...@gnu.org writes:
I am not sure whether the q stuff should be slated for 2.16. It
greatly simplifies things and decreases potential for problems, but
I don't see people reporting any test results, and it certainly has
seen less user contact than my totally new code.
As
So check it out at least once it is in Patch-review orderly. That
means that it is regtest-clean, but that does not mean that a
feature change will make its main users happy.
OK. BTW, I've meant staging, not master. Sorry for the thinko.
And I might point out that it was you who
Werner LEMBERG w...@gnu.org writes:
So check it out at least once it is in Patch-review orderly. That
means that it is regtest-clean, but that does not mean that a
feature change will make its main users happy.
OK. BTW, I've meant staging, not master. Sorry for the thinko.
Same thing.
OK. BTW, I've meant staging, not master. Sorry for the thinko.
Same thing. Once it is in staging, it will move forward
_automatically_ to master potentially within hours unless there is a
compilation/testing error.
Humpf. I wasn't fully aware of this automatism.
OK, will apply manually
Phil Holmes email at philholmes.net writes:
I'm suspicious about collision-dots-move.ly. Look at the penultimate set of
notes
The change was intended; when voices cross or mesh and dotted notes
end up on the left, most situations are clarified if we raise the dots.
The regression test
Werner LEMBERG w...@gnu.org writes:
OK. BTW, I've meant staging, not master. Sorry for the thinko.
Same thing. Once it is in staging, it will move forward
_automatically_ to master potentially within hours unless there is a
compilation/testing error.
Humpf. I wasn't fully aware of this
[Applying rietveld 5595043 to git afb4c5fb]
It means running your own files that use this feature, and reading
the docs to see whether the docs as well as the new incarnation of
the feature make sense to you.
It was really good that you have been a pain in the neck, since your
patch causes
Werner LEMBERG w...@gnu.org writes:
[Applying rietveld 5595043 to git afb4c5fb]
It means running your own files that use this feature, and reading
the docs to see whether the docs as well as the new incarnation of
the feature make sense to you.
It was really good that you have been a pain
On 12-01-29 11:04 AM, David Kastrup wrote:
Werner LEMBERGw...@gnu.org writes:
OK. BTW, I've meant staging, not master. Sorry for the thinko.
Same thing. Once it is in staging, it will move forward
_automatically_ to master potentially within hours unless there is a
compilation/testing
Colin Campbell c...@shaw.ca writes:
On 12-01-29 11:04 AM, David Kastrup wrote:
Thanks. Note that this does _not_ mean regtests and doc builds: we have
automatisms for that. It means running your own files that use this
feature, and reading the docs to see whether the docs as well as the
On Sun, 29 Jan 2012 22:03:36 -0800, Jay Anderson horndud...@gmail.com wrote:
I agree with Werner that this is a
bug, but with the override it's low priority (it may be worth
documenting however).
I entered it as issue 2264.
The algorithm looks like dynamic programming, which should be
26 matches
Mail list logo
