Programming error: script direction not yet known

\version "2.11.49" \new Staff \relative c'' { %\key c \major %Add a key to correct programming errors. << { c16 e a g f e d c } { s16( s) s-. s-. s( s) s-. s-. } >> } I didn't find this one in the bug tracker. I'm swapping out the rhythm on the same passage and this error is created

Re: regressions: version?

2008/6/18 Marc Mouries <[EMAIL PROTECTED]>: > Even if the beam are separated, the notes remain sixteenth note > . So why would one wants to > separate the beams? Is it from an interpretation perspective? > > -Marc > Definately an interpretation perspec

Re: regressions: version?

On Tue, Jun 17, 2008 at 4:08 PM, Valentin Villenave <[EMAIL PROTECTED]> wrote: > 2008/6/17 Stan Sanderson <[EMAIL PROTECTED]>: > >> hmm, the test in my copy of the docs (2.11.49-1, which claims to be proofs >> for 2.11.48) does fail. > > Then why the heck can't we see it on > http://lilypond.org/te

Re: regressions: version?

Even if the beam are separated, the notes remain sixteenth note . So why would one wants to separate the beams? Is it from an interpretation perspective? -Marc Stan Sanderson wrote: On Jun 17, 2008, at 10:50 AM, Valentin Villenave wrote: 2008/6/

Re: regressions: version?

2008/6/17 Stan Sanderson <[EMAIL PROTECTED]>: > hmm, the test in my copy of the docs (2.11.49-1, which claims to be proofs > for 2.11.48) does fail. Then why the heck can't we see it on http://lilypond.org/test/v2.11.49-1/compare-v2.11.48-1/ ??? I'm puzzled. Cheers, Valentin _

Re: regressions: version?

On Jun 17, 2008, at 10:50 AM, Valentin Villenave wrote: 2008/6/17 Stan Sanderson <[EMAIL PROTECTED]>: regressions- lily 2.11.49-1 : version? current (first sentence): This document presents proofs for LilyPond 2.11.48. I do have 2.11.49-1 loaded! Maybe this would explain why the auto-beam-

Re: lilypond-book inserts stanzas entered at the bottom of a song on top of it

Don't get me wrong. I was not reproaching you to have no interest in bug reports at all. When talking of a limited interest I was refering to Mats statement, saying that even bug reports related to the latest stable version, 2.10, are mostly ignored I find nothing negative about having a l

Re: lilypond-book inserts stanzas entered at the bottom of a song on top of it

Claus Tirel wrote: > Please note that there is a waste of time to send bug reports > on such an old version of LilyPond. In fact, even bug reports > related to the latest stable version, 2.10, are mostly ignored Not to mention this limited interest on the lilypond bug page (http://lilypond.or

Re: regressions: version?

2008/6/17 Stan Sanderson <[EMAIL PROTECTED]>: > regressions- lily 2.11.49-1 : version? > > current (first sentence): This document presents proofs for LilyPond > 2.11.48. > > I do have 2.11.49-1 loaded! Maybe this would explain why the auto-beam-beaming-override.ly test hasn't failed (see Issue 63

Re: lilypond-book inserts stanzas entered at the bottom of a song on top of it

2008/6/17 Claus Tirel <[EMAIL PROTECTED]>: > To ignore user's bug reports because of the mentioned version number is, in > my view, a mistake as long as the reported bugs still exist. Please don't say our interest in bug reports is limited. Is *your* interest in having a bug-free program limited?

regressions: version?

regressions- lily 2.11.49-1 : version? current (first sentence): This document presents proofs for LilyPond 2.11.48. I do have 2.11.49-1 loaded! Stan ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-l

Re: lilypond-book inserts stanzas entered at the bottom of a song on top of it

> Please note that there is a waste of time to send bug reports > on such an old version of LilyPond. In fact, even bug reports > related to the latest stable version, 2.10, are mostly ignored Not to mention this limited interest on the lilypond bug page (http://lilypond.org/web/devel/participat

CR/LF regression in Lilypond editor

Hello all, Has anyone else run into issues with the way the Lilypond editor (Mac OS X 10.4) handles CR/LF? I don't remember exactly when, but starting at least five or six .01 versions ago, anything I cut and paste from my Lilypond editor to (e.g.) my email would have no CR/LF left in the