2014-02-26 10:37 GMT+01:00 Pierre Perol-Schneider <
pierre.schneider.pa...@gmail.com>:
> 2014-02-26 9:52 GMT+01:00 Federico Bruni <fedel...@gmail.com>:
>
> A snippet which says that you can use Staff and TabStaff together doesn't
>> make sense.
>>
> I don't see what you mean. If that make sense or not is not the aim of
> this snippet.
>
My assumption was that the LSR should not contain basic snippets, such as
this one. But I'm probably wrong, because I've just found another simple
one about hammer-on and pull-off.
Anyway, I would change the description, because what is interesting about
this snippet is that Lilypond supports chord slides by default (it didn't
some time ago), not that glissando can appear in Staff and TabStaff. Of
course the description should be improved, I'm tired now and can't find
better sentences:
\header {
texidoc = "Chord slides are supported. A glissando between two chords
draws a line between each matching note of each chord. It works in both
Staff and TabStaff. The slide in the TabStaff can be omitted."
}
myMusic = \relative c' {
<c e g>1 \glissando <f a c>
\override TabStaff.Glissando.stencil = ##f
<c e g>1 \glissando <f a c>
}
\score {
<<
\new Staff {
\clef "treble_8"
\myMusic
}
\new TabStaff {
\myMusic
}
>>
}
If you use slurs (aka hammer-on/pull-off in tablature) or glissando (aka
>> slides in tablature), they will appear on Staff and TabStaff by default;
>> this is what any user would expect.
>>
> I would not.
> If ever I had to use both Staff and TabStaff here's how I would write a
> glissando :
>
>
This is a matter of tastes. I don't like it at all, but this override may
be included in the snippet to show that the glissando can be removed (see
above).
> myMusic = \relative c' {
>
> <c e g>1 \glissando <f a c>
>
> }
>
> \score {
>
> <<
>
> \new Staff {
>
> \clef "treble_8"
>
> \myMusic
>
> }
>
> \new TabStaff \with { \override Glissando.style = #'none } {
>
> \myMusic
>
> }
>
> >>
>
> }
>
>
>
>
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
