lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: restrainOpenStrings


From: Marc Hohl
Subject: Re: restrainOpenStrings
Date: Sun, 13 Sep 2015 14:21:37 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0

Am 13.09.2015 um 14:07 schrieb BB:
I read the manual. But please answer the question WHY should lilypond
 statements not do what the statement text straight implies?

IIRC, we discussed quite a lot about the new restrainOpenStrings
functionality and how to name this new property. There were some
proposals, and restrain... was chosen as the best fit.

It may not be the perfect choice, but then again, the manual explains in
more detail what the property is used for.

\set
TabStaff.allowOpenStringsInTheCalculationOfPossibleFretPositionsEvenIfMinimumFretIsSet
= ##t

would be quite a bit of stuff to type, but completely understandable
without the manual ;-)

I agree that the minimumFret/restrainOpenStrings way is not fully
convincing to me either, but I can't think of anything better. There are
cases where you need strings fretted above a minimum fret with or
without empty strings, so Lilypond should handle both.

Just my 2ct,

Marc

Obviously you have not read my postings, as I have 1. pointed out
that I can handle the "contradictories" 2. quotation: "So simply let
me annul my question."

Cheers!

On 13.09.2015 13:56, Phil Holmes wrote:
I think the issue here is that David K has read the documentation
(the NR, section 2.4.1) but BB probably hasn't, and is trying to
guess what a lilypond command does from its name.  This is always
likely to be problematical.

-- Phil Holmes

----- Original Message ----- *From:* BB
<mailto:address@hidden> *To:* David Kastrup
<mailto:address@hidden> *Cc:* lilypond-user Mailinglist
<mailto:address@hidden> *Sent:* Sunday, September 13, 2015
12:25 PM *Subject:* Re: restrainOpenStrings

I try an explanation again:

If a user says \set TabStaff.minimumFret = #5 I would expect that
LP obeys and just uses no frets closer to the nut tha five. As you
wrote, LP is unobedient and uses open strings against that
imperative  TabStaff.minimumFret = #5 ? On the other extreme if one
sets \set TabStaff.minimumFret = #5 in my short code example LP is
fussy and omits the d that would simply be feasible with the 3rd
fret. Why does LP use open strings (fret 0 = nut) lower than 5th
fret, but is not flexible enough to use 3rd string for d in my
example - certainly with a warning or simple notice? (Indeed there
is a warning that no string is defined for that note d ...). I
think, a positive warning in the sense " I cannot accomplish your
wish for d with minimum Fret = #5. I warn/inform you, that I
will/can do it with the 3rd fret. So please react if you do not
like that". So I can react and change something or I may agree.
Beside: There is simply no alternative to the 3rd fret in my
example!

The same is true for \set TabStaff.restrainOpenStrings = ##t For me
the text implies, that LP must not use open strings. In my
interpretation minimumFret has nothing to do with \set
TabStaff.minimumFret = #5 straight. I would expect, that LP will
obey and fullfill my wish "no open strings". Whereas "restrain" is
not a strong categorically prohibition, but is a bit softer - maybe
in the meaning "whenever possible". (A problem with this only
happens with the "last" string, i. e. 6th string on guitar or the
equivalent for other stringed instruments.)

That soft "whenever possible" I would like for \set
TabStaff.minimumFret as well.

Again, let me point out that I know the "contradictories"
("contradictories" in my view/logic) and therefore I can handle
it.

Thanks.

On 13.09.2015 12:44, David Kastrup wrote:
BB<address@hidden>  writes:

I just pointed out - I can live with this contradictories. So
simply let me annul my question.
LilyPond's behavior and documentation is not supposed to be
contradictory.  So please point out any actual contradictions in
the documentation or LilyPond's behavior so that they may be
fixed.


------------------------------------------------------------------------


_______________________________________________
lilypond-user mailing list address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user




_______________________________________________ lilypond-user mailing
list address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user





reply via email to

[Prev in Thread] Current Thread [Next in Thread]