t:
http://lilypond.1069038.n5.nabble.com/composing-Scheme-identifiers-tp160030p160056.html
Sent from the User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Paul Morris writes:
> Simon Albrecht-2 wrote
>> scoreSetup =
>> #(define-music-function
>> (parser location letter)
>> (string?)
>> #{
>> \score {
>> \new Staff = "bassus" \with { instrumentName = "bassus" }
>> % this is supposed to give the same result as @code{\bassK} for example…
>> #(string->
whether I'm
just doing something wrong? Here's a simple example that produces that error
for me:
\version "2.18.0"
scoreSetup =
#(define-music-function
(parser location letter)
(string?)
#{
\score {
{ a b c d }
}
#})
\scoreSetup "K"
--
View this mess
Simon Albrecht writes:
> Hello,
>
> I currently work on a mass setting by Palestrina. The music is stored
> in variables sopranoK, altoK, tenorK, bassK, sopranoVerseK, …,
> sopranoG, altoG, etc. etc. for the different parts and movements. Now
> since I need a separate \score block for each moveme
Hello,
I currently work on a mass setting by Palestrina. The music is stored in
variables sopranoK, altoK, tenorK, bassK, sopranoVerseK, …, sopranoG,
altoG, etc. etc. for the different parts and movements. Now since I need
a separate \score block for each movement, but these score blocks will
hanks,
David
--
View this message in context:
http://www.nabble.com/writing-identifiers-tf3803517.html#a10765855
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu
It's not that tricky. At first sight, you may even think that there is
no need for
a music function at all, but as you probably have found out yourself, an
identifier like
myGrace = { \once \override Slur #'transparent = ##t \appoggiatura }
does not work. The reason is that \appoggiatura itself i
me.
>
Thanks, Graham. I had followed links as far as 5.6, which didn't help. Ch.
12, "Interfaces for programmers", is serious stuff, as the title says. I
might work on it when I have more time for study.
David
--
View this message in context:
http://www.nabble.com/writing-identi
madhg wrote:
But after rereading this section of the doc, I still don't know what should
go after "parser location" or replace "(number?)". Is that information
somewhere accessible (bearing in mind that the Learning Manual is intended
for non-experts)? I feel rather at sea here.
Follow the l
ion padding) (number?)
#{
\once \override TextScript #'padding = #$padding
#})
from the "Learning Manual" section of the documentation:
http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Saving-typing-with-identifiers-and-functions
But after rereadi
That's a straightforward application of section "12.1.2 Simple
substitution functions":
\version "2.10.0"
trip = #(define-music-function (parser location music) (ly:music?)
#{ \times 2/3 $music #})
/Mats
Anders Nelstrom wrote:
Is it possible to create an identifier to save typing when triple
Is it possible to create an identifier to save typing when triplets
are required? For example, instead of typing:
\times 2/3 { c8 e g } \times 2/3 { c g e } c
it would be great to use:
\trip { c8 e g } \trip { c g e } c4
or such like.
I appreciate that the \times command is flexible, and I
Kamal wrote:
How do you attach a duration (or other notation) to an identifier?
You can't attach durations to identifiers. You need to write a music
function to do this; see "interfaces for programmers" in the 2.9 manual.
C
s capability for my chord library, so I will be interested
in an answer as well.
--
View this message in context:
http://www.nabble.com/Identifiers-tf2596524.html#a7246499
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
How do you attach a duration (or other notation) to an identifier?
Example:
I have:
8 16[ ]
I want to use "" as an identifier so I tried the following but
it didn't work:
var = { < a c e> }
\score {
{ \var \var16[ \var16] }
}
I am using lilypond 2.8.6
___
ll keep digging & experimenting to satifsy my curiousity.
I did discover that identifiers needed to be alpha only in the documentation although I didn't look until after I tried: 'CMaj7 = { }' . That has everything to do with my learning style and nothing to do with the doc
Quoting Mike Amundsen <[EMAIL PROTECTED]>:
While creating identifiers for fret diagrams I found the identifiers
can be alpha only. I've searched the archives to see if there was a
discussion that described the reasons for that constraint. I'd guess
it's for reasons
While creating identifiers for fret diagrams I found the identifiers
can be alpha only. I've searched the archives to see if there was a
discussion that described the reasons for that constraint. I'd guess
it's for reasons of simplicity and/or something to do with the
interopera
18 matches
Mail list logo
