I am working up a series of chord sheets for myself and I have run into
some page turning problems. It seems very awkward with my limited
knowledge to get good control over vertical spacing as well as getting
page brakes in the right place. What is the most systematic way to do
this? Is
Andrea Rossato [EMAIL PROTECTED] writes:
I'm trying to find a cleaner solution: is it possible to define that
function inside a .ly file?
I tried, by adding a # before the definition, but I get an error message.
Putting the sharp sign should really do it:
#(define-public
I
am working up a series of chord sheets for myself and I have run into
some page turning problems. It seems very awkward with my limited
knowledge to get good control over vertical spacing as well as getting
page brakes in the right place. What is the most systematic way to do
this? Is there
In message [EMAIL PROTECTED], Erik Sandberg
[EMAIL PROTECTED] writes
Since this intermediate file is a valid Lilypond file, an intermediate
pass can perform some kind of transformation
on it before passing it back to Lilypond for actual processing.
Is this reasonable ? or is Lilypond's internal
