Re: Issue 2348 in lilypond: Patch: Handling of open strings in tablature

[lilypond]

Comment #9 on issue 2348 by address@hidden: Patch: Handling of open strings  
in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348

Ok, I am officially an idiot.  It turns out that my assertion that  
properties were usually defaulting to #f was totally wonkers if you take a  
look at ly/engraver-init.ly.  Don't ask me what I have been thinking or  
drinking.  For example, we have

%% tablature:
  stringOneTopmost = ##t
  highStringOne = ##t

So for the sake of people not having to head-scratch more than necessary, I  
do a full reverse turn and propose that the property is  
called "includeOpenStrings" or "allowOpenStrings" or "admitOpenStrings" and  
has the reverse logic.  Because in this manner, the special action taken  
for open strings, even though the default, corresponds to #t.  And all  
attempts to come up with a nice naming for the reverse logic are really  
strained.

Sorry for having caused this rather painful endrun by blubbering something  
without verification that I somehow thought I remembered to be the case.