[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Fwd: Possible bug with minimumFret
From: |
Colin Hall |
Subject: |
Re: Fwd: Possible bug with minimumFret |
Date: |
Fri, 4 Jan 2013 14:10:58 +0000 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Fri, Jan 04, 2013 at 12:34:08PM +0100, Federico Bruni wrote:
> 2013/1/4 Eluze <address@hidden>
>
> > Yevgeny Lezhnin wrote
> > > When I trying to change TabStaff.minimumFret to 3 there is 0 fret for
> > > all notes, that can be on 0 fret.
> >
> > see the NR:
> >
> > http://www.lilypond.org/doc/v2.17/Documentation/notation/common-notation-for-fretted-strings
> >
> > Even when minimumFret is set, open strings are used whenever possible. This
> > behaviour can be changed by setting restrainOpenStrings to #t
Thanks for directing the OP to the docs, Eluze.
> I've been wondering for a while why restrainOpenStrings is set to #f by
> default.
> Most of the times users expect not to have open strings when they set
> minimumFret. IMO open strings should be restrained by default when
> minimumFret is set.
That makes sense to me, Federico.
> I've skimmed through issue 2348 but I couldn't find any discussion on this
> matter.
> What do you think about it?
Please correct me if I am wrong, but as far as I can see there is no
actual bug here.
If you would like to start a discussion about a design change then I
think either lilypond-user or lilypond-dev are the correct place to do
that.
Once you have a concise definition for the design change then yes,
please post it here and we'll create a tracker for it.
Cheers,
Colin.
--
Colin Hall