2014-02-22 10:49 GMT+01:00 Federico Bruni <fedel...@gmail.com>:

> I'm not sure if it's a bug. But the duplication can be a bit annoying when
> you work on a big file containing many errors (for example, because it's
> the result of an export which doesn't produce good lilypond code). I know I
> can skip the duplicate,  but a cleaner log would be nice.


Well, of course the best workaround should be: comment one of the two
staffs, fix the errors and then uncomment.
While this works fine in the minimal example I posted before, I cannot make
it work in the real file I'm working on at the moment. The log message is
duplicated and I cannot figure out why. This is the score block commented:

\score {
   % \new StaffGroup <<
      \new Staff \with {
        midiInstrument = "acoustic guitar (steel)"
        fingeringOrientations = #'(left)
      } { \clef "treble_8" << \voiceOne \upper \\ \voiceTwo \lower >> }
     %{ \new TabStaff \with {
        stringTunings = #guitar-tuning
        \override TabNoteHead.font-name = #"Nimbus Sans L Bold"
        \remove "Staff_performer"
      } <<
        \new TabVoice { \clef "moderntab" \voiceOne \upper }
        \new TabVoice { \clef "moderntab" \voiceTwo \lower }
      >>%}
    %>>
    \layout { indent = 0  }
    \midi {
      \tempo 4 = 100
    }
  }
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to