Re: Use variable to simplify colorizing specific notes

Noeck writes: >> However I haven't found any variant of this that works. > > > Hi Jim, > > this works for me: > > > \version "2.19.36" > > stable = \tweak #'color #red \etc > > { > a \stable b > } The 2.18 equivalent is stable = #(define-music-function (parser location

Re: Use variable to simplify colorizing specific notes

> However I haven't found any variant of this that works. Hi Jim, this works for me: \version "2.19.36" stable = \tweak #'color #red \etc { a \stable b } Cheers, Joram ___ lilypond-user mailing list lilypond-user@gnu.org

Use variable to simplify colorizing specific notes

ng Turkish improvisations, and I'm colorizing "stable" notes to help visualize the structure of the improvisation. What I have in mid is setting a variable such as stable = \tweak color #red so that in the score I can simply precede a note name with \stable However I haven

Re: using variable within make-pango-font-tree

menelikke <antfont...@gmail.com> writes: > Hi > > does anybody knows if and how is possibile to use a variable within > "make-pango-font-tree" function, please? > > I'm using > > \version "2.18.2" % necessary for upgrading to future

using variable within make-pango-font-tree

Hi does anybody knows if and how is possibile to use a variable within "make-pango-font-tree" function, please? I'm using \version "2.18.2" % necessary for upgrading to future LilyPond versions. \include "global.ly" \paper { #(define fonts (

Re: chordmode using variable

2016-04-28 14:05 GMT+02:00 Simon Albrecht <simon.albre...@mail.de>: > On 28.04.2016 11:52, Gianmaria Lari wrote: >> >> Dear Harm, >> >> some weeks ago replying to me, you used a variable name syntax that I >> didn't know: >> >>> mynote.7 = ...

Re: chordmode using variable

t; >> Dear Harm, >> >> some weeks ago replying to me, you used a variable name syntax that I >> didn't know: >> >>> mynote.7 = . >> >> I see the compiler didn't complain and having the possibility to use >> number in the variable name would b

Re: chordmode using variable

