Not really a Lilypond comment, but we no longer sing “in all thy sons command”
- the words are now “in all of us command”.
https://www.canada.ca/en/canadian-heritage/services/anthems-canada.html#a11
Thanks,
Carolyn
P.s. I think this might be my first post, and I don’t really understand how to
Hello Vlad,
Also checkout this thread:
https://lists.gnu.org/archive/html/lilypond-user/2023-02/msg00035.html
If you want a real alias (that is a second binding to the same function) you
can do
#(define acc acciaccatura)
This will create another binding to the same object, which means you do
Leo Correia de Verdier writes:
>> 27 juni 2023 kl. 21:57 skrev Volodymyr Prokopyuk
>> :
>>
>> I'd like to define a shorter alias to a parametrized command. My two
>> specific use cases are
>> • Define \acc { c='8 d e } to be translated into \acciaccatura
>> { c='8 d e }
>> • Define \af
Hi Leo,
The \etc is exactly what I was looking for!
Thank you so much,
Vlad
On Tue, Jun 27, 2023 at 10:32 PM Leo Correia de Verdier <
leo.correia.de.verd...@gmail.com> wrote:
> Hi Volodymyr!
>
> You can write:
> %
> acc = \acciaccatura \etc
> af = \after \etc
> %
>
> \se
On Tue, Jun 27, 2023 at 12:19 PM Valentin Petzel wrote:
> Hello Knute,
>
> so you are using books to allow specification of the midi filename. This
> is
> probably a fine usecase, but it still seems like a bit of an abuse of the
> book
> mechanic to me. Rather I’d adapt the midi output name logic
Hi Volodymyr!
You can write:
%
acc = \acciaccatura \etc
af = \after \etc
%
\set in lilypond is something completely else.
HTH
/Leo
> 27 juni 2023 kl. 21:57 skrev Volodymyr Prokopyuk
> :
>
> Hello,
>
> I'd like to define a shorter alias to a parametrized command. My
Hello,
I'd like to define a shorter alias to a parametrized command. My two
specific use cases are
- Define \acc { c='8 d e } to be translated into \acciaccatura { c='8 d
e }
- Define \af 4. to be translated into \after 4.\!
I've tried the \set command, but it seems that the \set comman
Hello Knute,
so you are using books to allow specification of the midi filename. This is
probably a fine usecase, but it still seems like a bit of an abuse of the book
mechanic to me. Rather I’d adapt the midi output name logic itself.
This code adapts the internal function responsible for writ
On Tue, Jun 27, 2023 at 2:35 AM Valentin Petzel wrote:
> Hello Knute,
>
> I do not think this behaviour is particularly weird, rather the input is
> weird.
>
Thanks for your replies. Here is my slightly convoluted use-case. Maybe
there's a better way to do it.
I am engraving collections of pi
Hello Knute,
I do not think this behaviour is particularly weird, rather the input is
weird.
Using \book is telling Lilypond you want to generate a new PDF. So there
should be no reason to enclose scores that only produce MIDI into a \book
clause. And if you do I think it should not be unexpe
Le lundi 26 juin 2023 à 16:39 -0700, Knute Snortum a écrit :
> I've run into some odd behavior in LilyPond. If your PDF-only is a score but
> your MIDI-only is a separate book, the PDF file gets "-1" appended to the
> file name. So for instance, with this code:
>
> File name: test.ly
>
> %%%
>
11 matches
Mail list logo
