Re: Open strings in chords (commit 9203eadca5bcb79415060f8488889706a9c8e62a)

[Marc Hohl]

Am 14.02.2012 09:58, schrieb Marc Hohl:
> Hello all,
>
> while typesetting a piece for two guitars, I stumbled across
> the influence of the commit mentioned above.
>
> Before that,
>
> something like
>
> \set minimumFret = #2
> dis'8 ( e' dis ) h fis2
>
> worked smoothly out of the box, now I have to tell
> lilypond explicitly which string to use when I want to
> avoid open strings.
>
> \set minimumFret = #2
> dis'8 ( e\2 dis ) h\3 fis2 |
>
> I dont want to make lilypond input even more complicated,
> but what about a separate switch, something like
>
> \tabOpenStringsOn \tabOpenStringsOff ?
>
> These commands control whether open strings
> are taken into account or not.
>
> Perhaps I have some time to create a patch myself
> within the next week or so.
The rehearsal this evening was canceled, so here you are.

Regards,

Marc
> Regards,
> Marc
>
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-devel

0001-Handling-of-open-strings-in-tablature.patch.txt
Description: Text document