On Mon, 21 Aug 2000, Peter Schaffter wrote:
> lily on for the past five weeks. Why all the time? Because
> lily takes well over an hour to process the .ly file, which
> is a relatively simple, 223 bar piece. I've encountered
> some resource hogs in my time (Netscape springs to mind),
> but right now, lily beats all! I can recompile my kernel in
I'm doing a psalm book with 32MB ram. I find that Lily gets to a
certain point and things just begin to churn. Fortunately, I've done it in
about 50 different .ly files, so if I just give it a Ctrl+C and start again,
it's already compiled half of them, so it doesn't have to do those again. And
as long as I stop it every time it starts churning (currently I need 3 runs
for my 49 page doc), it runs reasonably quickly. I don't know if this is
useful to anyone, but I hope so.
:)
---------------------------------------------------------------------
| Name: Tim Nelson | Because the Creator is, |
| E-mail: [EMAIL PROTECTED] | I am |
---------------------------------------------------------------------
Web: Temporarily unavailable
----BEGIN GEEK CODE BLOCK----
Version 3.1
GCS d? s: a-- C++>++++$ US+ P++ L++ E- W+++ N+ w+> M-- V- Y+>++
PGP->++ R(+) !tv B++ DI++++ D+ G e>++ h!/* y-
-----END GEEK CODE BLOCK-----
