[EMAIL PROTECTED] writes:
> During my editing I've found what I believe to be bugs:
>
> 1.
> In order to get a very narrow spaced measure for a special purpose in
> one of my scores I tried to achieve that by inserting a 3/16 measure.
> But Lilypond doesn't like that and abends with this error message:
>
> Calculating column positions... [3]assertion "d >= 0 && d <= 100 CM"
> failed: file "spring-spacer.cc", line 376
Can you send an example.
> 2.
> I generally prefere to do source file editing with emacs and therefore
> installed mudela-mode within my emacs load-path. Emacs wouldn't
> byte-compile line 163:
>
> (setf comment-start-skip "%{")
>
> before I changed it to
>
> (setq comment-start-skip "%{")
thanks.
>
> My elisp knowledge is more than modest but nonetheless I wonder if this
> line isn't superfluous as comment-start-skip is defined a few lines
> earlier in the statement
I don't know how to write emacs modes, I sort of tried copying python
mode. Suggestions/patches are appreciated.
> - I would like to avoid that ties across line breaks run _through_ the
> clef on the new line
fixed in .3
> - I would like the possibility of forcing clef- and key- changes to be
> printed _after_ the new bar line
> [..]
I put your things on the TODO list. In the meantime, if you feel like
hacking C++, don't hesitate to ask for directions.
> - do I need to get warnings on 'No one to print a repeat brace' when I
> issue a '\repeat fold 2 \alternative' statement with an empty leading
> text item in a \lyrics context in order to achieve multiple lyrics lines
> in a _section_ of a score ?
Yes, you can ignore them.
--
Han-Wen Nienhuys, [EMAIL PROTECTED] ** GNU LilyPond - The Music Typesetter
http://www.cs.uu.nl/people/hanwen/lilypond/index.html
