Re: inter-staff distance / page header

This is simply making me nuts. NOTHING I'm trying is having any effect on inter-staff distance at all. Here's the current non-working attempt to increase the distance - \score { \context Staff = "guitar" \with { \consists "Span_arpeggio_engraver" \override VerticalAxisGroup #'next-staff-s

Re: Tempo markings and tempo dynamics

Robin Bannister wrote: Paul Scott wrote: If anyone has an acceptable solution for this I would appreciate hearing about it. Inserting a grace spacer is fairly painless (unless it triggers issue 34). Wow!! How did you figure that out? Thanks, Paul _

Re: Pedal markings at the end of a piece of music

On 1 April 2010 18:01, Andrew Hawryluk wrote: > This looks like a bug to me. My minimal example: > > \version "2.13.16" > { >  \set Staff.pedalSustainStyle = #'text >  c''1\sustainOn > } > > If the pedalSustainStyle is set to #'mixed or #'bracket then the > bracket indicates the sustain up at the

Re: Three systems per page

Hi Fibonacci: > Doesn't work, I still get two systems per page. Works here... did you change your page-breaking algorithm (as indicated on the page I linked)? Cheers, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/m

[ANN] LilyPond engines for TeXShop (and a little more)

Hi, I am pleased to announce that I have eventually updated my TeXShop engines for LilyPond (well, actually, only the engine that runs lilypond-book). The new engine is much more robust and flexible than the previous one (which was called LilyPond-LaTeX). You may download the engines, plus synt

Re: Three systems per page

Doesn't work, I still get two systems per page. 2010/4/3 Kieren MacMillan : > Hi Fibonacci: > >> is it possible [...] to fit three systems per page? > > Have you tried > >  systems-per-page = 3 > > ? > > > H

Re: Three systems per page

Hi Fibonacci: > is it possible [...] to fit three systems per page? Have you tried systems-per-page = 3 ? Hope this helps! Kieren. ___ lilypond-user mailing

Re: inter-staff distance / page header

My mistake. The problem isn't "collisions". It's inter-staff distance, which I'm not finding a way to increase. Can you help me do that? Thanks! Tom On 04/03/2010 12:47 AM, James Bailey wrote: It may not help much, but I've just compiled the file with 2.13.17 and had no collisions to speak of

Three systems per page

Hello. This is (almost) the final version of the score I was recently working on and which I posted on this list a while ago. However, I still have one doubt: is it possible, perhaps by reducing the spacing or the size of the symbols, to fit three systems per page? Even though the systems are even

wanted: title inter-item spacing tips/suggestions

[Lilypond 2.13.17] Hi all, I'm trying to get a good bookTitleMarkup and scoreTItleMarkup setup... Basically, all is well. But it's a pain to set/tweak the inter-item spacing -- for example, between a dedication and title -- because of [at least] the following issues: 1. \override #'(basel

Re: glissando between two notes not joint

Hi Eluze I was thinking of something like this, which works as long as the fingering is directly above the note: { \once \override Glissando #'(bound-details left Y) = #4 \once \override Glissando #'(bound-details right Y) = #5.3 g''2-1 \glissando <<{s} \\ {e''}>> b''-1 } It might need a bit

Re: Major version: LilyPond 2.14.0 released!

1. I will not respond to your insults 2. Of course this was about stable releases. 3. It is called "Release early, release often, and listen to your customers" and its the total opposite of what you have said right from the very beginning of this statments appearing in The Cathedral and the Bazaa

Re: glissando between two notes not joint

Trevor Daniels wrote: > > > There's a fair bit on fiddling with glissando lines in Section > 5.4.6 of the Notation Reference under Using the line spanner > interface. If you've not seen this maybe it will help. > thanks Trevor! i had read it before and reread it now - and still i feel a bit

Re: inter-staff distance / page header

It may not help much, but I've just compiled the file with 2.13.17 and had no collisions to speak of. For printing header information on every page, see section 3 of the notation reference. I even think that odd/even page header may work in the development version, although I'm not sure.