A few helpful hints after an accidental tweak.
First off, I noticed something interesting: the nasty chords ALWAYS
appeared the first note following a completed \repeat volta n. Each
chord occurs only once, even if it itself is in a \repeat block.
Because lily doesn't unfold repeats automaticall
Let me broaden said bug a little. The extra thickness between bars
occurs with *all* barlines, not just the |. . It's interesting this
wasn't reported before (or was it?); on OS X 10.3 in Preview.app, at
default zoom, multiline systems look very, very odd. I wonder if this
is a Preview only thi
I get an entirely different error, one that was discussed on this list
in February if I am reading things correctly.
cd ./out-www; texi2dvi --batch lilypond.texi
This is e-TeX, Version 3.141592-2.2 (Web2C 7.5.4)
---! /usr/share/texmf-var/web2c/etex.fmt was written by pdfetex
(Fatal format file er
Lifted entertainer.ly from Han-Wen's web site - don't know what version, so
assumed 0.0.0. Using convert-ly 2.4.3 most everything converted OK. What
follows shows seven bars that have a problem. Seem to be two or three
different bugs. First five bars show \> not moved outside the chord. Last
t
Erik Sandberg wrote:
On Saturday 23 April 2005 19.17, Paul Scott wrote:
Attached is a possibly long awaited example of what seems to me to be a
problem with raggedbottom. With raggedbottom and raggedlastbottom both
set to #t I would expect the music to be right under the header instead
of at th
On Saturday 23 April 2005 19.17, Paul Scott wrote:
> Attached is a possibly long awaited example of what seems to me to be a
> problem with raggedbottom. With raggedbottom and raggedlastbottom both
> set to #t I would expect the music to be right under the header instead
> of at the bottom of the
On Saturday 23 April 2005 17.39, Will Oram wrote:
> I understand your concerns. If I had any more specific information, I
> would have gladly posted it...this is by far not the first time I've
> described a bug on bug-lilypond. I've tooled around with lily
> for...wow, 1.5 years already. Anyway, I
Attached is a possibly long awaited example of what seems to me to be a
problem with raggedbottom. With raggedbottom and raggedlastbottom both
set to #t I would expect the music to be right under the header instead
of at the bottom of the page. If not what values of these variables
would give me
I understand your concerns. If I had any more specific information, I
would have gladly posted it...this is by far not the first time I've
described a bug on bug-lilypond. I've tooled around with lily
for...wow, 1.5 years already. Anyway, I have done my absolute best to
identify the root of the
On Saturday 23 April 2005 05.17, Will Oram wrote:
> I have a rather simple project going in 2.5.20. It looks fine on
> output. For awhile, it sounds just as good on MIDI, then...BLARGH!
> You're hit with a single chord that sounds like you sat on your
> Wurlitzer. Then it's back to normal. This hap
I'm sorry, I seem to need new glasses!
/Bernard
Bernard Hurley wrote:
> But it would be helpful if you would tell us what version you are using.
>
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
I don't know what others on the list think but, personally, I would not
be prepared to even look at this unless you _post_ enough information
(e.g. a small example) to illustrate the problem. That way everyone
knows what the bug is and everyone knows when it has been fixed. I am
not altogether hap
This is a bug. Thickness between staffs slightly greater than in staffs.
But it would be helpful if you would tell us what version you are using.
/Bernard
On Sat, 2005-04-23 at 04:40 -0400, Will Oram wrote:
> This is an extreme zoom in on the end of a system in 2.5.20.
>
> http://spamguy.cwru.e
This is an extreme zoom in on the end of a system in 2.5.20.
http://spamguy.cwru.edu/misc/images/barline.jpg
Notice the jaggedness of the "|.". Anal? Maybe. But at 100%, I think I
can see it, and it looks ugly.
focus on the wherefore
for in it lies the question
---
I had the same problem. From what I've read, the flex API has changed
since 2.5.4a. Here's what I did to fix it:
sed -i -e 's:\$\(FLEX\) :\$\(FLEX\) -l :' stepmake/stepmake/c-rules.make
The "-l" flag tells flex to behave like old-school lex. It seems like
the configure script should take care
15 matches
Mail list logo
