Carl
At first glance this looks like a major improvement!
I'm tied up today, but I'll give it a whirl within a
day or two.
Trevor
- Original Message -
From:
To:
Cc: ;
Sent: Sunday, June 13, 2010 2:47 AM
Subject: Redo autobeam settings to make resetting easier
(issue1667041)
R
On 13 June 2010 07:02, Boris Shingarov wrote:
> "Your post is absolutely unnecessary"
> http://www.mail-archive.com/lilypond-u...@gnu.org/msg52334.html
That comment wasn't directed at Jiříi; it was part of a reply to David Kastrup.
Regards,
Neil
___
Neil Puttock writes:
> On 13 June 2010 07:02, Boris Shingarov wrote:
>
>> "Your post is absolutely unnecessary"
>> http://www.mail-archive.com/lilypond-u...@gnu.org/msg52334.html
>
> That comment wasn't directed at Jiříi; it was part of a reply to David
> Kastrup.
And while I am certainly not a
Le 13 juin 2010 à 15:22, David Kastrup a écrit :
> If the worst Boris can come up with with regard to developer attitudes
> are misconstrued postings of mine (heck, I'd think I can be enough of a
> problem without reverting to such tactics) or replies to them, the
> situation cannot be all that ba
On 6/13/10 12:02 AM, "Boris Shingarov" wrote:
> Hi Graham and all Lilyponders,
>
> I was quite astonished to hear that my slides were understood to mean anything
> pessimistic or negative. If they give people this impression, then it is a
> defect of the slides which I will fix.
>
> But rig
Am Sonntag, 13. Juni 2010, um 16:55:01 schrieben Sie:
> May I suggest that "Publisher-Grade" is perhaps a misnomer? This makes it
> sound like we can't produce *any* publisher-grade music without footnotes,
> or endnotes, or widow/orphan control. Perhaps an adjustment to the title
> to "Publisher
Hello,
The attached patch adds a minimal example of what the new vertical
spacing commands look like.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
From b4a7e4cc68ed8e51932db20798ce50c43837cf09 Mon Sep 17 00:00:00 2001
From: Francisco Vila
Date: Sun, 13 Jun 2010 17:27:3
Hello!
I have just started browsing the lily source and would like to send my first
cosmetics patch.
All I did was changed a few "*= 1 /" to"/=" and wrote the needed overloaded /=
operators in interval and offset.
Please let me know if I did anything wrong, as I would like to send some more
pa
Am Mittwoch, 19. Mai 2010, um 11:42:59 schrieb David Kastrup:
> Han-Wen Nienhuys writes:
> > On Mon, May 3, 2010 at 4:22 AM, David Kastrup wrote:
> >> Nice touch, but it's not your work going in the bin.
> >
> > Just for the record: I am ok with the current form of the patch.
>
> As you can see
Am Sonntag, 13. Juni 2010, um 18:48:28 schrieb Lôrinc:
> I have just started browsing the lily source and would like to send my
> first cosmetics patch. All I did was changed a few "*= 1 /" to"/=" and
> wrote the needed overloaded /= operators in interval and offset.
Looks good to me.
I wouldn't
On Sun, Jun 13, 2010 at 6:21 PM, Reinhold Kainhofer
wrote:
> Can't we finally give commit access to David?
Yes, a week or two ago:
http://savannah.gnu.org/project/memberlist.php?group=lilypond
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-
On Sun, 2010-06-13 at 02:02 -0400, Boris Shingarov wrote:
> > BTW, have you fixes for the vertical alignment been pushed yet?
> You mean, the vertical space estimation? There were several bugs
> screwing height-estimation. Some of those fixes are pushed, and some
> are still sitting on Rietveld.
On 13 June 2010 18:22, Reinhold Kainhofer wrote:
> Looks good to me.
I agree, apart from this:
-at (LEFT) += r;
+at (LEFT) += r;
at (RIGHT) += r;
We don't add extra spaces to make columns line up.
Cheers,
Neil
___
lilypond-devel mai
Hi Carl,
Are you sure this is ready for review?
I see comments like this,
// I removed this to solve a bug; need to make sure it's right -- cds
and commented debug code,
+;(display "\nIn auto-beam.scm\n")
and alarm bells start to ring. :)
Also, there are several places where beamSettings is
On 13 June 2010 19:44, Reinhold Kainhofer wrote:
> (At least not in C++... in Scheme we do)
Do we?
The only place I recall this happening is in output-lib.scm for
barline visibility.
Cheers,
Neil
___
lilypond-devel mailing list
lilypond-devel@gnu.or
On 13 June 2010 20:07, Neil Puttock wrote:
> On 13 June 2010 19:44, Reinhold Kainhofer wrote:
>
>> (At least not in C++... in Scheme we do)
>
> Do we?
>
> The only place I recall this happening is in output-lib.scm for
> barline visibility.
I mean, of course, break visibility.
_
Reinhold Kainhofer writes:
> Am Mittwoch, 19. Mai 2010, um 11:42:59 schrieb David Kastrup:
>> Han-Wen Nienhuys writes:
>> > On Mon, May 3, 2010 at 4:22 AM, David Kastrup wrote:
>> >> Nice touch, but it's not your work going in the bin.
>> >
>> > Just for the record: I am ok with the current fo
Hey lilypond developers,
I have an algorithm I'm working on for my waveform patch and I am not
good (or patient) enough at symbolic math to make any headway w/ it. In the
attached python file (which needs numpy to run), line 106 uses linalg.solve
to solve a system of equations with fairly regu
Mike Solomon writes:
> Hey lilypond developers,
> I have an algorithm I'm working on for my waveform patch and I am not
> good (or patient) enough at symbolic math to make any headway w/ it. In the
> attached python file (which needs numpy to run), line 106 uses linalg.solve
> to solve a sys
On 6/13/10 9:17 AM, "Reinhold Kainhofer" wrote:
>
>> If there are other patches that are not yet up to
>> LilyPond status, but might be able to get there, it would be nice to have
>> them listed as issues with patches attached.
>
> I suppose a starting point could be to look at the patches al
On 6/13/10 1:01 PM, "n.putt...@gmail.com" wrote:
> Hi Carl,
>
> Are you sure this is ready for review?
>
> I see comments like this,
>
> // I removed this to solve a bug; need to make sure it's right -- cds
Oh, yeah. I forgot that I had done that. I didn't put it in my notes when
I was work
21 matches
Mail list logo
