Re: Variables, tags, filtering, conditions

On 19/05/2024 12:11, Giles Boardman wrote: Hello Timothy, Looks about perfect to me. Thank you very much. I can see how it's working and there are obviously a lot of other programming possibilities hinted at that I haven't found the documentation for. Where do I read about #( if (string=? an

Re: Variables, tags, filtering, conditions

nks Giles From: Timothy Lanfear Sent: 19 May 2024 12:03 To: Giles Boardman ; lilypond-user@gnu.org Subject: Re: Variables, tags, filtering, conditions On 19/05/2024 11:36, Giles Boardman wrote: Hello, I am an occasional Bb clarinetist and very bad at transposing on the fly. I wou

Re: Variables, tags, filtering, conditions

On 19/05/2024 11:36, Giles Boardman wrote: Hello, I am an occasional Bb clarinetist and very bad at transposing on the fly. I would like to create alternative versions of a score based on the value of a parameter. How about this as a solution? \version "2.24.0" instrument = "clarinet" tp

Re: Variables and Bookpart

> use: > > ``` > % movement1.ly > variable = \relative c'' { ... } > bookpartI = \bookpart { \score { \variable } } > > % movement2.ly > variableII = \relative c'' { ... } > bookpartII = \bookpart { \score { \variableII } } > > % main.ly > \include "movement1.ly" > \include "movement2.ly" > \bo

RE: Variables and Bookpart

; 'Hans Aikema' Cc: 'lilypond-user mailinglist' Subject: Re: Variables and Bookpart Le dimanche 12 mars 2023 à 16:54 -0700, Mark Stephen Mrotek a écrit : Hans, Thank you for your advice. That format is not what is given in the manual. \bookpart { \header { … } \sc

Re: Variables and Bookpart

That really only addresses the full score, not the parts, since in the parts multiple movements share the same bookpart. On Sun, Mar 12, 2023 at 5:19 PM Jean Abou Samra wrote: > Le dimanche 12 mars 2023 à 17:06 -0700, Saul Tobin a écrit : > > For what it's worth my use case was that I use the sa

RE: Variables and Bookpart

; lilypond-user@gnu.org; Hans Aikema Cc: j...@abou-samra.fr Subject: Re: Variables and Bookpart If I’m thinking correctly what Mark attempts to do is to have multiple files containing scores and then to \bookpart { \include ... } to combine these scores. The problem here is quite simple: The

Re: Variables and Bookpart

Le dimanche 12 mars 2023 à 17:06 -0700, Saul Tobin a écrit : > For what it's worth my use case was that I use the same variable names for > each instrument in a separate file for each movement of a piece. I therefore > need to \include the music for each movement immediately before the \score >

Re: Variables and Bookpart

Le dimanche 12 mars 2023 à 16:54 -0700, Mark Stephen Mrotek a écrit : > Hans, >   > Thank you for your advice. > That format is not what is given in the manual. >   > \bookpart { >   \header { … } >   \score { … } > }. I find this fascinating, because the user who asked this ques

Re: Variables and Bookpart

For what it's worth my use case was that I use the same variable names for each instrument in a separate file for each movement of a piece. I therefore need to \include the music for each movement immediately before the \score for that movement, in order to redefine the variables with the music for

RE: Variables and Bookpart

...@aikebah.net] Sent: Sunday, March 12, 2023 3:51 PM To: Mark Stephen Mrotek Cc: lilypond-user mailinglist Subject: Re: Variables and Bookpart On 12 Mar 2023, at 20:38, Mark Stephen Mrotek mailto:carsonm...@ca.rr.com> > wrote: Jean Abou Samra, Thank you. Yes variables must (a

Re: Variables and Bookpart

Le dimanche 12 mars 2023 à 16:34 -0700, Saul Tobin a écrit : > A slightly nicer syntax to workaround this limitation is to use the function: > > parserDefine = > #(define-void-function (name val)(symbol? scheme?) >     (ly:parser-define! name val)) > > Then instead of var = { ... } you can

Re: Variables and Bookpart

Le lundi 13 mars 2023 à 00:24 +0100, Valentin Petzel a écrit : > (by the way this also allows us to define bindings the parser does not handle > > well such as e.g. \c: c = ... will not be allowed, as c is a note name, but > #(define c ...) works). You can write ``` "c" = ... ``` though.

Re: Variables and Bookpart

A slightly nicer syntax to workaround this limitation is to use the function: parserDefine = #(define-void-function (name val)(symbol? scheme?) (ly:parser-define! name val)) Then instead of var = { ... } you can write \parserDefine var { ... }. I believe this was posted on the list a few yea

Re: Variables and Bookpart

If I’m thinking correctly what Mark attempts to do is to have multiple files containing scores and then to \bookpart { \include ... } to combine these scores. The problem here is quite simple: The notation name = value is something that is evalutated by the parser and will generally evaluate

Re: Variables and Bookpart

> On 12 Mar 2023, at 20:38, Mark Stephen Mrotek wrote: > > Jean Abou Samra, > > Thank you. > Yes variables must (and are) placed before the \score in each individual > movement. That is why each complies perfectly when done individually. > The error appears when the code for the movement (tha

RE: Variables and Bookpart

attention is appreciated.’ Mark From: Jean Abou Samra [mailto:j...@abou-samra.fr] Sent: Sunday, March 12, 2023 11:23 AM To: Mark Stephen Mrotek ; lilypond-user@gnu.org Subject: Re: Variables and Bookpart Le dimanche 12 mars 2023 à 11:16 -0700, Mark Stephen Mrotek a écrit : Hello

Re: Variables and Bookpart

Le dimanche 12 mars 2023 à 11:16 -0700, Mark Stephen Mrotek a écrit : > Hello, >   > Each movement of a piano piece has a separate file. In each movement the > various voices are identified by a variable, e.g., ArightOne, BleftTwo. Each > file compiles perfectly individually. > When the fil

Re: Variables

Euler: ... > PartMfluteVoiceOne = \relative fis' { > \clef "treble" \key d \major \time 3/4 > d'2 ^"Menuetto" e8( d) } ... You can use text marks (see the notation manual) or something like: /// file a.ily ma = { d'2 e } mb = { fis2 g } men = \markup{ Menuetto } Men = { s2^\men s } //

Re: Variables

The syntax of music functions has changed between version 2.18.2 and 2.19.83. I recommend using the newer version, but here is the old syntax. \version "2.18.2" dacapo = #(define-music-function (parser location dc) (string?) #{   \once \override Score.RehearsalMark.break-visibility = #end-of-l

Re: Variables

Hello Timothy, here is the compilation i got: ( version 2.18.2) # -*-compilation-*- Traitement de « E:/Users/christophe/CloudStation/cgyproduction/produits/Catalogue/Sources/JC Bach/Sonate1-score.ly » Analyse... E:/Users/christophe/CloudStation/cgyproduction/produits/Catalogue/Sources/JC Bach/Son

Re: Variables

Hello Karl, let me give you the full context: in the code file I have the music code sonate.ly contains PartMfluteVoiceOne = \relative fis' { \clef "treble" \key d \major \time 3/4 d'2 ^"Menuetto" e8( d) } PartMViolinVoiceOne = \relative fis' { \clef "treble" \key d \major

Re: Variables

On 02/06/2019 14:36, Euler wrote: Hello, I'm looking for a way to get some markup in variables. in parts i would like to get the markup printed, but only once in scores. here is attached an example in score mode where i would like "Menuetto da Capo" printed only in the lower voice.

Re: Variables

Christophe: ... > I'm looking for a way to get some markup in variables. See notation manual 1 Musical notation 1.8 Text 1.8.2 Formatting text Text markup introduction just before the See also. > in parts i would like to get the markup printed, but only once in scores. Markups only happens o

Re: variables for specific kinds of markup?

"Marc Evanstein" writes: > Thanks so much – changing it to define-event-function worked > perfectly. Is a markup considered an "event" rather than "music"? No. But ^\markup ... is. > Was define-music-function somehow returning that event attached to > empty music or something? The decision wh

Re: variables for specific kinds of markup?

Thanks so much – changing it to define-event-function worked perfectly. Is a markup considered an "event" rather than "music"? Was define-music-function somehow returning that event attached to empty music or something? At any rate, glad to hear that this is getting simpler in the near future, a

Re: variables for specific kinds of markup?

"Marc Evanstein (formerly Evans)" writes: > Hi all, > > I'm trying to create a variable to handle a certain type of markup > text. For instance, I'd like percussion strikings to be in small caps > above the staff, and what I really want is to define some sort of > macro that replaces all instance

Re: variables for numbers

On Thu, May 10, 2018 at 3:01 PM, Thomas Morley wrote: > 2018-05-10 22:51 GMT+02:00 Flaming Hakama by Elaine < > ela...@flaminghakama.com>: > > > > On Tue, May 1, 2018 at 11:03 AM, wrote: > >> > >> Send lilypond-user mailing list submissions to > >> lilypond-user@gnu.org > > > > > > > > I

Re: variables for numbers

Thomas Morley-2 wrote > raiseDistance = #1.3 > \markup \raise #raiseDistance { \italic "sotto voce" } Much easier! ... and better! I should upgrade some of my codes... -- Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html ___ lilypond-use

Re: variables for numbers

2018-05-10 22:51 GMT+02:00 Flaming Hakama by Elaine : > > On Tue, May 1, 2018 at 11:03 AM, wrote: >> >> Send lilypond-user mailing list submissions to >> lilypond-user@gnu.org > > > > I'm having difficulty understanding how to use a variable that stores a > number, for use with a \raise co

Re: variables for numbers

I don't know if it is the easier way, but I'd do: #(define-markup-command (raiseDistance layout props text) (markup?) (interpret-markup layout props #{ \markup { \raise #1.3 #text } #})) sottoVoce = <>^\markup \raiseDistance {

Re: Variables and Repetition

On 03/25/2018 02:59 AM, David Kastrup wrote: John A writes: Hi all, I just got started using Lilypond with Frescobaldi, and I'm having a great time. I have been trying to organize the music with variables to make things more efficient, and I am running into a little bit of trouble. This is

Re: Variables and Repetition

John A writes: > Hi all, > > I just got started using Lilypond with Frescobaldi, and I'm having a > great time. I have been trying to organize the music with variables to > make things more efficient, and I am running into a little bit of > trouble. This is what happens: I have a repeated figure,

Re: Variables and Repetition

On 25/03/18 04:13, John A wrote: > I am entering the notes in relative mode, and when I engrave the score, > if the ending notes of the figure are too high or low, on the second > repetition the whole figure will be an octave too high or too low. On > the next repetition, it goes an octave higher o

Re: variables in \book { }

>> I don’t think that not having a proper >> scope for each book/bookpart is a problem. > > I think it is. > >> So I’d vote for this change. > > I vote against it. It does not make sense that when I write I would also say, without its own scope there is little gain and it will just lead to mor

Re: variables in \book { }

Simon Albrecht writes: > On 17.02.2016 13:27, David Kastrup wrote: >> Graham King writes: >> >>> >>>\book { >>> music = \relative { c' d e f } >>> \score { >>> \music >>> } >>>} >> The problem is that it would likely be

Re: variables in \book { }

On 17.02.2016 13:27, David Kastrup wrote: Graham King writes: \book { music = \relative { c' d e f } \score { \music } } The problem is that it would likely be possible to teach LilyPond's parser to accept the latter,

Re: variables in \book { }

Graham King writes: > On Wed, 2016-02-17 at 10:58 +0100, David Kastrup wrote: > >> The problem with the repeated use of "I've tried that" is that nobody >> can really guess just _what_ exactly you have tried with what error >> messages as the result. And nobody can try reproducing or debugging o

Re: variables in \book { }

On Wed, 2016-02-17 at 10:58 +0100, David Kastrup wrote: > Graham King writes: > > > Thanks Ben, > > that will be useful once I've found a solution to the immediate problem: > > defining and using a variable within \book{} or \bookpart{} or > > \book[part]{ \score { }} > > > > \version "

Re: variables in \book { }

... better to use define-void-function %%% snip %%% pdefine = #(define-void-function (sym val)(symbol? scheme?) (ly:parser-define! sym val)) %%% snip %%% Cheers Jan-Peter Am 17.02.2016 um 10:56 schrieb Jan-Peter Voigt: > Hi Graham, > > I didn't went through the whole thread, but IIUC, the probl

Re: variables in \book { }

Graham King writes: > Thanks Ben, > that will be useful once I've found a solution to the immediate problem: > defining and using a variable within \book{} or \bookpart{} or > \book[part]{ \score { }} > > \version "2.19.35" > \book { > music = \relative { c' d e f } >

Re: variables in \book { }

Hi Graham, I didn't went through the whole thread, but IIUC, the problem is about defining variables inside a pair of braces. Sometimes I use a helper function to define variables: %%% snip %%% \version "2.19.35" % a little helper function using ly:parser-define! pdefine = #(define-scheme-functi

Re: variables in \book { }

On Tue, 2016-02-16 at 19:27 -0500, Ben Strecker wrote: > Graham, > > > > Have you tried putting each score inside it’s own \bookpart? > > > The documentation for ragged-last-bottom says: > > > ragged-last-bottom > > > > If this is set to false, then the last page,

Re: variables in \book { }

Graham, Have you tried putting each score inside it’s own \bookpart? The documentation for ragged-last-bottom says: ragged-last-bottom <> <>If this is set to false, then the last page, and the last page in each section created with a \bookpart block, will be vertically justified in the same w

Re: variables in \book { }

On Wed, 2016-02-17 at 00:20 +0100, David Kastrup wrote: > Graham King writes: > > > On Tue, 2016-02-16 at 19:15 +0100, David Kastrup wrote: > > > > > >> > >> However, your original posting stated: > >> > >> > (Alternatively, if there's a way to make book-titling.ily do a > >> > ragged-last-bo

Re: variables in \book { }

Graham King writes: > On Tue, 2016-02-16 at 19:15 +0100, David Kastrup wrote: > > >> >> However, your original posting stated: >> >> > (Alternatively, if there's a way to make book-titling.ily do a >> > ragged-last-bottom for each piece, that would save even more work). >> >> Have you actuall

Re: variables in \book { }

On Tue, 2016-02-16 at 19:15 +0100, David Kastrup wrote: > > However, your original posting stated: > > > (Alternatively, if there's a way to make book-titling.ily do a > > ragged-last-bottom for each piece, that would save even more work). > > Have you actually tried > > \layout { > ragged-

Re: variables in \book { }

Graham King writes: > On Tue, 2016-02-16 at 18:36 +0100, David Kastrup wrote: > >> Graham King writes: >> >> > oops, just found the simple fix (I think): > > > >> Have you actually _read_ your question? >> > > Yes, read the question, but failed to read the rubbish I put forward as > a "simple

Re: variables in \book { }

On Tue, 2016-02-16 at 18:36 +0100, David Kastrup wrote: > Graham King writes: > > > oops, just found the simple fix (I think): > Have you actually _read_ your question? > Yes, read the question, but failed to read the rubbish I put forward as a "simple fix". Too much going round in circles

Re: variables in \book { }

Graham King writes: > oops, just found the simple fix (I think): > > > \version "2.19.35" > > music = { \relative { c' d e f }} > > \book { > \score { > \music > } > } > > One extra pair of braces around the music

Re: variables in \book { }

oops, just found the simple fix (I think): \version "2.19.35" music = { \relative { c' d e f }} \book { \score { \music } } One extra pair of braces around the music expression. Apologies for the noise.

Re: Variables: multiple use with multiple stanza

Michael, Thank You a lot! I will use this way. I would just write a plain simple melody and whereever you need > additional lyrics just add another line of lyrics, like here > ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mai

Re: Variables: multiple use with multiple stanza

> I engrave ancient russian church music in original notation (by > \lyricmode) and common score. This is single-voice music: one score + one > string of ancient notation ( + one string of words). But SOMETIMES there > is TWO strings of ancient notation under 1-2-3 notes. There I use > construction

Re: Variables in instrumentName markup?

Hi Mark & hi Harm, Brilliant. Just what I was looking for, and instructive in two different ways. Thank you both. Trevor. On Sat, Mar 28, 2015 at 4:20 PM, Thomas Morley wrote: > 2015-03-28 20:27 GMT+01:00 Mark Knoop : > > At 14:13 on 28 Mar 2015, Trevor Bača wrote: > >>Hi, > >> > >>Is there a

Re: Variables in instrumentName markup?

2015-03-28 20:27 GMT+01:00 Mark Knoop : > At 14:13 on 28 Mar 2015, Trevor Bača wrote: >>Hi, >> >>Is there a way to do ... >> >> foo = #12 >> \new Staff \with { >> instrumentName = \markup { \hcenter-in \foo Percussion } >> } { ... } >> \new Staff \with { >> instrumentName = \marku

Re: Variables in instrumentName markup?

At 14:13 on 28 Mar 2015, Trevor Bača wrote: >Hi, > >Is there a way to do ... > > foo = #12 > \new Staff \with { > instrumentName = \markup { \hcenter-in \foo Percussion } > } { ... } > \new Staff \with { > instrumentName = \markup { \hcenter-in \foo Violin } > } { ... } > >... o

Re: Variables when compiling a book

We at Mutopia.org have been struggling with the same issues, except that we have the extra condition that each separate piece in the collection should also compile on its own. You can see our "flayelings" here: https://github.com/ksnortum/mp-sandbox Knute Snortum (via Gmail) On Tue, Feb 3, 2015

Re: Variables when compiling a book

On 02/03/2015 08:58 AM, John McWilliam wrote: > You may be right in which case I will have to study your construct > and apply it to my Piobaireachd tunes, however, I was hoping for a > simpler solution. If you cannot see one then I suppose I must bite > the bullet but I'm not very code literate

Re: Variables when compiling a book

>Unfortunately, this is one of the cases where LilyPond use resembles >other kinds of computer programming. You’ll need to refactor your files... This solution presented a completely new mind set for me. The problem is that I already have a considerable collection of bagpipe tunes written without

Re: Variables when compiling a book

On 02/02/2015 02:34 PM, John McWilliam wrote: > I am compiling a collection of bagpipe tunes and am having a problem > when the individual files are to be compiled into a book. Many of the > tunes have sections of music defined in variables - these definitions > lie outside the \score context and a

Re: Variables when compiling a book

> On 2 Feb 2015, at 21:34, John McWilliam wrote: > > I am compiling a collection of bagpipe tunes and am having a problem when the > individual files are to be compiled into a book. Many of the tunes have > sections of music defined in variables - these definitions lie outside the > \score conte

Re: Variables as variables

Janek Warchoł writes: > I think this snippet may be interesting to you > https://github.com/openlilylib/snippets/blob/master/input-shorthands/late-evaluation-of-variables.ly It is, indeed... Thanks! Now, why can this snippet not be found when searching for "lazy evaluation" and "late evaluation

Re: Variables as variables

Josiah Boothby writes: > Would not a more canonical way be to use tags? Not as elegant maybe, > but: > > aaa = { > \tag #'first { c4 d e f } > \tag #'second { f4 e d c } > } > > bbb = { > a4 a a a > s4*4 > b4 b b b > } > > \score { << \bbb { s4*4 \keepWithTag #'first \aaa } >> } >

Re: Variables as variables

On Mon, 20 Jan 2014 16:00:59 +0100 Johan Vromans wrote: > Now I want to re-use bbb with a different value of aaa. Like a real > variable as known from other programming languages. > > aaa = { c4 d e f } > bbb = { a4 a a a \aaa b4 b b b } > \score { \bbb }% a4 a a a c4 d e f b4 b b b >

Re: Variables as variables

2014/1/20 Johan Vromans : > In LilyPond terms, in > > namedMusic = { ... } > > 'namedMusic' is called a variable, identifier or macro. > > Normal LilyPond behaviour is > > aaa = { c4 d e f } > bbb = { a4 a a a \aaa b4 b b b } > \score { \bbb } > > This produces { a4 a a a c4 d e f b4 b b b

Re: Variables as variables

"Phil Holmes" writes: > - Original Message - > From: "David Kastrup" > To: "Johan Vromans" > Cc: > Sent: Monday, January 20, 2014 3:23 PM > Subject: Re: Variables as variables > > > >> That's not "like

Re: Variables as variables

- Original Message - From: "David Kastrup" To: "Johan Vromans" Cc: Sent: Monday, January 20, 2014 3:23 PM Subject: Re: Variables as variables That's not "like a real variable as known from other programming language". If I write aaa = 3 bbb =

Re: Variables as variables

Johan Vromans writes: > In LilyPond terms, in > > namedMusic = { ... } > > 'namedMusic' is called a variable, identifier or macro. > > Normal LilyPond behaviour is > > aaa = { c4 d e f } > bbb = { a4 a a a \aaa b4 b b b } > \score { \bbb } > > This produces { a4 a a a c4 d e f b4 b b b }

Re: variables tied with slurs

Indeed that works! Awesome! Thanks! On Sep 27, 2013, at 3:46 AM, Peter Bjuhr wrote: > > On 09/27/2013 07:05 AM, Urs Liska wrote: >> Does >> >> A = \drums { sn8 sn8~ } >> >> { \A \A } >> >> Do what you want? > > I was curious of this, but Urs is right it does work. There are no obstacles >

Re: variables tied with slurs

This is an interesting approach and it seems like I should be able to do what I want with it... I'm not entirely sure I understand why it works though, why the simultaneous rests create the tie on the snares ? I'm too new to both lilypond and music so please forgive my naiveness. I would just n

Re: variables tied with slurs

Not exaclty, that puts the A patternse in different staffs and there is no tie between them... Thanks for the response though, and sorry it took me so long to get back to this. On Sep 27, 2013, at 12:05 AM, Urs Liska wrote: > Does > > A = \drums { sn8 sn8~ } > > { \A \A } > > Do what you w

Re: variables tied with slurs

On 09/28/2013 01:41 PM, David Kastrup wrote: That's because each \A is in a Voice of its own. Use an explicit Voice to avoid independent implicit voices for each \A: That's good to know! Thanks! If I may add another more realistic yet hypothetical example. The following works. If the ties c

Re: variables tied with slurs

Peter Bjuhr writes: > On the other hand, this doesn't work: > > \version "2.17.28" > > A = \relative c'' {a4 b c a ~ } > > \score { > \new Staff > { \A \A } > } That's because each \A is in a Voice of its own. Use an explicit Voice to avoid independent implicit voices for each \A: \score {

Re: variables tied with slurs

On 09/28/2013 08:49 AM, Urs Liska wrote: \version "2.17.26" % How could I write the equivalent of \drums { sn8 sn8 ~ sn8 sn8 } %using variables? % This does work! A = \drummode { sn8 sn8 ~ } \score { \new DrumStaff { \A \A } } %end with a tie { b'4 a' g' b' ~ } Best Peter Thanks. I didn

Re: variables tied with slurs

Am 27.09.2013 10:46, schrieb Peter Bjuhr: On 09/27/2013 07:05 AM, Urs Liska wrote: Does A = \drums { sn8 sn8~ } { \A \A } Do what you want? I was curious of this, but Urs is right it does work. There are no obstacles in ending with a tie. Apparently it is just ignored: \version "2.17.26

Re: variables tied with slurs

On 09/27/2013 07:05 AM, Urs Liska wrote: Does A = \drums { sn8 sn8~ } { \A \A } Do what you want? I was curious of this, but Urs is right it does work. There are no obstacles in ending with a tie. Apparently it is just ignored: \version "2.17.26" % How could I write the equivalent of \d

Re: variables tied with slurs

Hello Alexander, the \drums command implicitly creates a new DrumStaff, so I recommend using \drummode for this purpose. If you have basic patterns, which shall receive "random" ties, you can create SimultaneousMusic with a << >> construct and overlay the patterns with the needed ties: --sni

Re: variables tied with slurs

Does A = \drums { sn8 sn8~ } { \A \A } Do what you want? Alexander Wallace schrieb: >Hi all, > >For study purposes, i want to do 128 rithmic patterns composed of 7 >basic rithmic patterns combined via a tie. > >Rather than writing the 128 patterns separately I'd love to write the >basic 7 a

Re: Variables: structure vs layout

At Thu, 15 Mar 2012 21:57:35 +0100, Janek Warchoł wrote: > > On Thu, Mar 15, 2012 at 4:35 PM, James Harkins wrote: > > I'm getting a bit confused about the use of variables to reflect the > > structure of the music, or the distribution of notes between different > > voices etc. > > > > After it

Re: Variables: structure vs layout

El 15/03/2012 16:35, "James Harkins" escribió: > I guess it's a fairly vague question. I guess the best way to narrow it down is -- especially asking experienced users -- what level of "atomization" seems to work the best for variables? I'd use a variable for each voice undoubtedly. Use spacing

Re: Variables: structure vs layout

On Thu, Mar 15, 2012 at 4:35 PM, James Harkins wrote: > I'm getting a bit confused about the use of variables to reflect the > structure of the music, or the distribution of notes between different voices > etc. > > The passage where I'm struggling with this right now is for one instrument*. >

Re: Variables syntax problem

> > I got another problem I am not able to solve. I change the title of the > > header so that the tempo is included, see attached file. This works > > nicely, but I have not been able to substitute the duration in the \note > > declaration by some variable, i.e. I'd like to be able to do something

Re: Variables syntax problem

On 18/02/11 01:43, Matthias Hüsken wrote: Dear all, I got another problem I am not able to solve. I change the title of the header so that the tempo is included, see attached file. This works nicely, but I have not been able to substitute the duration in the \note declaration by some variable, i

Re: variables

On 24.11.2009, at 02:02, Frank Steinmetzger wrote: Am Montag, 23. November 2009 schrieb Hugh Myers: Given: eMinor = < e b gis e b e, > I'd like to be able to do something like \eMinor' since I'm working in relative mode. Is this possible. Same thing for chord length, i.e. \eMinor2. et

Re: variables

eMinor=\relative c { ... } does not allow either eMinor' or eMinor, etc. --hsm On Mon, Nov 23, 2009 at 6:02 PM, Frank Steinmetzger wrote: > Am Montag, 23. November 2009 schrieb Hugh Myers: >> Given: >> >> eMinor = < e   b  gis  e b e, > >> >> I'd like to be able to do something like \eMinor' sin

Re: variables

Am Montag, 23. November 2009 schrieb Hugh Myers: > Given: > > eMinor = < e b gis e b e, > > > I'd like to be able to do something like \eMinor' since I'm working in > relative mode. Is this possible. Same thing for chord length, i.e. > \eMinor2. etc. AFAIK: eMinor=\relative c { < e b gis e b

Re: variables in lilypond-book

> Can we use variable options for lilypond-book? No. lilypond-book only handles the \lilypond... commands and the `lilypond' environment, nothing else. Werner ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinf