Keith,
retested.
http://code.google.com/p/lilypond/issues/detail?id=2051#c9
passes make and a new set of reg test diffs are up.
James
http://codereview.appspot.com/5431065/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.or
Uh, this reads
commit a228baa1e5bb0f0d65c371e7da5076a7d8f58a5e
Author: David Kastrup
Date: Fri Nov 25 18:39:58 2011 +0100
Tiny convertrule fix for occurences of 2468 inside of embedded Scheme with
#{ ... #}
and now it has already made its way into master so I can't change that
cryptic d
- Original Message -
From: "Graham Percival"
To: "Phil Holmes"
Cc: "Devel"
Sent: Friday, November 25, 2011 7:10 PM
Subject: Re: LSR updates and Issue 1971
On Fri, Nov 25, 2011 at 05:59:04PM -, Phil Holmes wrote:
I've got a large patch that updates the snippets from the LSR and
Passes Make - reg tests here:
http://lilypond-stuff.1065243.n5.nabble.com/Tracker-2053-26-November-td5023673.html
Jam
http://codereview.appspot.com/5432070/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/
hi
i am Sacha, new user of Lilypond
i wanted to suggest you the implementation of something very simple in Lilypnd
to get Chord grids
for example a \Chordgrid (width= height = number of raws = number of columns =)
{a/c b:7} etc
that would be very useful
Xavier worked for me and managed to get a g
I saw Steven Schick and Shahrokh Yadegari perform this live, and it literally
changed me as a musician — one of the top ten artistic experiences of my entire
life.
Here's a sample:
Of course, video doesn't match the insane spectacularity of the live
performance (both by Schick and the live pro
On 2011/11/26 07:32:48, dak wrote:
The functionality seems to be there just fine. What makes you suspect
that this
copying-of-properties-at-definition-and-documentation-time is
responsible for a
crash?
I'm just flying blind. Mike pointed out that using properties that
weren't in an interf
I know you've pushed a different patch, which fixes Issue 1900, but
doesn't fix
1997. Have you tried this patch to see if it fixes 1997?
I'll do so, but frankly, if it _does_ fix 1997, I don't want it pushed.
Do you have a reference for Mike's analysis?
It seems we should rather fix the segf
On 2011/11/26 15:07:17, dak wrote:
I'll do so, but frankly, if it _does_ fix 1997, I don't want it
pushed. Do you
have a reference for Mike's analysis?
http://lists.gnu.org/archive/html/lilypond-devel/2011-11/msg00556.html
It seems we should rather fix the segfault at its source than hid
On 2011/11/26 15:15:25, Carl wrote:
On 2011/11/26 15:07:17, dak wrote:
>
> I'll do so, but frankly, if it _does_ fix 1997, I don't want it
pushed. Do
you
> have a reference for Mike's analysis?
http://lists.gnu.org/archive/html/lilypond-devel/2011-11/msg00556.html
>
> It seems we should
On 2011/11/26 15:43:34, dak wrote:
On 2011/11/26 15:15:25, Carl wrote:
Any way, your patch does not fix the segfault on Ubuntu 11.10 without
specific
compilation options, so we can as well forget it, I guess.
OK, I'll close this issue. We have a record of the conversation on
-devel.
Tha
On Nov 26, 2011, at 4:11 AM, k-ohara5...@oco.net wrote:
> On 2011/11/26 02:09:57, Keith wrote:
>> Maybe the *0.5 was converting half-staff-spaces to staff-spaces
> No; the units are fine.
>
> The problem seems to be not so much the overestimate of the slur extent,
> but that said overestimate of
On Nov 26, 2011, at 9:56 PM, Keith OHara wrote:
> Mike, Maybe change-clefs should not get the full extra-spacing-height by
> default.
I could do this if I could call Item::break_visible before line breaking (which
would let me know which clefs are change clefs as opposed to
beginning-of-line-c
On Sat, Nov 26, 2011 at 12:53:55PM -, Phil Holmes wrote:
> - Original Message - From: "Graham Percival"
>
> >if you skim over the patch in gitk, you shouldn't see anything
> >weird. commit that and push directly to staging.
>
> Depends what counts as weird. I see lots of commitish c
On Sat, 26 Nov 2011 14:48:29 -0800, m...@apollinemike.com
wrote:
On Nov 26, 2011, at 9:56 PM, Keith OHara wrote:
Mike, Maybe change-clefs should not get the full extra-spacing-height by
default.
I could do this if I could call Item::break_visible before line breaking (which
would let me
As far as I can see, this patch is approved for pushing, but hasn't been
pushed yet.
Are you going to push it, Adam, or should I push the one that I have?
Thanks,
Carl
http://codereview.appspot.com/5343050/
___
lilypond-devel mailing list
lilypond-
16 matches
Mail list logo
