Stewart Holmes wrote:
Might I recommend that the documentation be changed from:
The lengths to shorten a text-spanner on both sides, for example a
pedal bracket
to something like:
The lengths to shorten a text-spanner on both sides, for example a
pedal bracket, negative values lengthe
Sorry, the stems still collide. Well, voice 1 flag
collides with voice 3 stem.
Thanks
--- Rick Hogg <[EMAIL PROTECTED]> wrote:
> I asked this question last month and got an answer
> that almost helped, but is it possible to use
> X-offset
> in the <<\\>> environment? I need both voices to be
>
I asked this question last month and got an answer
that almost helped, but is it possible to use X-offset
in the <<\\>> environment? I need both voices to be
stem-up, so I created a blank second voice, using only
first and third for notation, but the flags still
collide (that is, << \\ \\ >>).
Th
Hello,
I'm copying a score (same one I've been working on for
months now, trying to make it perfect, waiting for
technology to catch up, etc, etc.) and one of the
things in this score is dynamic markings above or
below the bar lines. It helps spacing in some
aspects. So I'm wondering, how do I go
Howdy,
I'm using a TextSpanner over a linebreak. I've
modified it using:
\once \override TextSpanner #'shorten-pair = #'(-7
. -8)
This causes there to be a gap in the textspanner at
the start of the next line.
This gap disappears if I remove the shorten-pair
modification... but
Has this:
\override RemoveEmptyVerticalGroup #'remove-first = ##t
been depricated in 2.8.5? It's not in the new manual.
If so, then how do I get rid of the large amount of vertical whitespace
between the header and the first system? My page only has 3 lines and I'd
like them all to be togethe
Hello,
I've been away from LP for a few months, so I decided to upgrade to 2.8.5.
I added 9x12 inch paper to paper.scm, however LP is still not recognizing
all the real estate available to it. Also when I go to print and tell Adobe
the paper is 9x12, Adobe still thinks the document size is 8.5x
When I try the following:
\version "2.9.11"
erga = {\once \override NoteHead #'style = #'diamond a}
para = {< \parenthesize a>}
{
a ~ \erga ~ \erga
a( \erga) \erga( a)
a ~ \para ~ \para
a( \para) \para( a)
}
I get:
GNU LilyPond 2.9.11
Processing `greg.ly'
Parsing...
greg.ly:7:10: error: synt
I'm trying to use 2.9.1 for the first time because of various new features and seem to have immediately run into a bug. The attached file should produce landscape output, but it doesn't. It doesn't matter if I put the line at the top of the file or in the \paper section.Any thoughts for a workaroun
