On 2010-06-16 16:33, Kieren MacMillan wrote:
Hi Alexander,
Ugh, I just recognized that this actually is not arbitrary. \vspace creates a
vertical space of argument /amount/ _multiplied by 3_.
Which does not make sense to me - why * 3? - but okay, then I see why the value
is about a third,
Hi Alexander,
is it possible to tell LilyPond to use the same vertical positions for all
topmost and bottommost staff lines of different pages? Rephrased, can I say
I know what I'm doing, ignore all vertical extents below the last staff
lines of a page for vertical stretching, even if it
On 2010-06-16 13:16, Kieren MacMillan wrote:
Hi Alexander,
is it possible to tell LilyPond to use the same vertical positions for all topmost and
bottommost staff lines of different pages? Rephrased, can I say I know what I'm
doing, ignore all vertical extents below the last staff lines of
On 2010-06-16 14:12, Alexander Kobel wrote:
[...] finding the correct
\vspace value in the footer far easier. (For some reason, the latter is
not quite what I'd expect, e.g. for padding = -100 I need \vspace #31.5
to get a nice result for a two-line footer?!)
Ugh, I just recognized that this
Hi Alexander,
Ugh, I just recognized that this actually is not arbitrary. \vspace creates
a vertical space of argument /amount/ _multiplied by 3_.
Which does not make sense to me - why * 3? - but okay, then I see why the
value is about a third, +- foot-separation.
Would this be fixed by
Hi, all,
is it possible to tell LilyPond to use the same vertical positions for
all topmost and bottommost staff lines of different pages? Rephrased,
can I say I know what I'm doing, ignore all vertical extents below the
last staff lines of a page for vertical stretching, even if it
