Am 01.09.2012 um 22:22 schrieb David Kastrup:
> pls <p.l.schm...@gmx.de> writes:
>
>> There must have been a change in default with regards to the
>> visibility of string numbers between 2.15.20 and the current
>> version. In 2.15.20 it was still possible to add string numbers to
>> notes (e.g. c'4\4) without them showing up in the score.
>
> But they showed up when writing <c'4\4>, so this was more a convenient
> bug than anything else.
>
>> This was very handy in order to automatically specify the appropriate
>> fret on the right string in tablature. One could decide whether to
>> output individual string numbers via <c'\4>4 or not to engrave them
>> via c'4\4.
>
> And what would you do when _wanting_ a chord with more than a single
> note but no string numbers?
I used to use <c e g>\5\4\3. Quite a convenient bug, indeed! ;)
>
>> Now it seems that this behavior can only be achieved by constantly
>> overriding the string number stencil...
>
> Not that bad:
>
> n=#(define-event-function (parser location e) (ly:event?)
> #{ \tweak #'stencil ##f $e #})
>
> { c'\4 c'\n\4 }
>
> --
> David Kastrup
>
>
> _______________________________________________
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-devel
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
