Am 03.02.2014 15:15, schrieb Robin Bannister:
Marc Hohl wrote:
Try
\once \override Score.LeftEdge.break-visibility = #all-visible
Thanks, sounds plausible, but it doesn't work either:
Umm ... and with MetronomeMark ?
D'Oh...
Works significantly better ;-)
Sorry for mixing up MetronomeMa
Marc Hohl wrote:
But why does LilyPond seem to ignore '(left-edge)?
It seems it is not "visible".
The first left edge doesn't arise via a line break,
so for pedantic Lilypond the _unbroken_ case applies.
Try
\once \override Score.LeftEdge.break-visibility = #all-visible
Cheers,
Robin
___
Marc Hohl wrote:
Try
\once \override Score.LeftEdge.break-visibility = #all-visible
Thanks, sounds plausible, but it doesn't work either:
Umm ... and with MetronomeMark ?
Cheers,
Robin
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https
Hi lilypond.org,
We have updated your application listing for LilyPond 2.19.2-1 on
MacUpdate.com. Please take a moment to review your application's information to
make sure that everything is correct.
You may view your updated listing by visiting:
https://www.macupdate.com/app/mac/19024/lilypon
Am 03.02.2014 10:45, schrieb Robin Bannister:
Marc Hohl wrote:
But why does LilyPond seem to ignore '(left-edge)?
It seems it is not "visible".
The first left edge doesn't arise via a line break,
so for pedantic Lilypond the _unbroken_ case applies.
Try
\once \override Score.LeftEdge.break-v
[CC'ing to -devel]
Am 03.02.2014 00:44, schrieb Eluze:
Marc Hohl wrote
Hi list,
I want the tempo indication to appear at the leftmost edge of the piece
(I know that Gould has a different opinion about this, but I am using
LilyJAZZ, and the Realbook style does not care about these typographic
c
> Found another worthwhile optimization making a difference
> (basically, not discarding and regenerating a blob that is going to
> get analyzed next anyway). In your use case where almost all
> changes happen in the same large file, this does make a bit of a
> difference, in particular regarding
