Re: Open strings in chords (commit 9203eadca5bcb79415060f8488889706a9c8e62a)

[David Kastrup]

Marc Hohl <address@hidden> writes:

> Am 14.02.2012 21:18, schrieb Marc Hohl:
>> Am 14.02.2012 21:01, schrieb David Kastrup:
>>> Marc Hohl<address@hidden>  writes:
>>>
>>>> Am 14.02.2012 09:58, schrieb Marc Hohl:
>>>> +    \set TabStaff.handleOpenStrings = #'forbid
>>>> +<  g, d>1
>>>> +  }
>>>> +}
>>>> diff --git a/ly/engraver-init.ly b/ly/engraver-init.ly
>>>> index 6335ab6..11181d3 100644
>>>> --- a/ly/engraver-init.ly
>>>> +++ b/ly/engraver-init.ly
>>>> @@ -46,6 +46,7 @@
>>>>
>>>>     predefinedDiagramTable = #default-fret-table
>>>>     handleNegativeFrets = #'recalculate
>>>> +  handleOpenStrings = #'allow
>>> Symbols 'allow and 'forbid are not a typical interface.  You would
>>> rather use a boolean here.
>> Yes, you are right, I changed it accordingly.
> Um, does
>
> allowOpenStrings = ##t
>
> sound better than
>
> handleOpenStrings = ##t

Sure.  Capo/bottleneck do not play into this?  I don't think we have any
options with a default of ##t though, so it might make more sense to
have ignoreOpenStrings (better suggestions?).

-- 
David Kastrup