Re: Collision between tuplet bracket and accidental

2014-04-27 Thread James Harkins 

On Friday, 25 April 2014 15:59:16 HKT, Pierre Perol-Schneider wrote:

2014-04-25 7:29 GMT+02:00 James Harkins :
I have a case (attached) where LilyPond doesn't leave enough space for

an accidental.


Try :

\once\override NoteColumn.X-offset = #1


Perfect, thanks!
hjh

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Collision between tuplet bracket and accidental

2014-04-25 Thread Pierre Perol-Schneider 
2014-04-25 7:29 GMT+02:00 James Harkins :

I have a case (attached) where LilyPond doesn't leave enough space for
> an accidental.
>

Try :

%%
\version "2.18.2"
\relative c {
\cadenzaOn
\tuplet 3/2 { f8 [ d' ] e4 d8 [ e ] }
\once\override NoteColumn.X-offset = #1
b''!8 g,4
}




HTH,

~Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Collision between tuplet bracket and accidental

2014-04-24 Thread James Harkins 
I have a case (attached) where LilyPond doesn't leave enough space for
an accidental.

This minimal example *almost* reproduces it. There's not an actual
collision here, but the space is uncomfortably small. If anything
forces narrower spacing (as in my full piece), they will crash into
each other.

\relative c {
\cadenzaOn
\tuplet 3/2 { f8 [ d' ] e4 d8 [ e ] } b''!8 g,4
}

How to fix?

(I do need the forced natural sign b/c there are a lot of Bb's in
other registers elsewhere in this passage.)

hjh
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user