Tablature: ignore minimumStretch to/from fret zero

Tablature: ignore minimumStretch to/from fret zero

[Graham Percival, 2012-12-21 07:01:20]

Not really about this patch, but what happened to the plans for running
scripts/auxiliar/fixscm.sh ?  it would be nice to get rid of those tabs.

[marc, 2012-12-21 07:55:18]

Am 21.12.2012 08:01, schrieb graham@percival-music.ca:
> Not really about this patch, but what happened to the plans for running
> scripts/auxiliar/fixscm.sh ?
There were objections about the way emacs does the automatic formatting,
and I am not sure how one can preformat stuff so that the script will fit in
nicely.
Emacs treats the first entry in a list as a function call which does not 
look right.
I asked about that a long while ago, but still don't have a clue.

Regards,

Marc
>   it would be nice to get rid of those tabs.
>
> https://codereview.appspot.com/6944061/
>
> _______________________________________________
> lilypond-devel mailing list
> lilypond-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-devel
>

[Carl, 2012-12-23 14:24:31]

I think the whole issue on this "bug" is incorrect.

The problem we have is that by using restrain open strings, we are telling
lilypond "Don't use open strings".  Then by setting minimum-fret to 0, we are
saying "Do use open strings."  How can we decide what behavior lilypond should
have when the user is inconsistent in their request?

I believe the original code is correct -- if restrain-open-strings is true, a
zero fret should not be allowed.  That's what restrainOpenStrings means.

[dak, 2012-12-23 14:29:29]

On 2012/12/23 14:24:31, Carl wrote:
> I think the whole issue on this "bug" is incorrect.
> 
> The problem we have is that by using restrain open strings, we are telling
> lilypond "Don't use open strings".  Then by setting minimum-fret to 0, we are
> saying "Do use open strings."  How can we decide what behavior lilypond should
> have when the user is inconsistent in their request?
> 
> I believe the original code is correct -- if restrain-open-strings is true, a
> zero fret should not be allowed.  That's what restrainOpenStrings means.

No, it isn't.  Then it would be "forbidOpenStrings".  Please see the original
discussion.  Open strings are merely restrained to the same level as normal
frets are.  In particular, they obey minimumFret