lilypond-book

2002-07-04 Thread Tom Cato Amundsen
Howdy, just wanted to say that the columnsep support was not BugFree(tm), it was more like PlainStupid(tm) combined with IDontKnowGeometry(tm). I'm working on TheRealSolution with NiceTestSuite and EvenMoreGeometryOptions supported. And don't worry, the changes to lilypond-book will_be_written_in

Re: grob creation

2002-07-04 Thread Rune Zedeler
Citat Han-Wen Nienhuys <[EMAIL PROTECTED]>: > because the result of an acknowledged grob may be a new grob. That new > grob must be acked, and the result may be another grob. The cycle is > continued until no new grobs are created. (example: Note head leads > to stem. Stem leads to beam.) Thank

Re: grob creation

2002-07-04 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > > ... > > because the result of an acknowledged grob may be a new grob. That new > > grob must be acked, and the result may be another grob. The cycle is > > continued until no new grobs are created. (example: Note head leads > > to stem. Stem leads to beam.) > > Soun

Re: grob creation

2002-07-04 Thread Juergen Reuter
On Thu, 4 Jul 2002, Han-Wen Nienhuys wrote: > ... > because the result of an acknowledged grob may be a new grob. That new > grob must be acked, and the result may be another grob. The cycle is > continued until no new grobs are created. (example: Note head leads > to stem. Stem leads to beam.

Re: grob creation

2002-07-04 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > > > It would be technically more correct to make an accidental if there is > > reason, and kill it off later when it is not needed, but that might > > lead to excessive grob creation. > > Well, yes wouldn't that lead to spacing problems and problems with > accidental

grob creation

2002-07-04 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > Still struggling with the accidental engraver. > I still quite haven't understood the idea of the different functions in the > engravers. > I tried moving all the code from "process_asknowledged_grobs" (or whatever name > the function is changed to) to "stop_translati

grob creation

2002-07-04 Thread Rune Zedeler
Still struggling with the accidental engraver. I still quite haven't understood the idea of the different functions in the engravers. I tried moving all the code from "process_asknowledged_grobs" (or whatever name the function is changed to) to "stop_translation_timestep" - and (no surprise) it

Re: lilypond-book patch

2002-07-04 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > > > None of the supported geometry options are documented. So I did it the > > > lazy way, and just listed the options that are not supported. I think > > > the list are complete. People should read the documentation for the > > > geometry package if they want to use it

Re: lilypond-book patch

2002-07-04 Thread Tom Cato Amundsen
On Thu, 2002-07-04 at 13:06, Han-Wen Nienhuys wrote: > [EMAIL PROTECTED] writes: > > On Tue, 2002-07-02 at 02:02, Han-Wen wrote: > > > [EMAIL PROTECTED] writes: > > > > Attached is a patch that adds support for the columnsep when using the > > > > geometry package. > > > > > > Could you also incl

Re: lilypond-book patch

2002-07-04 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > On Tue, 2002-07-02 at 02:02, Han-Wen wrote: > > [EMAIL PROTECTED] writes: > > > Attached is a patch that adds support for the columnsep when using the > > > geometry package. > > > > Could you also include documentation for this option? > None of the supported geometr