RE: Re: Variable binding breaks layout

Thank you for the explanation. Juergen.

Re: Variable binding breaks layout

Le jeudi 11 mai 2023 à 06:26 +, juergen.gr...@xyz.de a écrit : > Hello all, > > > why does each of the out commented lines break the layout when active? And > why does "(brace-Y..." not? What breaks the layout is not the variable bindings per se of course, but the ly:grob-property calls,

Re: Variable equivalent in Scheme

On 2019-11-09 5:37 pm, Freeman Gilmore wrote: If: traLaLa = { c'4 d'4 } How would I write this in Scheme? #(define traLaLa ?) You can quote LilyPond syntax within Scheme using the #{ #} tokens: #(define traLaLa #{ { c'4 d'4 } #}) You can also define music purely in Sc

Re: variable of type finger

Gianmaria Lari writes: > On Mon, 25 Jun 2018 at 22:44, David Kastrup wrote: >> >> #(display #{ \finger "3" #}) >> >> compiles just fine even if its output is not particularly legible. >> > > The problem was " wherever you can put Scheme expressions" I tried > to use it where lilypond expects

Re: variable of type finger

On Mon, 25 Jun 2018 at 22:44, David Kastrup wrote: > Gianmaria Lari writes: > > > On Mon, 25 Jun 2018 at 15:49, David Kastrup wrote: > > > >> Gianmaria Lari writes: > >> > >> > This code define a variable containing a duration and the use it: > >> > > >> > \version "2.19.81" > >> > #(define my

Re: variable of type finger

Gianmaria Lari writes: > On Mon, 25 Jun 2018 at 15:49, David Kastrup wrote: > >> Gianmaria Lari writes: >> >> > This code define a variable containing a duration and the use it: >> > >> > \version "2.19.81" >> > #(define myDuration (ly:make-duration 4 0)) >> > { a\myDuration} >> > >> > >> > I c

Re: variable of type finger

On Mon, 25 Jun 2018 at 15:49, David Kastrup wrote: > Gianmaria Lari writes: > > > This code define a variable containing a duration and the use it: > > > > \version "2.19.81" > > #(define myDuration (ly:make-duration 4 0)) > > { a\myDuration} > > > > > > I can do something similar wit fingering:

Re: variable of type finger

Gianmaria Lari writes: > This code define a variable containing a duration and the use it: > > \version "2.19.81" > #(define myDuration (ly:make-duration 4 0)) > { a\myDuration} > > > I can do something similar wit fingering: > > \version "2.19.81" > myFinger = \finger "3" > { a\myFinger} > > > H

Re: variable and tie

