-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
lasconic wrote:
| I follow Joe Neeman's advice and it does the trick for me !
| The manual for extra-spacing-width is here :
|
http://lilypond.org/doc/v2.11/Documentation/user/lilypond-learning/Outside-staff-objects
|
| I just added :
| \layout {
|
b | % 4
> d2 e | % 5
> g1 | % 6
>
> a4:maj7/bf cs:sus4/e bf fs:maj7.5+/af | % 1
> c2/g g | % 2
> d2/fs e:m | % 3
> a2:m g/b | % 4
> d2 e | % 5
> g1 | % 6
> }
>
>
> %
> % Chord rhyth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe Neeman wrote:
| Try overriding the extra-spacing-width property on the ChordName grob
| (the extra-spacing-width property is part of the item-interface, which
| is supported by ChordName).
|
| You could also try overriding the padding property of
On Sun, 2008-08-03 at 07:51 -0500, Shamus wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi all,
>
> I recently upgraded from 2.10.33 to 2.11.52 and noticed that
> SeparatingGroupSpanner is no longer available. I used to use it to keep
> my chord names from running into each other w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Do'h!
Trevor Daniels wrote:
|
| Shamus wrote Sunday, August 03, 2008 1:51 PM
|
|> I recently upgraded from 2.10.33 to 2.11.52 and noticed that
|> SeparatingGroupSpanner is no longer available.
|
| You're right. A quick check of the git history shows
Shamus wrote Sunday, August 03, 2008 1:51 PM
I recently upgraded from 2.10.33 to 2.11.52 and noticed that
SeparatingGroupSpanner is no longer available.
You're right. A quick check of the git history shows
it was replaced with a springs algorithm in 2.11.27.
This should control the spacing a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I recently upgraded from 2.10.33 to 2.11.52 and noticed that
SeparatingGroupSpanner is no longer available. I used to use it to keep
my chord names from running into each other with
\override SeparatingGroupSpanner #'padding = #'2.0
in my C
