Re: Adding StringNumber 0 in TabStaff crashes

[Thomas Morley]

2012/11/23 David Kastrup <address@hidden>:
> Federico Bruni <address@hidden> writes:
>
>> 2012/11/23 Pierre Perol-Schneider <address@hidden>
>>
>>     ?? Confusing string number 0 ??
>>     Humm ... not sure...
>>     If string number is wanted Thomas should write :
>>
>>     \version "2.17.6"
>>     \new TabStaff { d\4 }
>>
>>     Don't you think ?
>>
>> The bug was found because I was updating a Mutopia file where the
>> typesetter wanted to show string number 0 in a bar. Probably because
>> that bar contains a G note played on 4th string and on 3rd string: I
>> think that he wanted to stress this alternation.
>
> Sounds like a confusion of string number and fret number to me.
>
> --
> David Kastrup
>
> _______________________________________________
> bug-lilypond mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/bug-lilypond

In printed editions of scores for the guitar I often saw StringNumber
0 indicating an open string.

In LilyPond
\new Staff { d\0 }
is valid input, printing a circle around a StringNumber with the value
of 0, equal to the appearance of said editions.

LilyPond should not crash with it while using TabStaff, otherwise

m = { d\0 }
<<
\new Staff \m
\new TabStaff \m
>>

wouldn't be possible.

Well, one could argue, whether it makes sense to indicate an open
string with StringNumber 0, instead of using FingerNumber 0 or the
\open-articulation.
But I think that's a different question.

Again, the main point is, that LilyPond's TabStaff should not crash
with an valid input for Staff.


Cheers,
  Harm