Actually, I wouldn't really classify this as a bug at all. The same
thing happens in many other situations. For example, you get an extra
Staff in the following situation:
\new StaffGroup{
\set Staff.instrumentName = "Stray stave"
<<
\new Staff{ c'' }
\new Staff { e'' }
>>
}
not to mention situations like:
\new StaffGroup{
\key g \major
<<
\new Staff{ c'' }
\new Staff { e'' }
>>
}
which have caused a number of questions on the mailing list over the years.
/Mats
Quoting Mats Bengtsson <[EMAIL PROTECTED]>:
A simple workaround would be to do the property setting higher up
in the context hierarchy, for example at the Score level, which means
that they will be inherited to all TabStaff contexts (if there are any):
\set Score.minimumFret = #3
/Mats
Quoting Graham Percival <[EMAIL PROTECTED]>:
Thanks, entered as
http://code.google.com/p/lilypond/issues/detail?id=387
Cheers,
- Graham
hernan gonzalez wrote:
I have a score that uses TabStaff; the voices include here and there
some tab-related commands (eg. \set TabStaff.minimumFret ). If I
choose to not output the TabStaff (commenting out that staff from the
main score definition), lilypond get badly confused with the
tabstaff-related commands it finds.
Test case:
With Lilypond 2.10.23 (Win)
%%%%%%%%%%%%%%%%%%%%%
\version "2.10.1"
frag = {
e'1 \set TabStaff.minimumFret = #3
g'1 \set TabStaff.minimumFret = #0
e'1
}
\score {
<<
<< \new Staff { \frag } >>
% << \new TabStaff { \frag } >> % uncommenting this line it works ok.
>>
}
%%%%%%%%%%%%%%%%%%%%%
Cheers
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
_______________________________________________
bug-lilypond mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-lilypond
