[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: cresc. whitespace padding
From: |
Thomas Morley |
Subject: |
Re: cresc. whitespace padding |
Date: |
Sat, 12 Oct 2013 17:18:40 +0200 |
Hi Ed,
2013/10/12 EdBeesley <address@hidden>:
> David Kastrup wrote
>> EdBeesley <
>
>> edplaysdrums@
>
>> > writes:
>>
>>> Damnit David, I'm a musician not a programmer!
That's true for me, too!
:)
>>> In all seriousness
>>> though I always do my best to figure out the answer myself via the
>>> documentation.
>>
>> Good. Then you can tell us where the documentation falls short. To be
>> exact, I reacted to your statement:
>>
>>> Now when you say this could be easily turned into a
>>> music-function... could we assume for a second that I'm totally dumb
>>> and have no idea how to do this?
>>
>> And my answer to that was: "That's where LilyPond's documentation could
>> come in handy..."
>>
>> You are in obvious disagreement:
>>
>>> I know I've asked a far few questions over the past week but believe
>>> me there are a lot that I've not posted because I've spent hours
>>> reading through the manual and snippets. I'm very conscious about only
>>> using the mailing list as a last resort instead of a short-cut to
>>> problems I could solve myself, and I'm sorry if I've not given that
>>> impression!
>>
>> So let's see where 5 minutes (we are not talking hours here) with the
>> manual will take us.
>>
>> I first look up "music function" in the Notation Reference's index and
>> find
>> <URL:http://lilypond.org/doc/v2.16/Documentation/notation/using-music-functions#index-Music-functions>
>>
>> Going straight to the second section "substitution function examples"
>> (assuming that I am dumb and the first section "Substitution function
>> syntax" scares me) from there, the very first example illustrates how to
>> wrap a code passage taking numerical values as arguments into a music
>> function.
>>
>> So obviously you got stuck elsewhere in your attempt to solve that
>> problem yourself in the hour between the time the non-parametric
>> solution was posted and you asked for getting a solution using a
>> function.
>>
>> Where? How can we improve the documentation so that anybody faced with
>> the same task, namely wrapping some code with parameters into a music
>> function, is not still floored after having been given the right
>> keywords?
>>
>> Could we assume for a second that I'm totally clueless and have no idea
>> how to do this?
>>
>> --
>> David Kastrup
>
>
> I'm sensing a certain level of hostility here which I don't think is
> completely deserved....
I'm _sure_ no hostility was intended.
If David is abrupt sometimes ...
ignore it.
And if he (or me or someone else) is in a really bad mood ...
ignore it.
Read and try to understand what is written, I guarantee you will gain
much profit !!
Would be nice if you could help us to improve the documentation.
So please take David serious (and _not_ offending) and try to reply
his question.
Please understand that developers and longtime users are very familiar
with the docs.
Perhaps you can imagine that this might be a _disadvantage_ sometimes.
Best,
Harm
- Re: cresc. whitespace padding, (continued)
- Re: cresc. whitespace padding, Thomas Morley, 2013/10/11
- Re: cresc. whitespace padding, Thomas Morley, 2013/10/11
- Re: cresc. whitespace padding, EdBeesley, 2013/10/12
- Re: cresc. whitespace padding, David Kastrup, 2013/10/12
- Re: cresc. whitespace padding, EdBeesley, 2013/10/12
- Re: cresc. whitespace padding, Phil Holmes, 2013/10/12
- Re: cresc. whitespace padding, EdBeesley, 2013/10/12
- Re: cresc. whitespace padding, David Kastrup, 2013/10/12
- Re: cresc. whitespace padding, EdBeesley, 2013/10/12
- Re: cresc. whitespace padding, David Kastrup, 2013/10/12
- Re: cresc. whitespace padding,
Thomas Morley <=
- Re: cresc. whitespace padding, David Kastrup, 2013/10/12
Re: cresc. whitespace padding, Colin Campbell, 2013/10/11