> > Before that, the bad-spacing.ly and good-spacing.ly give the same
> > result.
>
> Fixed in git
Thanks!
> (with a regtest!)
:-) I always try to write my bug reports so that they can be used as
regtests with just minimal editing.
Werner
___
On Fri, 2008-08-15 at 20:01 +0200, Werner LEMBERG wrote:
> > They can usually do that if you can limit the range to a single
> > release.
>
> I've done bisecting. This is the problematic commit:
>
> commit 2b8a93c3007d1789ac67c86b0ed63fbae003fc6e
> Author: Joe Neeman <[EMAIL PROTECTED]>
>
As a general comment - this commit didn't include a comment on the
why, nor a regtest. Could you make sure one is added for any other
changes you make?
thanks,
On Sat, Aug 16, 2008 at 11:57 AM, Joe Neeman <[EMAIL PROTECTED]> wrote:
>> I've done bisecting. This is the problematic commit:
>>
>>
On Fri, Aug 15, 2008 at 11:01 AM, Werner LEMBERG <[EMAIL PROTECTED]> wrote:
> > They can usually do that if you can limit the range to a single
> > release.
>
> I've done bisecting. This is the problematic commit:
>
> commit 2b8a93c3007d1789ac67c86b0ed63fbae003fc6e
> Author: Joe Neeman <[EMAIL
2008/8/15 Werner LEMBERG <[EMAIL PROTECTED]>:
>> They can usually do that if you can limit the range to a single
>> release.
>
> I've done bisecting. This is the problematic commit:
>
> commit 2b8a93c3007d1789ac67c86b0ed63fbae003fc6e
> Author: Joe Neeman <[EMAIL PROTECTED]>
> Date: Mon Aug 6
> They can usually do that if you can limit the range to a single
> release.
I've done bisecting. This is the problematic commit:
commit 2b8a93c3007d1789ac67c86b0ed63fbae003fc6e
Author: Joe Neeman <[EMAIL PROTECTED]>
Date: Mon Aug 6 13:17:21 2007 +1000
Tweak spacing between a musica
They can usually do that if you can limit the range to a single release.
On Fri, Aug 15, 2008 at 3:26 AM, Werner LEMBERG <[EMAIL PROTECTED]> wrote:
>> > Attached are two files which show the difference. Again, I'm posting
>> > it here to the list and not to the bug tracker so that either Han-Wen
> > Attached are two files which show the difference. Again, I'm posting
> > it here to the list and not to the bug tracker so that either Han-Wen
> > or Joe can confirm the problem. Maybe this was an intentional change,
> > and I just missed to adjust my data accordingly.
>
> 2.11.20 to 2.11.55
On Fri, Aug 15, 2008 at 3:03 AM, Werner LEMBERG <[EMAIL PROTECTED]> wrote:
>> I've just found a wonderful example which demonstrates what I want to
>> fix. Look at the fourth and fifth quarter: It's *really* ugly.
>>
>> On the other hand I'm not sure whether this is a different spacing
>> bug. Jo
> I've just found a wonderful example which demonstrates what I want to
> fix. Look at the fourth and fifth quarter: It's *really* ugly.
>
> On the other hand I'm not sure whether this is a different spacing
> bug. Joe?
This is indeed a different bug, caused by my special setup using an
invisib
On Thursday 12 July 2007 00:12, Nicolas Sceaux wrote:
> Hi,
>
> A regression was introduced a few days ago regarding the spacing of
> lines when next-space is set to 0 (this used to be fixed). On
> ragged-bottom pages, the spacing is fine in spite of the programming
> errors ("insane blocking force
Hi,
A regression was introduced a few days ago regarding the spacing of
lines when next-space is set to 0 (this used to be fixed). On
ragged-bottom pages, the spacing is fine in spite of the programming
errors ("insane blocking force"), but otherwise it is wrong.
Example illustrating the problem:
"Han-Wen Nienhuys" <[EMAIL PROTECTED]> writes:
> I don't understand. Where are the callers of
> ly:solve-spring-and-rod-problem changed?
it's changed here:
diff --git a/scm/layout-page-layout.scm b/scm/layout-page-layout.scm
index 6c1f605..91742ef 100644
--- a/scm/layout-page-layout.scm
+++ b/sc
I don't understand. Where are the callers of
ly:solve-spring-and-rod-problem changed?
Or was that the bug?
I agree with the change, since passing 0 in a float is more elegant
than passing inf.
2007/6/9, Nicolas Sceaux <[EMAIL PROTECTED]>:
Hi,
Here is a patch that fixes the zero spacing issue t
Hi,
Here is a patch that fixes the zero spacing issue that can be
demonstrated by the following snippet:
\version "2.11.25"
#(set-default-paper-size "a6")
\paper {
between-system-padding = 0
between-title-space = 0
ragged-bottom = ##f
ragged-last-bottom = ##f
}
\markup h
The attached lilypond file has what seems to be unpleasantly close
spacing of the 'r2 r4 r8' figure. Another part with a similar figure
is less close, but still not as readable as it might be.
altus.ly
Description: Binary data
--
Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ )
(
16 matches
Mail list logo
