Il 01/03/2013 20:12, m...@mikesolomon.org ha scritto:
>
>2.: Would it be possible to at least inform the user about the
>suppressed grob by printing a warning in the compilation buffer?
>
No. Please report this problem to bug-lilyp...@gnu.org.
well, the same input compiled in 2.17.13 print
Hi Orm,
No noise, this is a bug. Or at least a known issue for in the doc.
Greetings, Ed
Op 1 mrt. 2013 22:00 schreef "Orm Finnendahl" <
o.finnend...@inm.mh-freiburg.de> het volgende:
> Am Freitag, den 01. März 2013 um 19:20:25 Uhr (-) schrieb Phil Holmes:
> >
> > Checkout glissando on:
> >
Am Freitag, den 01. März 2013 um 19:20:25 Uhr (-) schrieb Phil Holmes:
>
> Checkout glissando on:
>
> http://lilypond.org/doc/v2.15/Documentation/notation/spanners
Thanks and sorry for the noise. I should have found that myself...
___
lilypond-use
- Original Message -
From: "Orm Finnendahl"
To:
Sent: Friday, March 01, 2013 7:07 PM
Subject: spanners not showing up
Hi,
sorry, if that has been discussed before.
In the following example, there are two glissandos with an end arrow
between each f and g, but only the
On 1 mars 2013, at 20:07, Orm Finnendahl
wrote:
> My questions:
>
> 1.: Is there a direct way to enforce lilypond to always print those
>signs and adjust its spacing accordingly (I'm aware that I could
>use a hidden second voice with eigth notes to enforce more
>horizontal space, b
Hi,
sorry, if that has been discussed before.
In the following example, there are two glissandos with an end arrow
between each f and g, but only the second one is showing up. This is
obviously due to lilypond's spacing decisions, not leaving enough
space for the first gliss sign (see attached p
