[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Open strings in chords (commit 9203eadca5bcb79415060f8488889706a9c8e62a)
From: |
Marc Hohl |
Subject: |
Open strings in chords (commit 9203eadca5bcb79415060f8488889706a9c8e62a) |
Date: |
Tue, 14 Feb 2012 09:58:45 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.26) Gecko/20120131 Thunderbird/3.1.18 |
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.
Regards,
Marc
- Open strings in chords (commit 9203eadca5bcb79415060f8488889706a9c8e62a),
Marc Hohl <=