The point is to allow users to achieve the same snug skyline spacing
between stencils that is achieved between grobs.
I agree that it is inefficient as skylines are never cached, but as it
is not default beahvior anywhere in the code base, it allows people to
decide on the efficiency versus
On 2013/08/29 06:57:53, MikeSol wrote:
The point is to allow users to achieve the same snug skyline spacing
between
stencils that is achieved between grobs.
I agree that it is inefficient as skylines are never cached, but as it
is not
default beahvior anywhere in the code base, it allows
On 29 août 2013, at 10:25, d...@gnu.org wrote:
On 2013/08/29 06:57:53, MikeSol wrote:
The point is to allow users to achieve the same snug skyline spacing
between
stencils that is achieved between grobs.
I agree that it is inefficient as skylines are never cached, but as it
is not
Where's the point? We don't use that kind of arrangement in our code,
and it's not efficiently doable anyway.
A conceivable application would be for determining systems spacing
manually (for example, generating sequences of TeX \vspace and \break
for LilyPond-book that will reserve normal
