2017-10-11 21:56 GMT+02:00 Ophir Lifshitz <hangfromthefl...@gmail.com>:
> Hi Malte,
>
> Thank you very much for that cleaner workaround. Now I am mainly interested
> in making sure that this bug gets properly filed so that it can eventually
> be fixed.
>
> Ophir

Hi Ophir,

this has to do with how LilyPond deals with loose columns.
(Spacers don't cause a NoteColumn)

Look at the example below:

  \new PianoStaff <<
      \new Staff = "RH" {
          a'8 a' a' a'
          a'
          \change Staff = "LH"
          \clef treble
          ais'
          \change Staff = "RH"
          a'4

      }
      \new Staff = "LH" {
          c'8 s4.
          \mark \default
          \clef bass
          c'8
          s8
          \mark \default
          \clef bass
          c4
      }
  >>

At "A" we don't want additional spacing as opposed to "B"
Though, this is user-settable, albeit not documented.

  \new PianoStaff <<
      \new Staff = "RH" {
          a'8 a' a' a'
          a'
          \change Staff = "LH"
          \clef treble
          ais'
          \change Staff = "RH"
          a'4

      }
      \new Staff = "LH" {
          c'8 s4.
          \mark \default
          \clef bass
          c'8
          \override Score.NonMusicalPaperColumn.allow-loose-spacing = ##f
          s8
          \revert Score.NonMusicalPaperColumn.allow-loose-spacing
          \mark \default
          \clef bass
          c4
      }
  >>

So we have at least a documentation-issue, imho.

Cheers,
  Harm

_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to