On 28.04.2016 11:52, Gianmaria Lari wrote: Dear Harm, some weeks ago replying to me, you used a variable name syntax that I didn't know: mynote.7 = . I see the compiler didn't complain and having the possibility to use number in the variable name would be very practical (at least for me

Re: chordmode using variable

Dear Harm, some weeks ago replying to me, you used a variable name syntax that I didn't know: > mynote.7 = . I see the compiler didn't complain and having the possibility to use number in the variable name would be very practical (at least for me). But is it a "standard programmi

Re: duration using variable (Gianmaria Lari)

Dear Cynthia, thank you for your help! What you propose works correctly but it is not practical. I use tag to avoid duplicating code so it is crucial to be able to do not create two different variables music_screenOut and music_midiOut. Thank you, g.

Re: duration using variable

\score > > { > > \keepWithTag #'screenOut \music > > \layout {} > > } > > > > \score > > { > > \keepWithTag #'midiOut \music > > \layout {} > > \midi {} > > } > > > > > > In the attached captur

Re: duration using variable (Gianmaria Lari)

> On Apr 27, 2016, at 3:57 AM, lilypond-user-requ...@gnu.org wrote: > > Message: 4 > Date: Wed, 27 Apr 2016 10:56:53 +0200 > From: Gianmaria Lari <gianmarial...@gmail.com> > Subject: duration using variable > > In the previous example the cC variable contains a

Re: duration using variable

On Wed, 2016-04-27 at 13:02 +0200, David Kastrup wrote: > Graham King writes: > > > perhaps try: > > \scaleDurations 2/1 { \cC } > > Doesn't change the visuals. > Sorry. More haste, less speed. I meant \shiftDurations. It might require other things to be

Re: duration using variable

d the second using midiOut. > > * * * > > Now I would like to be able to increase the lenght of the musical expression > contained in the cC variable. > > In the previous example the cC variable contains a quarter note (and a > quarter bichord) and I would like to change it to an ha

Re: duration using variable

Graham King writes: > perhaps try: > \scaleDurations 2/1 { \cC } Doesn't change the visuals. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: duration using variable

perhaps try: \scaleDurations 2/1 { \cC } hth -- Graham > > > Now I would like to be able to increase the lenght of the musical > expression contained in the cC variable. > > > In the previous example the cC variable contains a quarter note (and a > quarter b

duration using variable

different output, the first when using screenOut and the second using midiOut. * * * Now I would like to be able to increase the lenght of the musical expression contained in the cC variable. In the previous example the cC variable contains a quarter note (and a quarter bichord) and I woul

Re: Termination of variable definitions

On 19/04/2016 21:55, Johannes Waldmann wrote: http://lists.gnu.org/archive/html/lilypond-user/2016-04/msg00465.html ... But it's recursive. what does that mean? - J.W. Recursion: See "Recursion". To take the violin example, violin = \new Staff { \relative { a'4 b c b } }

Re: chordmode using variable

Thomas, it works fantastically well! > So why? I don't see any advantage. I'm writing a kind of library to write accordion music. Let me finish the work and then I will post it here so that others can take advantage of it (I hope so) and/or suggest a better way to do it. Thanks again! g.

Re: chordmode using variable

2016-04-20 10:34 GMT+02:00 Gianmaria Lari <gianmarial...@gmail.com>: > To generate the dominant seventh chord of c we use > > \chordmode {c:7} > > > Does exist any way to make the same thing but starting from a variable > containing a note? > > Something like th

chordmode using variable

To generate the dominant seventh chord of c we use \chordmode {c:7} Does exist any way to make the same thing but starting from a variable containing a note? Something like this: mynote = {c} \chordmode { \mynote:7 } Thank you, g. ___ lilypond

Re: Termination of variable definitions

Thomas Morley writes: > Well, LilyPond uses an input-language, I don't think it qualifies as a > programming-language. > But you you can do a lot > > xx = \override NoteHead.color = #red > is one expression > yy = \override NoteHead.font-size = #5 > is one

Re: Termination of variable definitions

2016-04-19 23:25 GMT+02:00 David Sumbler <da...@aeolia.co.uk>: > Thank you all for your help on this. > > My original question, "how does Lilypond recognize the end of the > definition of a variable" has been answered: the definition has to be a > single, complete

Re: Termination of variable definitions

Thank you all for your help on this. My original question, "how does Lilypond recognize the end of the definition of a variable" has been answered: the definition has to be a single, complete expression. Which of course produces another question: "what is classed as a single exp

Re: Termination of variable definitions

David Wright writes: > violin = \new Voice b > you can substitute again, this time for "b". > (Within limits: contexts have a parent/child ordering, so Staff > can contain Voice but not vice versa.) Semantically not, but syntactically this is not a problem: \relative

Re: Termination of variable definitions

http://lists.gnu.org/archive/html/lilypond-user/2016-04/msg00465.html > ... But it's recursive. what does that mean? - J.W. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Termination of variable definitions

; and/or the $(if condition action) structure provided by David Kastrup, I >> > found that there is something very, very basic that I have never really >> > understood. >> > >> > So at the risk of embarrassing myself, I should be grateful if somebody >> > woul

Re: Termination of variable definitions

On Tue 19 Apr 2016 at 19:38:14 (+0100), David Sumbler wrote: > So at the risk of embarrassing myself, I should be grateful if somebody > would explain the following: how does Lilypond recognize the end of a > variable definition? Oversimplifying, there are about four things you c

Re: Termination of variable definitions

condition action) structure provided by David Kastrup, I >> > found that there is something very, very basic that I have never really >> > understood. >> > >> > So at the risk of embarrassing myself, I should be grateful if somebody >> > would explain th

Re: Termination of variable definitions

there is something very, very basic that I have never really > > understood. > > > > So at the risk of embarrassing myself, I should be grateful if somebody > > would explain the following: how does Lilypond recognize the end of a > > variable definitio

Re: Termination of variable definitions

> > So at the risk of embarrassing myself, I should be grateful if somebody > would explain the following: how does Lilypond recognize the end of a > variable definition? One expression. > For instance, an example from the documentation shows: > > violin = \new

Termination of variable definitions

would explain the following: how does Lilypond recognize the end of a variable definition? For instance, an example from the documentation shows: violin = \new Staff { \relative { a'4 b c b } } cello = \new Staff { \relative { \clef "bass" e2 d } } What I don't

Re: variable to simplify writing / chordmode and <<>>

2016-04-15 11:06 GMT+02:00 Gianmaria Lari : > I writing some accordion scores and for this reason I'm trying to create the > lilypond tools that will make the task more easy. > > I started writing the following vaiables: > > cC = {c4} > cc = \chordmode {c4} > ccC = { \new

variable to simplify writing / chordmode and <<>>

I writing some accordion scores and for this reason I'm trying to create the lilypond tools that will make the task more easy. I started writing the following vaiables: cC = {c4} cc = \chordmode {c4} ccC = { \new Voice << {\cC} {\cc}>>}%first solution (In the attached image you can see an

Re: Variable slur thickness

gt; grob > >>> internally calculate its own control points rather than relying on it > >>> being > >>> calculated elsewhere (also attached): > >> > >> Works great! I improved it further by making it compatible with ties > too: > >> >

Re: Variable slur thickness

ess property and having each grob >>> internally calculate its own control points rather than relying on it >>> being >>> calculated elsewhere (also attached): >> >> Works great! I improved it further by making it compatible with ties too: >> >> >>

Re: Inline images, was Re: Variable slur thickness

On Thu 10 Mar 2016 at 10:19:29 (-0600), Cynthia Karl wrote: > On Thu, 10 Mar 2016 06:04:57 -0700 (MST) tisimst > schrieb: > > > > HTH, > > Abraham > > > > P.S. Some of the power users on this list filter inline images, so if you > > wouldn't mind making the image an

Re: Variable slur thickness

n relying on it >> being >> calculated elsewhere (also attached): > > Works great! I improved it further by making it compatible with ties too: > > > #(define (variable-slur-thickness min-l max-l min-t max-t) (lambda (grob) > (let* ((cpf (if (grob::has-interface

Re: Variable slur thickness

eat! I improved it further by making it compatible with ties too: #(define (variable-slur-thickness min-l max-l min-t max-t) (lambda (grob) (let* ((cpf (if (grob::has-interface grob 'tie-interface) ly:tie::calc-control-points ly:slur::calc-control-points))

Re: Variable slur thickness

alculate its own control points rather than relying on it being calculated elsewhere (also attached): \version "2.19.36" #(define (variable-slur-thickness min-l max-l min-t max-t) (lambda (grob) (let* ((cpt (ly:slur::calc-control-points grob)) (cp0 (car cpt))

Re: Variable slur thickness

2016-03-11 10:23 GMT+01:00 Sharon Rosner : >> This problem arose before. >> One needs to set 'thickness before-line-breaking, but then you don't >> have access to the control-points, as far as I remember. >> I'm not sure there is any way, have to think about it. > > Can you

Re: Variable slur thickness

> This problem arose before. > One needs to set 'thickness before-line-breaking, but then you don't > have access to the control-points, as far as I remember. > I'm not sure there is any way, have to think about it. Can you explain what’s going on? As far as I could tell from debugging the

Re: Variable slur thickness

2016-03-11 10:01 GMT+01:00 Sharon Rosner : >> Thus again: how should it look, in cases where a broken slur has a >> (very) long and a (very) short part? >> Some average-thickness? Or something else? > > The problem is not with the broken slurs, but rather with the other slurs >

Re: Variable slur thickness

16, 17-19, 20-23 etc. Thanks Sharon -- View this message in context: http://lilypond.1069038.n5.nabble.com/Variable-slur-thickness-tp188374p188431.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-use

Re: Variable slur thickness

2016-03-11 1:18 GMT+01:00 Sharon Rosner <cico...@gmail.com>: >> How should it look in situations like below? >> >> \score { >> { c'1( \break d') \repeat unfold 12 { d' \noBreak } c'( \break c' d' c' d') } >> \layout { >> \override Slur.after-line-bre

Re: Variable slur thickness

> How should it look in situations like below? > > \score { > { c'1( \break d') \repeat unfold 12 { d' \noBreak } c'( \break c' d' c' d') } > \layout { > \override Slur.after-line-breaking = #(variable-slur-thickness 3 10 1.4 > 12.7) > } > } I created something

Re: Variable slur thickness

> Sharon How should it look in situations like below? \score { { c'1( \break d') \repeat unfold 12 { d' \noBreak } c'( \break c' d' c' d') } \layout { \override Slur.after-line-breaking = #(variable-slur-thickness 3 10 1.4 12.7) } } Cheers, Harm _

Re: Variable slur thickness

Hi Abraham, Putting this code into actual use, I found a show stopper. After a line break, the slur thickness stops being adjusted and reflects the default thickness value. Any idea? Sharon -- View this message in context: http://lilypond.1069038.n5.nabble.com/Variable-slur-thickness

Re: Variable slur thickness

lsr.di.unimi.it/LSR/Item?id=1028 >> > >> >> The header of the third score isn’t correct: Thickness goes from 1.2 to >> 2.7, not 1.4 to 2.7. > > > (facepalm) Thanks. Corrected. > > - Abraham Hi Abraham, I had a look. Pretty nice one, some nitpicks, though.

Re: Inline images, was Re: Variable slur thickness

At 10:56 10/03/2016 -0600, Matthew Skala wrote: On Thu, 10 Mar 2016, Brian Barker wrote: At 10:33 10/03/2016 -0600, Matthew Skala wrote: ... HTML in email is usually spam. You are joking, of course! No. OK, I'll rephrase that to help you: either you *have to be* joking or you are plain

Re: Inline images, was Re: Variable slur thickness

On Thu, 10 Mar 2016, Brian Barker wrote: > At 10:33 10/03/2016 -0600, Matthew Skala wrote: > > ... HTML in email is usually spam. > > You are joking, of course! No. -- Matthew Skala msk...@ansuz.sooke.bc.ca People before principles. http://ansuz.sooke.bc.ca/

Re: Inline images, was Re: Variable slur thickness

At 10:33 10/03/2016 -0600, Matthew Skala wrote: ... HTML in email is usually spam. You are joking, of course! Brian Barker ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Inline images, was Re: Variable slur thickness

now that some other regular list followers have mentioned this in the past. Perhaps doing both is how to satisfy both worlds, like you said? Best, Abraham -- View this message in context: http://lilypond.1069038.n5.nabble.com/Inline-images-was-Re-Variable-slur-thickness-tp188389p188391.html Sent

Re: Inline images, was Re: Variable slur thickness

On Thu, 10 Mar 2016, Cynthia Karl wrote: > Why on earth would anyone filter inline images? I filter HTML, because HTML in email is usually spam. "Inline" images imply HTML and thus get filtered too. -- Matthew Skala msk...@ansuz.sooke.bc.ca People before principles.

Inline images, was Re: Variable slur thickness

achment.html was > not found on this server. That’s not very convenient at all. Am I the only one with this problem? What’s the solution? Maybe it would be nice if inline images were also added as attachments? Regards, Pat Karl > > -- > View this message in context: > ht

Re: Variable slur thickness

correct: Thickness goes from 1.2 to > 2.7, not 1.4 to 2.7. > (facepalm) Thanks. Corrected. - Abraham -- View this message in context: http://lilypond.1069038.n5.nabble.com/Variable-slur-thickness-tp188374p188388.html Sent from the User mailing list archive at Nabble.com._

Re: Variable slur thickness

Am 10.03.2016 um 16:56 schrieb tisimst: Submitted to LSR: http://lsr.di.unimi.it/LSR/Item?id=1028 The header of the third score isn’t correct: Thickness goes from 1.2 to 2.7, not 1.4 to 2.7. ___ lilypond-user mailing list lilypond-user@gnu.org

Re: Variable slur thickness

e solution: >> >> Fantastic! I refactored the code to make it easier to change the >> parameters: >> > > +1. Nicely refactored. > Submitted to LSR: http://lsr.di.unimi.it/LSR/Item?id=1028 - Abraham -- View this message in context: http://lilypond.1069038.n5.na

Re: Variable slur thickness

; +1. Nicely refactored. - Abraham -- View this message in context: http://lilypond.1069038.n5.nabble.com/Variable-slur-thickness-tp188374p188379.html Sent from the User mailing list archive at Nabble.com.___ lilypond-user mailing list lil

Re: Variable slur thickness

> I was thinking about this just yesterday. Here's a reasonable solution: Fantastic! I refactored the code to make it easier to change the parameters: #(define (variable-slur-thickness min-l max-l min-t max-t) (lambda (grob) (let* ((cpt (ly:grob-property grob 'control-points)) (

Re: Variable slur thickness

" th) ;(format #t "newth: ~a\n" newth) (ly:grob-set-property! grob 'thickness newth) )) } %% HTH, Abraham P.S. Some of the power users on this list filter inline images, so if you wouldn't mind making the image an attachment next time, I know they'll appreciate i

Variable slur thickness

Hi All The following example shows slurs of variable length, engraved using a bigger than normal thickness. The first slur looks a bit too thick, and I'm having a hard time balancing the slur thickness so both short and long slurs would look good. <http://lilypond.1069038.n5.nabble.com/f

Re: Storing a bookpart in a variable

Vaughan McAlley <vaug...@mcalley.net.au> writes: > Greetings, > > I’d like to be able to specify at the top of my main score which > movements are printed. I can store a \bookpart in a variable, but I > can’t seem to return it from a scheme expression. Is there a bookpart &

Re: Storing a bookpart in a variable

I’d like to be able to specify at the top of my main score which movements are printed. I can store a \bookpart in a variable, but I can’t seem to return it from a scheme expression. Is there a bookpart equivalent to define-music-function that I haven’t found? Vaughan %% \version &

Re: Storing a bookpart in a variable

;>> Le 25 févr. 2016 à 00:48, Vaughan McAlley <vaug...@mcalley.net.au> a écrit : >>> >>> Greetings, >>> >>> I’d like to be able to specify at the top of my main score which >>> movements are printed. I can store a \bookpart in a variable, but I >&

Re: Storing a bookpart in a variable

t; >> Greetings, >> >> I’d like to be able to specify at the top of my main score which >> movements are printed. I can store a \bookpart in a variable, but I >> can’t seem to return it from a scheme expression. Is there a bookpart >> equivalent to define-mus

Re: Storing a bookpart in a variable

I can store a \bookpart in a variable, but I > can’t seem to return it from a scheme expression. Is there a bookpart > equivalent to define-music-function that I haven’t found? > > Vaughan > > > %% > \version "2.18.2" > > compil

Storing a bookpart in a variable

Greetings, I’d like to be able to specify at the top of my main score which movements are printed. I can store a \bookpart in a variable, but I can’t seem to return it from a scheme expression. Is there a bookpart equivalent to define-music-function that I haven’t found? Vaughan

Re: Passing along variable-number arguments

Urs Liska writes: > Am 02.02.2016 um 00:44 schrieb David Kastrup: >> Urs Liska writes: >> >>> In this code "format" receives "fmt" (the format strings) and "vals" - >>> the *list* of arguments. >>> How should I modify this so "format" doesn't

Passing along variable-number arguments

Hi, I'm hitting a wall with Scheme once more. I need to create wrapper functions around (format) and other functions that need a variable number of arguments. I know that with #(define (my-proc fmt . vals) "vals" will be an arbitrary number of arguments that will be wrapped

Re: Passing along variable-number arguments

Urs Liska <u...@openlilylib.org> writes: > Hi, > > I'm hitting a wall with Scheme once more. > I need to create wrapper functions around (format) and other functions > that need a variable number of arguments. > > I know that with > > #(defi

Re: Variable names

t; that a non-alpha separator is good to have, but two different >> separators may quickly become confusing. Is it 'set_variable' or >> 'set-variable'? >> >> Given the relation between LP and Guile, I'd suggest to only allow the >> dash and disallow the underscore (by syn

Variable names

I assume there have been discussions on extending the syntax for LP identifiers to include dashes and underscores. My personal opinion is that a non-alpha separator is good to have, but two different separators may quickly become confusing. Is it 'set_variable' or 'set-variable'? Given

Re: Variable names

may quickly become confusing. Is it 'set_variable' or > 'set-variable'? > > Given the relation between LP and Guile, I'd suggest to only allow the > dash and disallow the underscore (by syntax rule, not just by > convention). [...] I think extending identifiers to include '-' and '_' is

Re: Strings as variable names

olve enumeration, and Arabic numbers are out of the question. So I have a legend at the top of each include file describing what my nomenclature means: % Trichord Variable Names % 012: A % 013: B % 014: C % 015: D % 016

Re: Strings as variable names

in half-hours here and there: learning enough > scheme to do this is impractical. So in the meantime, I basically have > to give each three-note motive a variable with a coded name that allows > sufficient differentiation and can be searched reasonably easily. > Variables with Arabic nume

Re: Strings as variable names

> > Using the syntax with quotes is rather ugly, I agree. But it is > > nonetheless potentially useful for two reasons: > > (1) it enables us to use numbers etc. in variable names > Why would that be desirable? Suppose you make an edition of the St Matthew Passion, in which

Re: Strings as variable names

On 04.01.2016 08:02, Johan Vromans wrote: On Sun, 3 Jan 2016 21:36:30 +0100 Simon Albrecht wrote: No, for the simple reasons that a) noone mentioned on the list there was a tracker item and b) even though I know now, I have been unable to find it. May I kindly request

Re: guileV2 and Lilypond (was: Strings as variable names)

Hello Paul, Thanks a lot for the informatin and links, things are much clearer to me now. JM > Le 3 janv. 2016 à 20:51, Paul Morris a écrit : > >> On Jan 3, 2016, at 11:14 AM, Menu Jacques wrote: >> >> A newbie question: what are the expected

Re: trying to attach lyrics to global variable in /score

On 04.01.2016 03:29, David Wright wrote: ... but it does mean that you can't use \addlyrics, and dispense with naming the context when not required (ie simple cases). True, I deliberately left that one out, since it’s error-prone. Yours, Simon ___

Re: Strings as variable names

rings? Um, let's see: Ruby, PHP, Javascript (as of ES6), Swift, Scala, C#, Perl. Ah yes I forgot, Perl is not a _real_ programming language ;-) Sharon -- View this message in context: http://lilypond.1069038.n5.nabble.com/Strings-as-variable-names-tp185113p185529.html Sent from the User

Re: trying to attach lyrics to global variable in /score

Thank you for the reminder, so he is a complete, however abridged version of my code: viola = \new Voice \relative c' { c1 c1 c1 } recorder = \new Voice \relative c' { c1 c1 c1 } verseOne = \lyricmode { m -- -- -- } \score { \new StaffGroup << \new Staff << \new Voice \global \new

Re: Strings as variable names

On Sun, 03 Jan 2016 21:16:27 +0100 David Kastrup wrote: > Johan Vromans writes: > > Is this going to be taken seriously or can I spare the efforts? > There is a tracker issue for it and some discussion. [..] Have you > followed the discussion in the

Re: Strings as variable names

On 03.01.2016 21:34, Johan Vromans wrote: On Sun, 03 Jan 2016 21:16:27 +0100 David Kastrup wrote: Johan Vromans writes: Is this going to be taken seriously or can I spare the efforts? There is a tracker issue for it and some discussion. [..] Have you

Re: trying to attach lyrics to global variable in /score

Hello Ryan, please always reply on-list. Others may find the solution helpful as well. Also, please send complete compilable examples (with a version statement), else it’s difficult to figure out the problem. That said: The following code works for me. %% \version "2.18.2" global = {

Re: trying to attach lyrics to global variable in /score

On Mon 04 Jan 2016 at 00:26:44 (+0100), Simon Albrecht wrote: [...] > That said: The following code works for me. > > %% > \version "2.18.2" > global = { s1 } > recorder = { c''1 } > verseOne = \lyricmode { test } > \score { > \new StaffGroup << > > \new Staff << > \new Voice

Re: Strings as variable names

On Sun 03 Jan 2016 at 16:22:29 (+0100), David Kastrup wrote: > David Wright <lily...@lionunicorn.co.uk> writes: > > > On Mon 28 Dec 2015 at 20:27:22 (+0100), David Kastrup wrote: > >> > >> The strings in Python's regular expression replacements can interpo

Re: trying to attach lyrics to global variable in /score

On Sun 03 Jan 2016 at 15:33:39 (-0800), Ryan Michael wrote: > Thank you for the reminder, so he is a complete, however abridged version of > my > code:  > > viola = \new Voice \relative c' { > c1 c1 c1 > } > > recorder = \new Voice \relative c' { > c1 c1 c1 > } > > verseOne = \lyricmode { >  

Re: Strings as variable names

On Sun, 3 Jan 2016 21:36:30 +0100 Simon Albrecht wrote: > > No, for the simple reasons that a) noone mentioned on the list there was > > a tracker item and b) even though I know now, I have been unable to > > find it. > > > > May I kindly request mentioning the URL to the

Re: Strings as variable names

and > juxtaposed with other double-quoted strings they combine into a larger > string I believe. But that's only for preprocessor constants, and those > are not really part of the language proper. > > The strings in Python's regular expression replacements can interpolate > va

Re: Strings as variable names

David Wright <lily...@lionunicorn.co.uk> writes: > On Mon 28 Dec 2015 at 20:27:22 (+0100), David Kastrup wrote: >> >> The strings in Python's regular expression replacements can interpolate >> variable values, but those are not part of the string syntax but of the >

Re: Strings as variable names

> On Jan 3, 2016, at 10:06 AM, David Wright wrote: > > Recognising the lack of this construct, python is currently adding string > interpolation to the language. Looks like a trend as Javascript also got it in the ECMAscript 2015 specification:

guileV2 and Lilypond (was: Strings as variable names)

Hello folks, A happy new year 2016 to everybody! A newbie question: what are the expected benefits and challenges of moving from guile 1.8.x to guile 2.y? JM ___ lilypond-user mailing list lilypond-user@gnu.org

trying to attach lyrics to global variable in /score

I have the following lilypond code: \score { \new StaffGroup << \new Staff << \global \recorder >> \new Lyrics \lyricsto "recorder" { \verseOne } \new Staff << \global \viola >> >> \layout { } \midi { } } However I get the error: *cannot find Voice `recorder'*

Re: trying to attach lyrics to global variable in /score

On 03.01.2016 20:40, Ryan Michael wrote: I have the following lilypond code: \score { \new StaffGroup << \new Staff << \global \recorder >> \new Lyrics \lyricsto "recorder" { \verseOne } \new Staff << \global \viola >> >> \layout { } \midi { } } \lyricsto

Re: guileV2 and Lilypond (was: Strings as variable names)

> On Jan 3, 2016, at 11:14 AM, Menu Jacques wrote: > > A newbie question: what are the expected benefits and challenges of moving > from guile 1.8.x to guile 2.y? As I understand it, guile 2.0 introduced significant performance improvements, mainly for compiled scheme, but

Re: Strings as variable names

On Mon, 28 Dec 2015 20:28:58 +0100 Johan Vromans wrote: > NR refers to > http://www.lilypond.org/doc/v2.19/Documentation/learning/organizing-pieces-with-variables > which does not mention the quoted syntax, and explicitly disallows dashes > and underscores. > > ===

Re: Strings as variable names

Johan Vromans writes: > On Mon, 28 Dec 2015 20:28:58 +0100 > Johan Vromans wrote: > >> NR refers to >> http://www.lilypond.org/doc/v2.19/Documentation/learning/organizing-pieces-with-variables >> which does not mention the quoted syntax, and

Re: Strings as variable names

Hi David, > the name define-music-function renders the "Extending LilyPond” > guide ineligible for the Nobel Prize in Literature. Oh, is *that* what’s keeping us out of the running?? :) Thanks for the giggle! Kieren. Kieren MacMillan, composer ‣ website:

Re: Strings as variable names

Johan Vromans writes: > On Mon, 28 Dec 2015 23:04:37 +0100 > David Kastrup wrote: > >> You conveniently snipped shells so that you could mention them again. > > You can find a lot more on > https://en.wikipedia.org/wiki/String_interpolation About a third of

<    1   2   3   4   5   6   7   8   9   >