Gianmaria Lari writes: > On 9 May 2018 at 10:45, David Kastrup wrote: > >> Gianmaria Lari writes: >> >> > On 13 April 2018 at 09:13, David Kastrup wrote: >> > >> >> Gianmaria Lari writes: >> >> > >> >> > At the moment I do this >> >> > >> >> > \version "2.19.81" >> >> > var = {a b \tag #'last

Re: variable and tie

On 9 May 2018 at 10:45, David Kastrup wrote: > Gianmaria Lari writes: > > > On 13 April 2018 at 09:13, David Kastrup wrote: > > > >> Gianmaria Lari writes: > >> > > >> > At the moment I do this > >> > > >> > \version "2.19.81" > >> > var = {a b \tag #'lastnote a} > >> > {\removeWithTag #'lastn

Re: variable and tie

Gianmaria Lari writes: > On 13 April 2018 at 09:13, David Kastrup wrote: > >> Gianmaria Lari writes: >> > >> > At the moment I do this >> > >> > \version "2.19.81" >> > var = {a b \tag #'lastnote a} >> > {\removeWithTag #'lastnote \var a ~ a} >> > >> > but I would like to know if there are othe

Re: variable and tie

On 13 April 2018 at 09:13, David Kastrup wrote: > Gianmaria Lari writes: > > > I would like to tie the last note contained in a variable like this > > > > \version "2.19.81" > > var = {a b a} > > {\var ~ a} > > > > but this generates an error. This is just a simple example, the reason > why > >

Re: variable and tie

Oh! I will wait for it :) Thank you David! On 13 April 2018 at 09:13, David Kastrup wrote: > Gianmaria Lari writes: > > > I would like to tie the last note contained in a variable like this > > > > \version "2.19.81" > > var = {a b a} > > {\var ~ a} > > > > but this generates an error. This is

Re: variable and tie

Gianmaria Lari writes: > I would like to tie the last note contained in a variable like this > > \version "2.19.81" > var = {a b a} > {\var ~ a} > > but this generates an error. This is just a simple example, the reason why > I would like to do this is because the variable in the real piece is us

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 writes: > > >> > > >> > I'm sorry for the trivial question but wh

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 this code is wrong? > >> > > >> > \version "2.19.80" > >> > > >>

Re: variable

On 24 November 2017 at 10:15, Werner LEMBERG wrote: > > >> 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 nee

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 does > nothing: > > \versi

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

>> 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 looks at \music > before deciding the

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} >> > \music >> > >> > >> > My understanding was that "\music" is su

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 substituted by its value "{a > b}" >

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 looks at \music before decidin

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

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 th

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 tell Lilypond to put 2 syst

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 separat

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 is

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" \language "engli

Re: Variable weirdness

I have again been trying to build up a sensible files-and-variables structure for more complex scores (e.g. orchestral pieces with several movements), and I seem once again to have run into the limitation that 'book' and 'bookpart' have no scope for variables. So I thought I would try Jan-Peter's p

Re: Variable weirdness

Thank you.  I might find this useful some time, if I have correctly understood what the purpose of it is. For the particular case I was concerned with, though, simply using #(define partName "Cello 1") seems a lot simpler. I just wondered why the Lilypond form isn't allowed in a situation where t

Re: Variable weirdness

Hello, here is a demo of the code: %%% snip \version "2.19.49" % the 2.18 version would just use parser and layout in the signature and the additional parser-argument in the ly:parser-define! call parserDefine = #(define-scheme-function (vkey val)(symbol? scheme?) (ly:parser-define! vkey v

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 in

Re: Variable weirdness

On 07.11.2016 17:56, David Kastrup wrote: David Sumbler writes: I had the following lines in the main file of my current Lilypond project: \book { \bookOutputName "../firstCello" partName = "Cello 1" \include "frontcover.ily" \bookpart { %music... The file "frontcover.ily"

Re: Variable weirdness

On Mon, 2016-11-07 at 17:56 +0100, David Kastrup wrote: > David Sumbler writes: > > > > > I had the following lines in the main file of my current Lilypond > > project: > > > > \book { > >   \bookOutputName "../firstCello" > >     partName = "Cello 1" > >     \include "frontcover.ily" > > \

Re: Variable weirdness

David Sumbler writes: > I had the following lines in the main file of my current Lilypond > project: > > \book { >   \bookOutputName "../firstCello" >     partName = "Cello 1" >     \include "frontcover.ily" > \bookpart { %music... > > The file "frontcover.ily" contains a \bookpart block whic

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 Voice << {\cC} {\cc}>>}

Re: Variable slur thickness

Thanks, Harm! On Friday, April 1, 2016, Thomas Morley-2 [via Lilypond] < ml-node+s1069038n189182...@n5.nabble.com> wrote: > 2016-03-11 21:51 GMT+01:00 Thomas Morley <[hidden email] > >: > > > 2016-03-11 14:31 GMT+01:00 Sharon Rosner <[hidden e

Re: Variable slur thickness

2016-03-11 21:51 GMT+01:00 Thomas Morley : > 2016-03-11 14:31 GMT+01:00 Sharon Rosner : >>> I've managed to bypass using before-line-breaking AND after-line-breaking >>> by assigning the function to the 'thickness property and having each grob >>> internally calculate its own control points rather

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 attachment next time, I know

Re: Variable slur thickness

2016-03-11 14:31 GMT+01:00 Sharon Rosner : >> I've managed to bypass using before-line-breaking AND after-line-breaking >> by assigning the function to the 'thickness property and having each grob >> internally calculate its own control points rather than relying on it >> being >> calculated elsewh

Re: Variable slur thickness

> I've managed to bypass using before-line-breaking AND after-line-breaking > by assigning the function to the 'thickness 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

Re: Variable slur thickness

Thomas and Sharon, On Fri, Mar 11, 2016 at 3:17 AM, Thomas Morley-2 [via Lilypond] < ml-node+s1069038n188435...@n5.nabble.com> wrote: > 2016-03-11 10:23 GMT+01:00 Sharon Rosner <[hidden email] > >: > >> This problem arose before. > >> One need

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 explain what’s going on?

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 callba

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 > beginning on the sec

Re: Variable slur thickness

> 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 beginning on the second line. Look at the slurs on bars 15-16, 17-19, 2

Re: Variable slur thickness

2016-03-11 1:18 GMT+01:00 Sharon Rosner : >> 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) >> } >> } > >

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 similar to show the problem. Lo

Re: Variable slur thickness

2016-03-11 0:29 GMT+01:00 Sharon Rosner : > 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 How should it look in situations like below? \

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-tp18837

Re: Variable slur thickness

2016-03-10 17:14 GMT+01:00 tisimst : > > On Thu, Mar 10, 2016 at 9:04 AM, Malte Meyn-3 [via Lilypond] <[hidden > email]> wrote: >> >> >> >> 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:

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 w

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

aving in-line images, I just know 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-thic

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. http://ansuz

Inline images, was Re: Variable slur thickness

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 attachment next time, I know they'll > appreciate it. :-) Why on earth would anyone filter inline image

Re: Variable slur thickness

On Thu, Mar 10, 2016 at 9:04 AM, Malte Meyn-3 [via Lilypond] < ml-node+s1069038n18838...@n5.nabble.com> wrote: > > > 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

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 h

Re: Variable slur thickness

On Thu, Mar 10, 2016 at 7:26 AM, Abraham Lee wrote: > On Thu, Mar 10, 2016 at 7:08 AM, Sharon Rosner [via Lilypond] < > ml-node+s1069038n188378...@n5.nabble.com> wrote: > >> > I was thinking about this just yesterday. Here's a reasonable solution: >> >> Fantastic! I refactored the code to make it

Re: Variable slur thickness

On Thu, Mar 10, 2016 at 7:08 AM, Sharon Rosner [via Lilypond] < ml-node+s1069038n188378...@n5.nabble.com> wrote: > > 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: > +1. Nicely refactored.

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)) (cp0 (c

Re: Variable slur thickness

Sharon, On Thu, Mar 10, 2016 at 3:02 AM, Sharon Rosner [via Lilypond] < ml-node+s1069038n18837...@n5.nabble.com> wrote: > Would there be a way to change the slur thickness in proportion to its > length, so short slurs will be thinner and longer ones will be thicker? > I was thinking about this j

Re: Variable names

"H. S. Teoh" writes: > On Thu, Jan 07, 2016 at 08:59:22PM +0100, Johan Vromans wrote: >> 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 >>

Re: Variable names

On Thu, Jan 07, 2016 at 08:59:22PM +0100, Johan Vromans wrote: > 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 becom

Re: variable containing header

On Tue, May 26, 2015 at 5:23 AM, Gianmaria Lari wrote: > I'm trying to define a variable containing the header but lilypond does not > accept it. Am'I doing some error or is this forbidden? > > % my source > \version "2.18.2" > head = \header { > title = "The Third Position" > } > > \score { >

Re: variable in scheme

Hey thanks I didn't need it after all. >>What's the intent? I never use tab so my bend file ""definitions.ily" has all the tab sections removed so it doesn't print tab- did that a long time ago. All works fine however a friend wanted to use the tab and couldn't do quarter tones. So I was going to

Re: variable in scheme

Am Mittwoch, 29. April 2015 07:21 CEST, Stephen MacNeil schrieb: > is this correct? What's the intent? > > (#'(,num)) > > (#'(,str)) No, commas (',') are only allowed within a backquoted form. Cheers, RalfD > > > thanks > > Stephen _

Re: variable in markup possible?

Am 12.02.2015 um 12:40 schrieb Noeck : www.oleschmidt.de > Hi Ole, > >> Is it possible to use a variable inside a markup > > Yes. With two modifications to your code: > 1. The definition of def must be a markup (insert \markup before the > \center-column) > 2. You have to call a variable

Re: variable in markup possible?

Hi Ole, > Is it possible to use a variable inside a markup Yes. With two modifications to your code: 1. The definition of def must be a markup (insert \markup before the \center-column) 2. You have to call a variable with a backslash (\def). The definitions of a variable is: var = … The usage of

Re: variable variables

Paul! Thank you so much! greetings, Gerjan I have to admit that I’m not working with lilypond for a long time and especially not this hardcore. > On 12 Dec 2014, at 02:26, Paul Morris wrote: > > Gerjan Piksen wrote >> I would be very very very happy with some help on this : ) > > Let me se

Re: variable variables

- Original Message - From: "Johan Vromans" To: Sent: Friday, December 12, 2014 7:15 AM Subject: Re: variable variables On Thu, 11 Dec 2014 18:29:44 -0700 (MST) Paul Morris wrote: I forgot to link to these snippets: make-connected-path-stencil http://lsr.di.unimi.it/L

Re: variable variables

On Thu, 11 Dec 2014 18:29:44 -0700 (MST) Paul Morris wrote: > I forgot to link to these snippets: > > make-connected-path-stencil > http://lsr.di.unimi.it/LSR/Item?id=891 FWIW, this snippet is missing the output of the second example (the one with the triangle and the moon). -- Johan

Re: variable variables

I forgot to link to these snippets: make-connected-path-stencil http://lsr.di.unimi.it/LSR/Item?id=891 another option: ly:make-stencil and path http://lsr.di.unimi.it/LSR/Item?id=623 -Paul -- View this message in context: http://lilypond.1069038.n5.nabble.com/variable-variables-tp169395p169

Re: variable variables

Gerjan Piksen wrote > I would be very very very happy with some help on this : ) Let me see if I can help. I think the first step is to use something besides embedded-ps. make-connected-path-stencil will be easier to work with. The following will let you set the width like you want. %%

Re: Variable length bars (Phil Holmes)

at 5:44 AM, Andrew A. Cashner wrote: > >> -- Forwarded message -- >> From: "Phil Holmes" >> To: "Patrick or Cynthia Karl" , >> Cc: >> Date: Fri, 27 Jun 2014 08:45:46 +0100 >> Subject: Re: Variable length bars >>

Fwd: Re: Variable length bars

Forgot CC … Original Message Subject: Re: Variable length bars Date: Fri, 27 Jun 2014 08:10:52 +0200 From: Malte Meyn To: Patrick or Cynthia Karl You don’t even need the \set Timing.measureLength, a \time command will do the same when you set the TimeSignature.stencil to

Re: Variable length bars

Am 27.06.2014 10:05, schrieb Urs Liska: Am 26.06.2014 23:53, schrieb Patrick or Cynthia Karl: I'm trying to set a John Dowland piece (Come Ye Heavy States of Night) which has a single initial time signature of "4/2 2/2" followed by measures that are either 4 half-note beats or 2 half-note beats

Re: Variable length bars

Am 26.06.2014 23:53, schrieb Patrick or Cynthia Karl: I'm trying to set a John Dowland piece (Come Ye Heavy States of Night) which has a single initial time signature of "4/2 2/2" followed by measures that are either 4 half-note beats or 2 half-note beats long, in quasi-random fashion. It's c

Re: Variable length bars

On 27/06/2014, at 9:53 am, Patrick or Cynthia Karl wrote: > I'm trying to set a John Dowland piece (Come Ye Heavy States of Night) which > has a single initial time signature of "4/2 2/2" followed by measures that > are either 4 half-note beats or 2 half-note beats long, in quasi-random > fash

Re: Variable length bars

- Original Message - From: "Patrick or Cynthia Karl" To: Sent: Thursday, June 26, 2014 10:53 PM Subject: Variable length bars I'm trying to set a John Dowland piece (Come Ye Heavy States of Night) which has a single initial time signature of "4/2 2/2" followed by measures that are

Re: Variable names?

On 19 Nov 2012, at 22:16 , David Kastrup wrote: "Christopher R. Maden" writes: On 11/18/2012 05:26 PM, David Kastrup wrote: At the current point of time, the rule is that "alphabetic" is a-z, A-Z, and _any_ non-ASCII character. This is a bit excessive, but short of a reliable "is a letter"

Re: Variable names?

"Christopher R. Maden" writes: > On 11/18/2012 05:26 PM, David Kastrup wrote: >> At the current point of time, the rule is that "alphabetic" is a-z, >> A-Z, and _any_ non-ASCII character. This is a bit excessive, but >> short of a reliable "is a letter" test, this was easiest to >> implement. >

Re: Variable names?

On 11/18/2012 05:26 PM, David Kastrup wrote: At the current point of time, the rule is that "alphabetic" is a-z, A-Z, and _any_ non-ASCII character. This is a bit excessive, but short of a reliable "is a letter" test, this was easiest to implement. Getting off-topic for -user, but... Most pro

Re: Variable names?

Thomas Morley writes: > 2012/11/18 Wim van Dommelen : >> >> My question: Is this use of different (utf8) characters supported "by >> accident", or on purpose? I would welcome this change but not when it >> can be broken in the future. And if "yes" can someone update the >> documentation to provid

Re: Variable names? (was: Re: Adding 3-column section to score)

2012/11/18 Wim van Dommelen : > Hi Harm, and others, > > I wondered in this discussion what you were exactly trying to achieve, so I > copied your code and compiled it. Very nice! > > And after the copy I saw a weird thing (nothing to do with this specific > example!): You use "non-standard" charac

Re: Variable assignment in music functions

Le 03/11/2011 20:02, David Kastrup disait : \paper { tocname = "Inhaltsverzeichnis" } #(define-markup-command (toc layout props) () (interpret-markup layout props (ly:output-def-lookup layout 'tocname "none"))) \markup \toc But the list is a bit longer (cf. enclosure) I first def

Re: Variable assignment in music functions

Le 03/11/2011 20:02, David Kastrup disait : Jean-Charles Malahieude writes: Le 03/11/2011 19:02, Michael Ellis disait : This allows me to do \set midiInstrument = #(cueInstrument 'get) in my cueNotes and similar functions and the choice of instruments can be set within the .ly file by

Re: Variable assignment in music functions

Jean-Charles Malahieude writes: > Le 03/11/2011 19:02, Michael Ellis disait : >> This allows me to do >> >> \set midiInstrument = #(cueInstrument 'get) >> >> in my cueNotes and similar functions and the choice of instruments can >> be set within the .ly file by >> >> #(setMainCueClapIn

Re: Variable assignment in music functions

Le 03/11/2011 19:02, Michael Ellis disait : Thanks for the suggestion, Jean-Charles. I think I've now got a solution that's fairly satisfactory: In my include file, I now have: %-- #(define (make-named-instrument default-name) (define

Re: Variable assignment in music functions

On Thu, Nov 3, 2011 at 12:04 PM, David Kastrup wrote: > Michael Ellis writes: > >> What's the right way to define a function that assigns string values >> to LilyPond variables? I'm trying to create a function in an include >> file that allows me to assign different values to variables used as >>

Re: Variable assignment in music functions

Michael Ellis writes: > What's the right way to define a function that assigns string values > to LilyPond variables? I'm trying to create a function in an include > file that allows me to assign different values to variables used as > midi instrument specifiers. > %--

Re: Variable names

Richard Sabey hotmail.co.uk> writes: > Carl Sorensen wrote: >> The core problem is -- how do you distinguish between a2 c (two notes) >> and a2c (you want it to be a variable) - currently it will be two notes. > > I might have missed something here, but: > in what circumstances can a pitch-name

Re: Variable names

David Kastrup gnu.org> writes: > > Richard Sabey hotmail.co.uk> writes: > > > in what circumstances can a > > pitch-name and a variable-name both be legal? > > > > Inside a music expression, if it comes immediately after a backslash, > > it can't be a pitch-name, and if it doesn't come immediat

Re: Variable names

Richard Sabey writes: > Carl Sorensen wrote: >>The core problem is -- how do you distinguish between a2 c (two > notes) and >>a2c (you want it to be a variable) - currently it will be two notes. > > I might have missed something here, but: in what circumstances can a > pitch-name and a variable-n

RE: Variable names

Carl Sorensen wrote: >The core problem is -- how do you distinguish between a2 c (two notes) and >a2c (you want it to be a variable) - currently it will be two notes. I might have missed something here, but: in what circumstances can a pitch-name and a variable-name both be legal? Inside a musi

Re: Variable names

On 13 May 2011, at 16:05, Carl Sorensen wrote: I have tried to find some description of the valid syntax of LilyPond variables and haven't found any. I would like to use variable names with numbers and possibly with underscores - is it somehow possible? >>> >>> Unfortunately, no. >

Re: Variable names

On 5/13/11 7:08 AM, "Janek Warchoł" wrote: > 2011/5/13 Carl Sorensen >> >> On 5/13/11 4:32 AM, "Jakub Pavlík" wrote: >> >>> I have tried to find some description of the valid syntax of LilyPond >>> variables and haven't found any. I would like to use variable names with >>> numbers and pos

  1   2   >