Re: bug report

On Thu, 2002-07-25 at 02:06, Han-Wen wrote: > Sorry for the delay -- I'm not sure what caused this, but I fixed this > in CVS. You now get a programming_error in stead of a crash. thanks, han-wen. i'm compiling the cvs sources now. greetings, simon. -- Confucius say, man who live in glass house

tie collision

The following example produces heavy tie collisions: ~ I think the following algorithm handles ties between chords gracefully: For an up-tie, first check the left chord. If the start note is the lower note of a second interval, shorten the tie. Then check the right chord. If the e

Re: bug report

On Thu, 2002-07-25 at 02:06, Han-Wen wrote: > Sorry for the delay -- I'm not sure what caused this, but I fixed this > in CVS. You now get a programming_error in stead of a crash. hmm, i have downloaded the cvs source from lilypond.org using: $ cvs -d :pserver:[EMAIL PROTECTED]:/home/lilypond lo

Re: bug report

[EMAIL PROTECTED] writes: > On Thu, 2002-07-25 at 02:06, Han-Wen wrote: > > Sorry for the delay -- I'm not sure what caused this, but I fixed this > > in CVS. You now get a programming_error in stead of a crash. > > hmm, i have downloaded the cvs source from lilypond.org using: The CVS repositor

Lilypond crash, signal 11

[EMAIL PROTECTED] writes: > Hello. The following occurred while trying to compile the full score > for the Magic Flute overture (recently published on Mutopia at > >). > > I'm afraid it's only a

Re: Beaming errors in 1.5.66

> > \score{ > > \context Staff \notes\relative c'''{ > > % 1. If you remove the grace note, the stem length of the first > > % triplet looks well! How can it possibly be affected by the > > % following grace note??? > > because the beam is an auto-beam, created "after the fact", u

Re: comments on CVS from 2002-07-14 15:58 (long)

Take a look at input/test/music-box.ly. Also, Arnold has made a simple preprocessing tool that easily handles these things. /Mats > Apropos abbreviations: I have two requests which could save a lot of > time for typing: > > . A special construction which returns the same notes in a chord

Re: configure bug?

> > That's odd. A quick test seems to to indicate that it works over > > here. Does your compiler have /usr/local as a preferred prefix? Try: > > > > echo '#include ' > foo.c > > cc -v -c foo.c > > I am not a compiling guru by any means but I do not believe > that /usr/local is p

Re: configure bug?

> > [EMAIL PROTECTED] writes: > > > > > > > Also unrelated to the compile; any idea why I am getting these with 1.4.1 > > 5? > > > > > > > > programming error: Infinity or NaN encountered while converting Real numb > > er; setting to zero. (Continuing; cross thumbs) > > > > > > No, that's not go

improved accidental algorithm (with images)

Here my algorithm again, this time with images. Werner == Preliminaries: The input order is the accidentals from top to down, subject to some reordering in rule 0. In the following, a `second' interval is c

lilypond-book: printfilename+verbose?

Currently, the printfilename option in lilypond-book is disabled if you also use the {small,}verbatim option. Are there any strong reasons for this feature? Even if you have the example printed verbatim in the document you may want to find the file to try and modify the example yourself. Unless

improved accidental algorithm (with images)

[EMAIL PROTECTED] writes: > > Here my algorithm again, this time with images. one small comment: in some cases there is not much difference between lily and your algorithm. Lily doesn't yet use accurate bboxes for the naturals, so it won't squash them as close your solution. -- Han-Wen Nienhu

lilypond-book: printfilename+verbose?

[EMAIL PROTECTED] writes: > Currently, the printfilename option in lilypond-book > is disabled if you also use the {small,}verbatim option. > Are there any strong reasons for this feature? Even if No, i'd say it is a bug. BTW, if you don't know what do else :), it would be nice to get a clickabl

Re: improved accidental algorithm (with images)

> one small comment: in some cases there is not much difference > between lily and your algorithm. Lily doesn't yet use accurate > bboxes for the naturals, so it won't squash them as close your > solution. I've mentioned this already in the algorithm version with images. Note that the images sho

Re: Beaming errors in 1.5.66

Mats Bengtsson <[EMAIL PROTECTED]> writes: > Here's an example of two beaming errors in 1.5.66. Also ugly autoknee Fixed in CVS >/Mats > > \score{ > \context Staff \notes\relative c'''{ > % 1. If you remove the grace note, the stem length of the first > % triplet looks well! How c

Re: configure bug?

> > > That's odd. A quick test seems to to indicate that it works over > > > here. Does your compiler have /usr/local as a preferred prefix? Try: > > > > > > echo '#include ' > foo.c > > > cc -v -c foo.c > > > > I am not a compiling guru by any means but I do not believe > > that /