Jan-Peter Voigt writes:
> Hello David,
> thank you for this detailed answer!
> Well, I don't agree in doing an awkward thing, using 2.14.
Duration arguments in Lilypond 2.14 are awkward without you being at
fault. There is a reason even a very simple command like \skip had to
be implemented in
Hello David,
thank you for this detailed answer!
Well, I don't agree in doing an awkward thing, using 2.14. But I
probably should not name shortcuts extensions.
When I am working on a collection of pieces to be printed, I am using
current *stable* version. While I'm working on them, I sometimes
Jan-Peter Voigt writes:
> Thanks for that hint! I will keep that in mind for future development.
> I actually use 2.14 for my allday work and create my extensions
> according to that syntax, because I want to be able to produce sheets
> day by day without stumbling over suprisingly upcoming chang
Thanks for that hint! I will keep that in mind for future development.
I actually use 2.14 for my allday work and create my extensions according to
that syntax, because I want to be able to produce sheets day by day without
stumbling over suprisingly upcoming changes.
I know, I should have a deve
Jan-Peter Voigt writes:
> Hi Paolo,
>
> this compiles in 2.14.2 on my machine:
> --snip--
> \version "2.14.2"
>
> myFunction = #(define-music-function (parser location foobar) (ly:duration?)
> (make-music 'SequentialMusic 'elements (list
> (make-music 'EventChord 'elements (list
> (
tion?)
> #{
> a ...how_can_I_use_$foobar_as_duration_??...
> #})
>
> \new Staff \myFunction ...how_can_I_pass_duration_??...
>
>
> -
>
>
> ...which is the right syntax and which version of lilypond could I use?
>
>
> Tha
2011/12/9 Matthew Collett :
>
> On 9/12/2011, at 2:27 pm, David Kastrup wrote:
>
>>> On 8/12/2011, at 10:48 pm, David Kastrup wrote:
>>>
Please, *never*, *never*, *never* send a "courtesy copy" of a public
answer as a private mail when answering on a mailing list unless you
have been
On 9/12/2011, at 2:27 pm, David Kastrup wrote:
>> On 8/12/2011, at 10:48 pm, David Kastrup wrote:
>>
>>> Please, *never*, *never*, *never* send a "courtesy copy" of a public
>>> answer as a private mail when answering on a mailing list unless you
>>> have been _explicitly_ asked to provide such
Matthew Collett writes:
> On 8/12/2011, at 10:48 pm, David Kastrup wrote:
>
>> Please, *never*, *never*, *never* send a "courtesy copy" of a public
>> answer as a private mail when answering on a mailing list unless you
>> have been _explicitly_ asked to provide such a copy.
>>
>> Otherwise, you
On 8/12/2011, at 10:48 pm, David Kastrup wrote:
> Please, *never*, *never*, *never* send a "courtesy copy" of a public
> answer as a private mail when answering on a mailing list unless you
> have been _explicitly_ asked to provide such a copy.
>
> Otherwise, you set up _two_ different communicat
Paolo Prete writes:
> I searched in "extending" manual for 2.15, but I did not find a
> solution for my problem.
Please, *never*, *never*, *never* send a "courtesy copy" of a public
answer as a private mail when answering on a mailing list unless you
have been _explicitly_ asked to provide such
_duration_??...
#})
\new Staff \myFunction ...how_can_I_pass_duration_??...
-
...which is the right syntax and which version of lilypond could I use?
Thanks
--- Gio 8/12/11, David Kastrup ha scritto:
> Da: David Kastrup
> Oggetto: Re: duratio
Paolo Prete writes:
> I need to create a function that
>
> accepts some_pitch and some_duration as arguments and prints the
> following three notes:
>
> 1) some_pitch with some_duration
> 2) some_pitch with some_duration*2
> 3) some_pitch with some_duration*3
>
>
> Should I use ly:duration as typ
Hi,
I need to create a function that
accepts some_pitch and some_duration as arguments and prints the following
three notes:
1) some_pitch with some_duration
2) some_pitch with some_duration*2
3) some_pitch with some_duration*3
Should I use ly:duration as type of the argument two? I can't
14 matches
Mail list logo
