Thanks Keith, that worked. Should I copy this to the bug reporting list?
Knute Snortum
(via Gmail)
On Sat, Jul 18, 2015 at 6:19 PM, Keith OHara k-ohara5...@oco.net wrote:
Knute Snortum ksnortum at gmail.com writes:
I thought the answer would be to force-hshift the lower note but it
I see that you submitted patch. Thank you.
Knute Snortum
(via Gmail)
On Sun, Jul 19, 2015 at 6:13 AM, Knute Snortum ksnor...@gmail.com wrote:
Thanks Keith, that worked. Should I copy this to the bug reporting list?
Knute Snortum
(via Gmail)
On Sat, Jul 18, 2015 at 6:19 PM, Keith OHara
Keith OHara k-ohara5a5a at oco.net writes:
Knute Snortum ksnortum at gmail.com writes:
I thought the answer would be to force-hshift the lower note but it
doesn't seem to move.
We should file a bug-report, to at least left-align before applying
explicit force-hshifts
I submitted a
I have a situation where I'm creating cross-staff chords. All is well
until the melody note is the same as the top chord note. LilyPond
(correctly) shifts the chord to the right, but now the note in the lower
staff doesn't create a cross-staff chord. I thought the answer would be to
Knute Snortum ksnortum at gmail.com writes:
I thought the answer would be to force-hshift the lower note but it
doesn't seem to move.
Annoyingly, LilyPond left-aligns the groups of clashing chords between
different staves. The code history says the reason was to left-align
\transpose
