Hello, all --
Jan replied:
Programming error messages should indicate bugs in LilyPond, no?
Right.
Then I'd better get this right...
When I use
\once \override Score.BarLine #'space-alist = #'((first-note
extra-space . 1.5))
I get
programming error: No spacing entry from BarLin
David Feuer writes:
> Programming error messages should indicate bugs in LilyPond, no?
Right.
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
___
lily
> Programming error messages should indicate bugs in LilyPond, no?
I've never worked with the code, but my impression from using LilyPond
is that "programming error" messages are not exactly bugs, but more in
the lines of complaints that Lily has been asked to do something too
complicated to figur
On 4/11/06, Geoff Horton <[EMAIL PROTECTED]> wrote:
> > Unfortunately, although it now *looks* correct, I get the error
> > programming error: unknown prefatory spacing
> > continuing, cross fingers
> > once per affected Staff-measure in the Score.
> >
> > Is there a better method than th
> Unfortunately, although it now *looks* correct, I get the error
> programming error: unknown prefatory spacing
> continuing, cross fingers
> once per affected Staff-measure in the Score.
>
> Is there a better method than the one I'm using?
> If not, is this error something I can just ig
Hello, all --
I think I've almost answered my own question:
Is there any easy way to tweak the spacing of *just* the notes
which begin a measure and have an accidental on them
I'm using
\once \override Score.BarLine #'space-alist = #'((first- fixed-
space . 2.0))
at the end of the measur
