Re: Change the duration of a chord defined as a variable

paolo prete writes: > 2018-03-06 13:15 GMT+01:00 David Kastrup : > >> >> Have you even tried what happens with articulations? >> > > Yes, I tried with: > > > %%% > chord = \mp > > newChord = > { > <$@(ly:music-property chord 'elements)

Re: Change the duration of a chord defined as a variable

Hi David, in the snippet below, is it possible to set a new duration of \newChord in the variable definition? Thanks chord = <f' a'>4 newChord = #(make-event-chord (ly:music-property chord 'elements)) { \newChord } 2018-03-06 12:14 GMT+01:00 David Kastrup <d...@gnu.org>: &

Re: Change the duration of a chord defined as a variable

2018-03-06 13:15 GMT+01:00 David Kastrup : > > Have you even tried what happens with articulations? > Yes, I tried with: %%% chord = \mp newChord = { <$@(ly:music-property chord 'elements) >8 $@(ly:music-property chord 'articulations ) } #(display

Re: Change the duration of a chord defined as a variable

paolo prete <paoloprete...@gmail.com> writes: >> paolo prete <paoloprete...@gmail.com> writes: >> >> > Hi David, >> > in the snippet below, is it possible to set a new duration of \newChord in >> > the variable definition? >> > Thanks &

Re: Change the duration of a chord defined as a variable

paolo prete <paoloprete...@gmail.com> writes: > Hi David, > in the snippet below, is it possible to set a new duration of \newChord in > the variable definition? > Thanks > > chord = <f' a'>4 > newChord = #(make-event-chord (ly:music-property chord 'elemen

Re: Change the duration of a chord defined as a variable

Great. Is there also way to add the articulations of chord to newChord ? 2018-03-06 12:46 GMT+01:00 David Kastrup <d...@gnu.org>: > paolo prete <paoloprete...@gmail.com> writes: > > > Hi David, > > in the snippet below, is it possible to set a new duration of \

Re: Change the duration of a chord defined as a variable

paolo prete <paoloprete...@gmail.com> writes: > Hello. > > How can I change the duration of a chord defined as a variable? > I want to obtain something like: > > chord = <f' a'> > > { \chord 8 } \version "2.18.0" chord = #(define-music-function

Change the duration of a chord defined as a variable

Hello. How can I change the duration of a chord defined as a variable? I want to obtain something like: chord = <f' a'> { \chord 8 } Thanks. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Having trouble understanding optional and variable amount of arguments

nt than symbols or numbers > are required, and the closest I can imagine is chaining functions to create > the illusion of a variable amount of arguments, like this: >> >> \version "2.19.80" >> >> #(define (end-list? obj) >>(and (list? obj) >&g

Re: Including tweaks in a variable

Simon Albrecht writes: > On 01.03.2018 17:51, Michael Stickles wrote: >> It was driving me crazy at first because it still wouldn't work, >> until I dug through the documentation a bit more and found that 2.18 >> and 2.19 have a slightly different syntax for the >>

Re: Including tweaks in a variable

On 01.03.2018 17:51, Michael Stickles wrote: It was driving me crazy at first because it still wouldn't work, until I dug through the documentation a bit more and found that 2.18 and 2.19 have a slightly different syntax for the function arguments: Truly the fact that it’s difficult for power

Re: Having trouble understanding optional and variable amount of arguments

Am 01.03.2018 um 18:31 schrieb Stefano Troncaro: ... @Urs, I not familiar with \with blocks, I'll take a look at the oll-core code and experiment a bit with it. Maybe I'll be able to help. Look at https://github.com/openlilylib/scholarly/blob/master/usage-examples/annotate.ly to see an

Re: Having trouble understanding optional and variable amount of arguments

Am 01.03.2018 um 18:31 schrieb Stefano Troncaro: ... @Urs, I not familiar with \with blocks, I'll take a look at the oll-core code and experiment a bit with it. Maybe I'll be able to help. Look at https://github.com/openlilylib/scholarly/blob/master/usage-examples/annotate.ly to see an

Re: Having trouble understanding optional and variable amount of arguments

to create the illusion of a variable amount of arguments, like this: > \version "2.19.80" > #(define (end-list? obj) >(and (list? obj) > (let ((item (last obj))) > (and (symbol? item) >(equal? "end" (symbol->string item)

Re: Including tweaks in a variable

anks again! From: "Jan-Peter Voigt" <jp.vo...@gmx.de> Sent: Thursday, March 01, 2018 10:43 AM To: lilypond-user@gnu.org Subject: Re: Including tweaks in a variable Hello Michael, it works if you add \etc to the variable (in lily-dev 2.19.x II

Re: Including tweaks in a variable

Hello Michael, it works if you add \etc to the variable (in lily-dev 2.19.x IIRC): smNote = \tweak font-size #-2 \etc That way smNote becomes a music-function that takes the note as argument and the tweak is applied. If you are using 2.18 you have to create the function like this: smNote

Including tweaks in a variable

e smaller, resulting in code like this: 1 What I want to do is replace the "tweak" section with a variable, like this: smNote = \tweak font-size #-2 1 But this results in errors: error: unknown escaped string: `\smNote' error: wrong

Re: Having trouble understanding optional and variable amount of arguments

Stefano Troncaro writes: > Thank you! I see that this is not an option then. Also, I now understand > why I couldn't make the optional arguments work, since I always left them > for last. > > Do you know if it is possible to have a flexible amount of optional >

Re: Having trouble understanding optional and variable amount of arguments

Stefano Troncaro writes: > Thank you! I see that this is not an option then. Also, I now understand > why I couldn't make the optional arguments work, since I always left them > for last. You can use an explicit \default to substitute optional arguments in final

Re: Having trouble understanding optional and variable amount of arguments

wrote: >> >>> I need a little help again. I'm struggling to understand how one >would >>> make a music function like \tempo, that accepts a variable number of >>> arguments. I couldn't find its definition so I couldn't look for >myself. >>> >>> S

Re: Having trouble understanding optional and variable amount of arguments

that allows for that kind of usage? 2018-02-28 20:45 GMT-03:00 Simon Albrecht <simon.albre...@mail.de>: > On 28.02.2018 23:54, Stefano Troncaro wrote: > >> I need a little help again. I'm struggling to understand how one would >> make a music function like \tempo, that a

Re: Having trouble understanding optional and variable amount of arguments

On 28.02.2018 23:54, Stefano Troncaro wrote: I need a little help again. I'm struggling to understand how one would make a music function like \tempo, that accepts a variable number of arguments. I couldn't find its definition so I couldn't look for myself. So far I know about making lambdas

Re: Having trouble understanding optional and variable amount of arguments

that accepts a variable number of arguments. I > couldn't find its definition so I couldn't look for myself. > > So far I know about making lambdas that take additional arguments and store > the extras in a list, but this does not work in a music function (or if it > w

Having trouble understanding optional and variable amount of arguments

Hello everyone, I need a little help again. I'm struggling to understand how one would make a music function like \tempo, that accepts a variable number of arguments. I couldn't find its definition so I couldn't look for myself. So far I know about making lambdas that take additional arguments

Re: List of articulations into a scheme variable

te wrote: > I'm sorry if I re-post a previous question, but I try to be more precise. > How can I extract and print the list of articulations, keeping them > into a new variable, from an argument passed as ly:music to a scheme > function? > I tried with the snippet below: it

Re: List of articulations into a scheme variable

extract and print the list of articulations, keeping them into a new variable, from an argument passed as ly:music to a scheme function? I tried with the snippet below: it compiles but the articulations are not shown. fun = #(define-music-function (parser location note) (ly:music?)   (let

Re: List of articulations into a scheme variable

Paolo Prete <p4olo_pr...@yahoo.it> writes: > I'm sorry if I re-post a previous question, but I try to be more > precise.How can I extract and print the list of articulations, keeping > them into a new variable, from an argument passed as ly:music to a > scheme function?I trie

List of articulations into a scheme variable

I'm sorry if I re-post a previous question, but I try to be more precise.How can I extract and print the list of articulations, keeping them into a new variable, from an argument passed as ly:music to a scheme function?I tried with the snippet below: it compiles but the articulations

Re: variable

On 24 November 2017 at 16:21, David Wright wrote: > On Fri 24 Nov 2017 at 10:08:29 (+0100), David Kastrup wrote: > > Gianmaria Lari writes: > > > > > On 24 November 2017 at 09:49, David Kastrup wrote: > > > > > >> Gianmaria Lari

Re: variable

On Fri 24 Nov 2017 at 10:08:29 (+0100), David Kastrup wrote: > Gianmaria Lari writes: > > > On 24 November 2017 at 09:49, David Kastrup wrote: > > > >> Gianmaria Lari writes: > >> > >> > I'm sorry for the trivial question but why

Re: variable

> could be > > > > music = {a b} \addlyrics {Oh well} > > > > For that it needs to decide what \music is but the assignment is not > > yet complete... > > This is documented under `\addlyrics'. Maybe it makes sense to add a > warning to the variable d

Re: variable

Malte Meyn writes: > Am 24.11.2017 um 09:37 schrieb Gianmaria Lari: >> I'm sorry for the trivial question but why this code is wrong? >> >> \version "2.19.80" >> >> music = {a b} >> \music > > The easiest way to deal with this is to add some scheme code that

Re: variable

Am 24.11.2017 um 09:37 schrieb Gianmaria Lari: I'm sorry for the trivial question but why this code is wrong? \version "2.19.80" music = {a b} \music The easiest way to deal with this is to add some scheme code that does nothing: \version "2.19.80" music = {a b} #'() \music

Re: variable

> > You need to put anything in between. LilyPond looks at \music > before deciding the assignment is complete because the assignment > could be > > music = {a b} \addlyrics {Oh well} > > For that it needs to decide what \music is but the assignment is not > yet com

Re: variable

Gianmaria Lari writes: > On 24 November 2017 at 09:49, David Kastrup wrote: > >> Gianmaria Lari writes: >> >> > I'm sorry for the trivial question but why this code is wrong? >> > >> > \version "2.19.80" >> > >> > music = {a b} >>

Re: variable

On 24 November 2017 at 09:49, David Kastrup wrote: > Gianmaria Lari writes: > > > I'm sorry for the trivial question but why this code is wrong? > > > > \version "2.19.80" > > > > music = {a b} > > \music > > > > > > My understanding was that "\music" is

Re: variable

Gianmaria Lari writes: > I'm sorry for the trivial question but why this code is wrong? > > \version "2.19.80" > > music = {a b} > \music > > > My understanding was that "\music" is substituted by its value "{a b}" You need to put anything in between. LilyPond

variable

I'm sorry for the trivial question but why this code is wrong? \version "2.19.80" music = {a b} \music My understanding was that "\music" is substituted by its value "{a b}" Thank you, g. ___ lilypond-user mailing list lilypond-user@gnu.org

Re: Variable Pecking Order

Joe, The string specified immediately following \lyricsto is the name of the voice that the lyrics should follow. In your case the name of the voice is "allVoxMelody". If you wish to also name your lyrics you should use \new Lyrics = "voxLyric" \lyricsto "allVoxMelody" Joshua. On 16/11/17

Variable Pecking Order

Hello, I am new with LilyPond but have managed to find a way of listing variables; guitarB =   \relative c' { d8 e f g a b c d } voxMelodyA =   \relative c' ... and inserting them as an order of phrasing under the \score staff grouping. Unfortunately I am having difficulties when adding

Re: macro variable doesn't behave same as original?

Patrick Smith writes: > I can wait for 2.21.0. > > I'll continuing coding with the assumption that the macrovariable will > indeed be a one-for-one, text in-place, copy of the original. > > On Tue, Nov 14, 2017 at 7:44 AM, David Kastrup wrote: > >> Caagr98

Re: macro variable doesn't behave same as original?

I can wait for 2.21.0. I'll continuing coding with the assumption that the macrovariable will indeed be a one-for-one, text in-place, copy of the original. On Tue, Nov 14, 2017 at 7:44 AM, David Kastrup wrote: > Caagr98 writes: > > >> On 11/14/17 13:21,

Re: macro variable doesn't behave same as original?

Caagr98 writes: >> On 11/14/17 13:21, Patrick Smith wrote: >>> This works: >>> >>> \version "2.18.2" >>> \relative c' { >>>   \time 2/4 >>>   c4 c( d) d( e) e( f) f( g) g( a) a( b) b( c) c( b) b( a) a( g) g( >>> f) f( e) e( d) d( c2)~ c2 \fermata  \bar "|." >>>   layout{} >>>

Re: macro variable doesn't behave same as original?

In the first version, you're applying the \fermata post-event to the c2, which is perfectly valid. In the second one, you're applying it to the {...}, which doesn't make sense. I'm afraid I don't know any good solution, though. On 11/14/17 13:21, Patrick Smith wrote: > This works: > > \version

macro variable doesn't behave same as original?

This works: \version "2.18.2" \relative c' { \time 2/4 c4 c( d) d( e) e( f) f( g) g( a) a( b) b( c) c( b) b( a) a( g) g( f) f( e) e( d) d( c2)~ c2 \fermata \bar "|." layout{} } This doesn't work: \version "2.18.2" macrovariable = {c4 c( d) d( e) e( f) f( g) g( a) a( b) b( c) c( b) b( a)

Re: Variable systems-per-page only on last page?

On 10.09.2017 02:47, David F. wrote: Is there a way to tell Lilypond to put 2 systems per page on all pages except the last—the last page can have one or two systems, depending on whichever fits best? I’m afraid you might have to hard-code it. Fortunately, this can be done by something like

Re: Variable systems-per-page only on last page?

On 10/09/17 05:20, David F. wrote: > That doesn’t work for me. (Lilypond 2.19.58) I’ve got 3 bars at the end of > a piece that would comfortably fit on a single line, but they are stretched > to fill two lines. > Is there a ragged-last-staff as well? Something like that, anyway, that means

Re: Variable systems-per-page only on last page?

That doesn’t work for me. (Lilypond 2.19.58) I’ve got 3 bars at the end of a piece that would comfortably fit on a single line, but they are stretched to fill two lines. David On Sep 9, 2017, at 7:38 PM, Kieren MacMillan wrote: > Hi David, > >> Is there a way to

Re: Variable systems-per-page only on last page?

Hi David, > Is there a way to tell Lilypond to put 2 systems per page on all pages except > the last—the last page can have one or two systems, depending on whichever > fits best? 1. It would be great if there was some consistent way to tell Lilypond to consider the first and last page

Variable systems-per-page only on last page?

Is there a way to tell Lilypond to put 2 systems per page on all pages except the last—the last page can have one or two systems, depending on whichever fits best? Thanks, David ___ lilypond-user mailing list lilypond-user@gnu.org

Re: Can't refer to variable directly after defining it

% -- 8< -- foo = {c' c' c' c'} { \foo } % -- 8< -- --- is ok. soprano = { \soprano \anotherSoprano } --- is ok also. I mean: % -- 8< -- soprano = \lyricmode { la -- la -- la } refrain = \lyricmode { ha -- ha -- ha } soprano = { \soprano \refrain } %

Re: Can't refer to variable directly after defining it

4On 04/22/17 23:47, Thomas Morley wrote: The reason for it: The parser needs to check whether there is something else which needs to be added to the definition of 'foo', (most common example for those stuff is 'addlyrics') or, something else makes clear the declaration of 'foo' is complete.

Re: Can't refer to variable directly after defining it

2017-04-22 23:32 GMT+02:00 <caag...@gmail.com>: > For some reason, it seems I can't refer to a variable directly after > defining it. As soon as I do /anything/ else, it works, but `foo={...} \foo` > gives errors. > > ``` > $ cat bug.ly > \version "2.18.2" >

Can't refer to variable directly after defining it

For some reason, it seems I can't refer to a variable directly after defining it. As soon as I do /anything/ else, it works, but `foo={...} \foo` gives errors. ``` $ cat bug.ly \version "2.18.2" foo = {c' c' c' c'} % bar = {d' d' d' d'} % {e' e' e' e'} % #foo \foo $ lilypond

Re: Putting tweaks in a variable

Thanks guys, that works. --- Knute Snortum (via Gmail) On Thu, Apr 6, 2017 at 3:50 PM, Simon Albrecht wrote: > Am 07.04.2017 um 00:15 schrieb David Kastrup: > >> masterTweak = \tweak something \tweak something-else \etc >> > > To give some context: You actually need a

Re: Putting tweaks in a variable

Am 07.04.2017 um 00:15 schrieb David Kastrup: masterTweak = \tweak something \tweak something-else \etc To give some context: You actually need a music function for that purpose. \etc is only an abbreviation to have the parser (?) construct that music function for you. Best, Simon

Re: Putting tweaks in a variable

Knute Snortum <ksnor...@gmail.com> writes: > I seem to remember that there is now a way to put several tweaks into a > variable. So instead of writing this: > > c4 -\tweak something -\tweak something-else c8 > > I could write something like this: > >

Putting tweaks in a variable

I seem to remember that there is now a way to put several tweaks into a variable. So instead of writing this: c4 -\tweak something -\tweak something-else c8 I could write something like this: masterTweak = { \magic -\tweak something -\tweak something-else } ... c4 -\masterTweak

Re: Cannot use \layout in a variable

AM, you wrote: > | I've added the missing text with a sidebar: > On Wed 11 Jan 2017 at 05:03:21 (-0700), ptoye wrote: >> Thanks all for putting me right. I have to say that the documentation is very >> confusing as to the syntax. From the Learning manual: > | A variable i

Re: Cannot use \layout in a variable

On 12.01.2017 05:07, David Wright wrote: \relative is a command that controls how LP interprets the notes' octavation, More precisely: a music function, i.e. a procedure which returns music. Best, Simon ___ lilypond-user mailing list

Re: Cannot use \layout in a variable

| I've added the missing text with a sidebar: On Wed 11 Jan 2017 at 05:03:21 (-0700), ptoye wrote: > Thanks all for putting me right. I have to say that the documentation is very > confusing as to the syntax. From the Learning manual: | A variable is assigned as follows: | name

Re: Cannot use \layout in a variable

David, Sorry, I used Nabble to enter my comment, and the raw text seems to have been expunged. Go to http://lilypond.1069038.n5.nabble.com/Cannot-use-layout-in-a-variable-td199054.html and all will be revealed! Best regards, Peter mailto:lilyp...@ptoye.com www.ptoye.com

Re: Cannot use \layout in a variable

: > > which don't have the brackets. > > How does the parser know when the variable definition has finished if it can > be on multiple lines? Without the quotations, it's tricky to guess what you've seen. Some hints: { c' } is a valid input file: a music expres

Re: Cannot use \layout in a variable

ptoye wrote > Thanks, but in this case I'm more interested in why what I wrote doesn't > work. > > > > -- > View this message in context: > http://lilypond.1069038.n5.nabble.com/Cannot-use-layout-in-a-variable-tp199054p199073.html > Sent from the User mailing

Re: Cannot use \layout in a variable

ptoye wrote > How does the parser know when the variable definition has finished if it > can be on multiple lines? Also, this may help you as well, understanding that multiple lines is fine if you just remember the braces (variables included): http://lilypond.org/doc/v2.18/Documentation/le

Re: Cannot use \layout in a variable

ptoye wrote > From the Learning manual: > > How does the parser know when the variable definition has finished if it > can be on multiple lines? The variable is finished when the pair of enclosed brackets finishes, multiple lines and all :

Re: Cannot use \layout in a variable

Thanks all for putting me right. I have to say that the documentation is very confusing as to the syntax. From the Learning manual: which implies that the brackets are needed, but it's followed by: and later by: which don't have the brackets. How does the parser know when the variable

Re: Cannot use \layout in a variable

Thanks, but in this case I'm more interested in why what I wrote doesn't work. -- View this message in context: http://lilypond.1069038.n5.nabble.com/Cannot-use-layout-in-a-variable-tp199054p199073.html Sent from the User mailing list archive at Nabble.com

Re: Cannot use \layout in a variable

Am 10. Januar 2017 18:55:04 MEZ schrieb Timothy Lanfear <timo...@lanfear.me>: >On 10/01/17 16:59, Peter Toye wrote: >> Cannot use \layout in a variable I wanted to use the same layout in a > >> number of places, so put it into a variable. And got an error.

Re: Cannot use \layout in a variable

On 10/01/17 16:59, Peter Toye wrote: Cannot use \layout in a variable I wanted to use the same layout in a number of places, so put it into a variable. And got an error. \version "2.19.52" \language "english" Lay = { \layout { } } \new Score { \new Staff { \rel

Re: Cannot use \layout in a variable

ptoye wrote > I wanted to use the same layout in a number of places, so put it into a > variable. And got an error. > > \version "2.19.52" > > \language "english" > > Lay = { > \layout { > } > } > > \new Score { > \new Staff

Cannot use \layout in a variable

I wanted to use the same layout in a number of places, so put it into a variable. And got an error. \version "2.19.52" \language "english" Lay = { \layout { } } \new Score { \new Staff { \relative { c'4 c c c } } } gives Starting lilypond-windows.ex

Re: Variable weirdness

On 17/12/16 17:04, David Sumbler wrote: Further to my earllier message, I have realized that the problem I am getting has nothing to do with variable scope (at least, I don't think it does), so I was asking the wrong question. But the problem still exists. I can't say I understand what

Re: Variable weirdness

Further to my earllier message, I have realized that the problem I am getting has nothing to do with variable scope (at least, I don't think it does), so I was asking the wrong question. But the problem still exists. My abbreviated file now looks like this: % \version "2.19.48"

Re: Variable weirdness

-function like this: > > > > parserDefine = > > #(define-scheme-function (key val)(symbol? scheme?) > > (ly:parser-define! key val)) > > > > !!!(I will correct this later, when I am on real computer ) > > > > This scheme-function works on every l

Re: Combining \markup and \override in a variable

David Sumbler writes: > On Sat, 2016-11-19 at 19:58 +0100, David Kastrup wrote: >> > I find this very confusing. >> > >> > \tweak returns music, yet it requires a hyphen in front of it. [explanation] > This is very, very useful.  OK, I had to read it and think about it 3

Re: Combining \markup and \override in a variable

On Sat, 2016-11-19 at 19:58 +0100, David Kastrup wrote: > David Sumbler writes: > > > > > On Sat, 2016-11-19 at 00:27 +0100, Simon Albrecht wrote: > > > > > > On 18.11.2016 22:41, David Sumbler wrote: > > > > > > > > > > > > I need to study this (and the previous answer)

Re: Combining \markup and \override in a variable

David Sumbler writes: > On Sat, 2016-11-19 at 00:27 +0100, Simon Albrecht wrote: >> On 18.11.2016 22:41, David Sumbler wrote: >> > >> > I need to study this (and the previous answer) to see if I can >> > fathom >> > out the logic of it all. >> \tweak is a music function

Re: Combining \markup and \override in a variable

On Sat, 2016-11-19 at 00:27 +0100, Simon Albrecht wrote: > On 18.11.2016 22:41, David Sumbler wrote: > > > > I need to study this (and the previous answer) to see if I can > > fathom > > out the logic of it all. > \tweak is a music function (which means it returns music) and it > also  > takes

Re: Combining \markup and \override in a variable

On 18.11.2016 22:41, David Sumbler wrote: I need to study this (and the previous answer) to see if I can fathom out the logic of it all. \tweak is a music function (which means it returns music) and it also takes music as its third argument. The dash turns a markup into a post-event, which

Re: Combining \markup and \override in a variable

bilities, here two of them > > larco = \tweak self-alignment-X  #-0.6 -\markup { \larger \italic "┌ > arco" } > > { >   f4 d^\larco a' > } > > larcoII = \markup { \translate #'(-0.8 . 0) \larger \italic "┌ arco" > } > > { >   f4

Re: Combining \markup and \override in a variable

arkup { \larger \italic "┌ arco" } { f4 d^\larco a' } larcoII = \markup { \translate #'(-0.8 . 0) \larger \italic "┌ arco" } { f4 d^\larcoII a' } Both could be turned into a function with argument(s) for the amount of moving and the markup itself. Probably even an automagicall

Combining \markup and \override in a variable

I have a bar which contains 3 notes, e.g. fs4 ds as' | It comes after a passage which is pizzicato, but the 2nd and 3rd notes of this bar need to be arco.  However, a normal "arco" marking over the d sharp does not make it sufficiently clear that that is what is intended: particularly because of

Re: Variable weirdness

e-function (key val)(symbol? scheme?) > > (ly:parser-define! key val)) > > > > !!!(I will correct this later, when I am on real computer ) > > > > This scheme-function works on every level defining a variable into > > the  > > current parser

Re: Variable weirdness

ol? scheme?) (ly:parser-define! key val)) !!!(I will correct this later, when I am on real computer ) This scheme-function works on every level defining a variable into the current parser. HTH Jan-Peter Am 7. November 2016 23:55:00 MEZ, schrieb Simon Albrecht <simon.albre...@mail.de>: On

Re: Variable weirdness

Hello, in these situations I use a little scheme-function like this: parserDefine = #(define-scheme-function (key val)(symbol? scheme?) (ly:parser-define! key val)) !!!(I will correct this later, when I am on real computer ) This scheme-function works on every level defining a variable

Re: Variable weirdness

er.ily" \bookpart { %music... The file "frontcover.ily" contains a \bookpart block which prints a front cover with title, composer etc. - these are defined elsewhere. But it needs one more variable, viz. 'partName'. I discovered that Lilypond will not accept a variable definition

Re: Variable weirdness

tCello" > >     partName = "Cello 1" > >     \include "frontcover.ily" > > \bookpart { %music... > > > > The file "frontcover.ily" contains a \bookpart block which prints a > > front cover with title, composer etc.

Re: Variable weirdness

\bookpart { %music... > > The file "frontcover.ily" contains a \bookpart block which prints a > front cover with title, composer etc. - these are defined elsewhere. >  But it needs one more variable, viz. 'partName'. > > I discovered that Lilypond will not accept a

Variable weirdness

ck which prints a front cover with title, composer etc. - these are defined elsewhere.  But it needs one more variable, viz. 'partName'. I discovered that Lilypond will not accept a variable definition in Lilypond format in the position I have put it: at the top level of a \book block.  No

Re: scheme code generate variable series with leading "\"

Re: scheme code generate variable series with leading "\" 2016-08-09 12:20 GMT+02:00 MING TSANG <tsan...@rogers.com>: > Thomas, how to use "$@(reverse (map cdr mel))"? Hi, try below. Uncommenting the displaying may help to see whats going on. mel.1 = { c'4 } mel.2

Re: scheme code generate variable series with leading "\"

2016-08-09 12:20 GMT+02:00 MING TSANG : > Thomas, how to use "$@(reverse (map cdr mel))"? Hi, try below. Uncommenting the displaying may help to see whats going on. mel.1 = { c'4 } mel.2 = { d' } mel.3 = { e' } %% make visible whats going on, i.e. print to terminal

Re: scheme code generate variable series with leading "\"

m> To: David Kastrup <d...@gnu.org> Cc: MING TSANG <tsan...@rogers.com>; Lilypond-usermailinglist <lilypond-user@gnu.org> Sent: Monday, August 8, 2016 10:51 AM Subject: Re: scheme code generate variable series with leading "\" 2016-08-08 14:15 GMT+02:00 D

Re: scheme code generate variable series with leading "\"

2016-08-08 14:15 GMT+02:00 David Kastrup <d...@gnu.org>: > Thomas Morley <thomasmorle...@gmail.com> writes: > >> 2016-08-08 13:49 GMT+02:00 MING TSANG <tsan...@rogers.com>: >>> Dear lilyponders: >>> I do not know scheme code. Can scheme c

Re: scheme code generate variable series with leading "\"

David Kastrup writes: > expendVar = > #(define-music-function (xx start stop) (list? index? index?) > #{ #@(map (lambda (i) #{ $xx . #i #}) (iota (- stop start -1) start)) #}) This currently needs to be $@(map ... since $xx . #i does not at the current point of time create a

Re: scheme code generate variable series with leading "\"

Thomas Morley <thomasmorle...@gmail.com> writes: > 2016-08-08 13:49 GMT+02:00 MING TSANG <tsan...@rogers.com>: >> Dear lilyponders: >> I do not know scheme code. Can scheme code to generate variable series with >> leading "\"? >> Detail question

Re: scheme code generate variable series with leading "\"

ic expressions. HTH Jan-Peter Am 08.08.2016 um 13:49 schrieb MING TSANG: Dear lilyponders: I do not know scheme code. Can scheme code to generate variable series with leading "\"? Detail question in the lily file attachment. Thank you for any help. Immanuel, Ming. ___

Re: scheme code generate variable series with leading "\"

MING TSANG <tsan...@rogers.com> writes: > Dear lilyponders:I do not know scheme code. Can scheme code to > generate variable series with leading "\"?Detail question in the lily > file attachment.Thank you for any help.Immanuel,Ming. \version "2.19.46" \language

Re: scheme code generate variable series with leading "\"

2016-08-08 13:49 GMT+02:00 MING TSANG <tsan...@rogers.com>: > Dear lilyponders: > I do not know scheme code. Can scheme code to generate variable series with > leading "\"? > Detail question in the lily file attachment. > Thank you f

scheme code generate variable series with leading "\"

Dear lilyponders:I do not know scheme code. Can scheme code to generate variable series with leading "\"?Detail question in the lily file attachment.Thank you for any help.Immanuel,Ming. \version "2.19.46" \language "english" \header { title = "感谢ä¸

<    1   2   3   4   5   6   7   8   9   >