Re: Conditional code in the midi block

Thank you all for your suggestions. I finally have the flag working after years of just editing my master file when I wanted one track per voice! Thanks, Carolyn > On May 20, 2024, at 6:09 AM, Jean Abou Samra wrote: > >  >> nostaffmidi = >> #(define-scheme-function () () >> (if TrackPerVoic

Re: Conditional code in the midi block

Jean Abou Samra writes: > Alternatively, you can do it more like you were envisioning, but for > technical reasons, you have to start the Scheme code with $ , not # , > and you also have to include an extra \midi { } around the \context > blocks (basically because \context outside \layout or \mid

Re: Conditional code in the midi block

Am So., 19. Mai 2024 um 21:28 Uhr schrieb Carolyn Beeton : > > I would like to include some Staff and Voice context settings in the \midi > block only if a flag is set to ##t and I have not been able to figure out how > to do this. When I try to wrap the \context blocks in a code block with > #

Re: Conditional code in the midi block

> nostaffmidi = > #(define-scheme-function () () >(if TrackPerVoice #{ \context { \Staff \remove "Staff_performer" } #})) Ah, that proves me wrong. I didn't recall the parser was smart enough for this. > Although, I don't understand why the contents of the scheme functions cannot > be pla

Re: Conditional code in the midi block

> I would like to include some Staff and Voice context settings in the > \midi block only if a flag is set to ##t and I have not been able to > figure out how to do this.  When I try to wrap the \context blocks > in a code block with #{…#} I get this error: > trackPerVoiceMWE.ly:31:16: error: synt

Re: Conditional code in the midi block

On 19/05/2024 20:27, Carolyn Beeton wrote: I would like to include some Staff and Voice context settings in the \midi block only if a flag is set to ##t and I have not been able to figure out how to do this. When I try to wrap the \context blocks in a code block with #{…#} I get this error: t

Re: Conditional markup? UP|DOWN

Thank you so much Aaron, How could I have *never* used chain-assoc-get. I've read the docs about it since then. I also used (display props) to know what was available (which by itself was instructing). Again, I'm very grateful for your help. Le lun. 29 avr. 2024, à 12 h 43, Aaron Hill a écrit :

Re: Conditional markup? UP|DOWN

On 2024-04-29 7:50 am, Pierre-Luc Gauthier wrote: Can a markup command introspect its direction ? Is it possible to set in a markup command some conditionals (not paper related) ? \version "2.25.15" #(define-markup-command (conditionalMrkp layout props) () (interpret-markup layout props

Re: Conditional Complilation

THanks to all who have offered ideas. I think the "bookpart" approach will be quite effective for me. I sincerely appreciate both the competence and the willingness to share of this fantastic community. Ken Ledeen Mobile: 617-817-3183 www.nevo.com www.bitsbook.com tiny.cc/KenLedeen

Re: Conditional Complilation

On Tue, Nov 14, 2023 at 9:21 PM Vaughan McAlley wrote: > On Wed, 15 Nov 2023 at 12:09, Ken Ledeen wrote: > >> Hi All, >> >> From time to time I would like to include / exclude portions of the total >> score. >> >> ... > > Hi Ken, > > For big projects I use something like this. You change a str

Re: Conditional Complilation

On Tue, Nov 14, 2023 at 8:09 PM Ken Ledeen wrote: > Hi All, > > From time to time I would like to include / exclude portions of the total > score. For now, in the crudest of ways, I just comment out the parts I > don't want (%{ . %}). That works, of course, but I was wondering if > there was

Re: Conditional Complilation

On Wed, 15 Nov 2023 at 12:09, Ken Ledeen wrote: > Hi All, > > From time to time I would like to include / exclude portions of the total > score. For now, in the crudest of ways, I just comment out the parts I > don't want (%{ . %}). That works, of course, but I was wondering if > there was a

Re: Conditional Complilation

On 2023-11-14 17:07, Ken Ledeen wrote: Hi All, From time to time I would like to include / exclude portions of the total score. For now, in the crudest of ways, I just comment out the parts I don't want (%{ . %}).  That works, of course, but I was wondering if there was a more elegant w

Re: Conditional Definitions

After some searching, I’ve found that Scheme has the define-once construct which does exactly what I was looking for ✝✝ Fr. Samuel, OSB (R. Padraic Springuel) St. Anselm’s Abbey 4501 South Dakota Ave, NE Washington, DC, 20017 202-269-2300 (c) 202-853-7036 PAX ☧ ΧΡΙΣΤΟΣ >

Re: Conditional Definitions

> Le 15 févr. 2023 à 20:55, Fr. Samuel Springuel a > écrit : > > I recently upgraded from 2.22 to 2.24 and have run into some problems with > one of my tools. The tool is set up to define some some stuff (in the > example attached below I’ve narrowed it down to be just a color), but only i

Re: Conditional fermata padding

Thank you very much, Lukas! Well, I didn't want to bother so much with more conditions. They are namely: only sharp accidentals and only notes starting from the fourth line and higher when the stem is down. For my use case I would just add those extra conditions in abjad. The reason why we have now

Re: Conditional fermata padding

Hi Martín, Am 08.09.22 um 10:52 schrieb Martín Rincón Botero: I would like to have less padding for a fermata when a note has an accidental. Say, if the fermata has a padding of x, I would like it be x-0.1 or so when the note in question has an accidental. I would be thankful for a snippet :-)

Re: Conditional segmentation faults

Thank you for these responses. Before I received them, I had already done a little more work on my score. After all, I knew that I could work around the seg. fault problem by issuing the lilypond command in a terminal, rather than from within emacs. So I reinstated the viola line, which was prev

Re: Conditional segmentation faults

I was also getting occasional seg. faults with 21.1.4. I would add a little more to the code and they would go away. Since I was able to finish that project I didn’t worry about it and it certainly worth the trouble to try too create a MWE. I also use Emacs but I just alt-tab to another shell

Re: Conditional segmentation faults

Hi David, That certainly is strange behaviour. A segmentation fault occurs when a program tries to access a segment of memory that it isn't allowed to. It's usually the result of memory bugs in the program. If it's a bug in emacs, which looks possible, then I am not sure what you will be able to d

Re: conditional breaks

Hi Urs, I changed the conditional breaks target to "manuscript-breaks" to make sure there wasn't a conflict but the breaks package is still not working (at all). I get no errors but also no breaks. Updated MWE attached. Craig On 20 February 2018 at 20:20, Urs Liska wrote: > Hi Craig, > > Am

Re: conditional breaks

Hi Craig, Am 20.02.2018 um 11:14 schrieb Craig Dabelstein: Hi all, I'm trying to get the edition engraver, scholarly and conditional breaks all to work at the same time. In the MWE I've attached, the edition engraver and scholarly are working but I can't seem to get the conditional breaks t

Re: Conditional paper block

In Frescobaldi you can choose the Engrave (custom) option which lets you add to the command line, and remembers the last used setting. I'd never noticed that option. However, after trying it I don't like that it pulls up the dialog each time. This slows me down because it requires me to inte

Re: Conditional paper block

In Frescobaldi you can choose the Engrave (custom) option which lets you add to the command line, and remembers the last used setting. But I think your solution is better. Best, Edward -- Dr. Edward Neeman Adjunct Instructor, South Georgia State College Collaborative Pianist, Valdost

Re: Conditional paper block

Absent a way to make Frescobaldi apply the command-line argument, I came up with the following solution: To the lyluatex preamble I added a flag which indicated the use of lyluatex (similar to what lilypond-book does): #(define inside-lyluatex #t) This change has been merged into the

Re: Conditional paper block

On Tue 12 Dec 2017 at 13:34:18 (-0500), Br. Samuel Springuel wrote: > On 2017-12-12 12:08 PM, David Wright wrote: > >You can set the default paper-size with a -d option in the LP command > >line. See p10 of the "Usage" manual (2.19.80 page ref.). > > That works perfect from the command line. Is i

Re: Conditional paper block

On 2017-12-12 12:08 PM, David Wright wrote: You can set the default paper-size with a -d option in the LP command line. See p10 of the "Usage" manual (2.19.80 page ref.). That works perfect from the command line. Is it possible to get Frescobaldi to apply this option when running LilyPond? I

Re: Conditional paper block

On Tue 12 Dec 2017 at 10:52:40 (-0500), Br. Samuel Springuel wrote: > I have a project in which I'm including a bunch of scores into a pdf > document using lyluatex. In the final product, lyluatex handles > figuring out what the appropriate line width is for the scores and > passes that informatio

Re: conditional when-property function not working as intended

Hi David, > But we are not talking about music functions (where the quite different > "parser location" arguments are now usually passed implicitly) but > markup commands here. Ah! That would be the source of my confusion. Thank you, Kieren. Kieren MacMillan, co

Re: conditional when-property function not working as intended

Hi David, > By not specifying a default value? I have absolutely no idea why you > put `markp' as the default-value of your call to ly:chain-assoc-get. Because this is somebody else’s code that I’m using, without (obviously) fully understanding what it does. With your hint, I believe I can now

Re: conditional when-property function not working as intended

Kieren MacMillan writes: > Hi David, > >> It's necessary for functions taking "layout props" arguments? Where >> would that cause reason for doubt? > > I thought I recalled a recent update (say, in the past 2 years) in > which those arguments were rendered unnecessary when writing certain > musi

Re: conditional when-property function not working as intended

Kieren MacMillan writes: > Hi David, > > Thank you for the helpful reply and documentation/explanation. > >> -- Function: ly:chain-assoc-get key achain default-value >> strict-checking >> Return value for KEY from a list of alists ACHAIN. If no entry is >> found, return DEFAULT-

Re: conditional when-property function not working as intended

Hi David, Thank you for the helpful reply and documentation/explanation. > -- Function: ly:chain-assoc-get key achain default-value > strict-checking > Return value for KEY from a list of alists ACHAIN. If no entry is > found, return DEFAULT-VALUE or ‘#f’ if DEFAULT-VALUE is not

Re: conditional when-property function not working as intended

Hi David, > It's necessary for functions taking "layout props" arguments? Where > would that cause reason for doubt? I thought I recalled a recent update (say, in the past 2 years) in which those arguments were rendered unnecessary when writing certain music functions — but apparently, I’m mis

Re: conditional when-property function not working as intended

Kieren MacMillan writes: > Hi all, > > Solved my own problem (I think?): the modified version (below) appears to > work as expected. > > On a related topic: I [clearly] don’t understand when “layout props” > is necessary, and when it’s not. It's necessary for functions taking "layout props" arg

Re: conditional when-property function not working as intended

Kieren MacMillan writes: > Hello all, > > In the snippet included below, I’m hoping the second line of the > scoreTitleMarkup will take no vertical space. If you comment out that line, > you’ll see that it *does* take no space, but when it’s included, so is the > 25mm spacing that is [I though

Re: conditional when-property function not working as intended

Hi all, Solved my own problem (I think?): the modified version (below) appears to work as expected. On a related topic: I [clearly] don’t understand when “layout props” is necessary, and when it’s not. Is this explained in the docs somewhere? Thanks, Kieren. SNIPPET BEGINS \version "2.1

Re: conditional include

Johan, thanks for your input. Your code put me in the right direction. I found an enhancement request has been submitted and an example is included. I get an error though. includeIfAbsent.ly:26:2: error: GUILE signaled an error for the expression beginning here # (if (not (defined? 'includeIfAbs

Re: conditional include

MarcM writes: > your function checks for arguments passed on the command line. Is there a way > to check variable like an IFDEF ? HTH, Johan ifdefined.ly Description: Binary data ifthenelse.ly Description: Binary data ___ lilypond-user mail

Re: conditional include

your function checks for arguments passed on the command line. Is there a way to check variable like an IFDEF ? I want to reduce the number of lilypond file needed to print SATB and quartets. In a quartet i have 4 voices that each includes the common header i have a file that contains all voices

Re: conditional markup

On 15/06/14 15:43, Orm Finnendahl wrote: > Hi David, > > thanks a lot for the comment. > > Am Sonntag, den 15. Juni 2014 um 16:07:01 Uhr (+0200) schrieb David Kastrup: >> A music function has to return music, period. Different music may be >> used in different contexts, but a music function cannot

Re: conditional markup

Hi David, thanks a lot for the comment. Am Sonntag, den 15. Juni 2014 um 16:07:01 Uhr (+0200) schrieb David Kastrup: > > A music function has to return music, period. Different music may be > used in different contexts, but a music function cannot return anything > but music. Maybe it would be

Re: conditional markup

Orm Finnendahl writes: > Am Sonntag, den 15. Juni 2014 um 14:26:36 Uhr (+0200) schrieb David Kastrup: >> Orm Finnendahl writes: >> Would you have preferred >> >> orm.ly:11:20: error: music function cannot return \markup \line { "Test"} > > that doesn't really matter, the problem for me was, wh

Re: conditional markup

Am Sonntag, den 15. Juni 2014 um 14:26:36 Uhr (+0200) schrieb David Kastrup: > Orm Finnendahl writes: > Would you have preferred > > orm.ly:11:20: error: music function cannot return \markup \line { "Test"} that doesn't really matter, the problem for me was, whether the error message meant "mus

Re: conditional markup

Orm Finnendahl writes: > Hi, > > Am Samstag, den 14. Juni 2014 um 16:56:36 Uhr (+0200) schrieb David Kastrup: >> Notice the - before the markup, turning this into a post-event. > > Thanks, that was the missing link. I had tried define-event-function > and got stuck as it appeared to be pre-event.

Re: conditional markup

Hi, Am Samstag, den 14. Juni 2014 um 16:56:36 Uhr (+0200) schrieb David Kastrup: > Notice the - before the markup, turning this into a post-event. Thanks, that was the missing link. I had tried define-event-function and got stuck as it appeared to be pre-event. BTW: This meaning of the error mes

Re: conditional markup

Orm Finnendahl writes: > Hi, > > for defining markups which appear selectively either only in the > parts or only in the score I'm trying to use the following strategy: > > I include a "score-defs.ly" or "part-defs.ly" file in the score or > part respectively and define commands like "sMarkup" f

Re: conditional markup

Am Samstag, den 14. Juni 2014 um 14:17:44 Uhr (+0100) schrieb Phil Holmes: > Had you considered using tags instead? No, thanks, I wasn't aware of this. Seems to be exactly what I need. -- Orm ___ lilypond-user mailing list lilypond-user@gnu.org https:/

Re: conditional markup

- Original Message - From: "Orm Finnendahl" To: Sent: Saturday, June 14, 2014 2:07 PM Subject: conditional markup Hi, for defining markups which appear selectively either only in the parts or only in the score I'm trying to use the following strategy: I include a "score-defs.ly" or

Re: conditional \when-property

Hi David, > the ly:make-stencil in your function is unneccesary. All you need to do is > the following: > > #(define-markup-command (when-property layout props symbol markp) (symbol? > markup?) > (if (chain-assoc-get symbol props) > (interpret-markup layout props markp) > empty-

Re: conditional \when-property

Hi Kieren, On Wed, Jul 31, 2013 at 5:59 PM, Kieren MacMillan < kieren_macmil...@sympatico.ca> wrote: > Hi David, > > > Using empty-stencil rather than your own call of ly:make-stencil should > > work for more versions. > > This sounds useful… but I don't quite know what you are suggesting I do.

Re: conditional \when-property

Hi David, > Using empty-stencil rather than your own call of ly:make-stencil should > work for more versions. This sounds useful… but I don't quite know what you are suggesting I do. Do you mean this (which appears to work, but still uses ly:make-stencil): #(define-markup-command (when-property

Re: conditional \when-property

Kieren MacMillan writes: > Hi all, > > Found the correct solution (I think): > > #(define-markup-command (when-property layout props symbol markp) (symbol? > markup?) > (if (chain-assoc-get symbol props) > (interpret-markup layout props markp) > (ly:make-stencil '() empty-interval emp

Re: conditional \when-property

Hi all, Found the correct solution (I think): #(define-markup-command (when-property layout props symbol markp) (symbol? markup?) (if (chain-assoc-get symbol props) (interpret-markup layout props markp) (ly:make-stencil '() empty-interval empty-interval))) At least that *seems* to do

Re: conditional scores

MarcM writes: > i took another look at the tag documentation and I was able to have a score > printed only under a certain condition with tag. > > music = \relative c' { > \tag #'dontPrintScore >{ > c e g c > } > } > > \score { > \keepWithTag #'inFunctions \music > } > > Thi

Re: conditional scores

i took another look at the tag documentation and I was able to have a score printed only under a certain condition with tag. music = \relative c' { \tag #'dontPrintScore { c e g c } } \score { \keepWithTag #'inFunctions \music } This works. This only inconvenient is that

Re: conditional include

Am 05.02.2013 11:07, schrieb David Kastrup: Jan-Peter Voigt writes: Hi Urs, you can write a music-function that conditionally includes files. I use a function to include a file, if it exists. The if statement can of course also test for a option with ly:get-option. \version "2.16.0" includeI

Re: conditional include

Am 05.02.2013 11:07, schrieb David Kastrup: Jan-Peter Voigt writes: Hi Urs, you can write a music-function that conditionally includes files. I use a function to include a file, if it exists. The if statement can of course also test for a option with ly:get-option. \version "2.16.0" includeI

Re: conditional include

Jan-Peter Voigt writes: > Hi Urs, > > you can write a music-function that conditionally includes files. > I use a function to include a file, if it exists. The if statement can > of course also test for a option with ly:get-option. > \version "2.16.0" > > includeIfExists = > #(define-music-funct

Re: conditional include

Hi Jan-Peter, thank you very much. This example function was actually accessible for me [other than a similar function in lalily, which is just that little amount more complex ...]. I tweaked it to my needs as can be seen in the attachment. It makes a decision depending on the presence of a -d

Re: conditional include

Hi Urs, you can write a music-function that conditionally includes files. I use a function to include a file, if it exists. The if statement can of course also test for a option with ly:get-option. Best, Jan-Peter On 04.02.2013 16:48, Urs Liska wrote: Hi list, I don't know if I _could_ f

Re: Conditional compilation

Jérôme Plût writes: > I am writing some ensemble music and want the file to compile in two > modes: with -dfull, compile all individual parts; without it, compile > only the conductor part (for debugging). This is probably a FAQ but I > cannot find an answer on the site: what is the preferred way

Re: Conditional ambitus

Thomas Morley writes: > Why use a function at all? > > \version "2.16.2" > > isAmbitus = ##f > > #(define includeAmbitus > (if isAmbitus > #{ \with { \consists "Ambitus_engraver" } #} > #{ \with { } #})) > > \score { > \new Voice = "one" \includeAmbitus {e' f' g'} > } > > Seems to

Re: Conditional ambitus

2013/1/26 David Kastrup : > Kevin Stolt writes: > >> Hi, >> I'm trying to conditionally add ambitus based on a variable >> definition. I'm >> having trouble figure out how to do it. >> >> \version "2.16.2" >> isAmbitus = #f >> includeAmbitus = #(define-music-function >> (parser location) >> (

Re: Conditional ambitus

Kevin Stolt writes: > Hi, > I'm trying to conditionally add ambitus based on a variable > definition. I'm > having trouble figure out how to do it. > > \version "2.16.2" > isAmbitus = #f > includeAmbitus = #(define-music-function > (parser location) > () > (if isAmbitus > #{ \with { \con

Re: conditional branch within scheme

Dear Jan-Peter, thanks! It was exactly, what I wanted! Am 23. April 2012 20:10 schrieb Jan-Peter Voigt : > Dear Stefan, > > here's a try, that has a parameter dir, which takes a symbol. If the > symbol equals 'above, the Staff is aligned above, else below: > --snip-- > \version "2.14.2" > ossiast

Re: conditional branch within scheme

Dear Stefan, here's a try, that has a parameter dir, which takes a symbol. If the symbol equals 'above, the Staff is aligned above, else below: --snip-- \version "2.14.2" ossiastaff = #(define-music-function (parser location x dir y) ( string? symbol? ly:music? ) (let ((align (if (eq? 'above d

Re: Re: conditional formatting

On Tue 05 Oct 2010, 20:51 Vicente Solsona wrote: > On Mon, 04 Oct 2010 23:11:01 +0200, Marten Visser > wrote: > >Dmytro's suggestion looks more promising, though I haven't been > >able to generate code that does the job so far. When I code Well, i guess that your checks was far to simple for your

Re: Re: conditional formatting

At 20:51 05/10/2010, you wrote: On Mon, 04 Oct 2010 23:11:01 +0200, Marten Visser wrote: Hi Vincente, thanks for the suggestion. However, I do not only want to delete a music expression (which can be tagged), but an entire staff, namely the tabStaff. I wouldn't know how to create code removing

Re: conditional formatting

At 19:03 05/10/2010, you wrote: I can't really use Scheme (other than find and replace), so maybe this doesn't solve what you need, but what about creating separate variables with the staves that you want and simply commenting an appropriate \score ? i.e., \version "2.12.3" piccolo = \relativ

Re: Re: conditional formatting

On Mon, 04 Oct 2010 23:11:01 +0200, Marten Visser wrote: Hi Vincente, thanks for the suggestion. However, I do not only want to delete a music expression (which can be tagged), but an entire staff, namely the tabStaff. I wouldn't know how to create code removing a staff by tagging it. yo

Re: conditional formatting

I can't really use Scheme (other than find and replace), so maybe this doesn't solve what you need, but what about creating separate variables with the staves that you want and simply commenting an appropriate \score ? i.e., \version "2.12.3" piccolo = \relative a' { a c' a e' e c a e } instrum

Re: Re: Re: conditional formatting

At 11:08 05/10/2010, you wrote: On Mon 04 Oct 2010, 23:11 Marten Visser wrote: > Dmytro's suggestion looks more promising, though I haven't been able > to generate code that does the job so far. When I code > > == > \new Devnull > << > \TablatureNotes > >> > ==

Re: Re: conditional formatting

On Mon 04 Oct 2010, 23:11 Marten Visser wrote: > Dmytro's suggestion looks more promising, though I haven't been able > to generate code that does the job so far. When I code > > == > \new Devnull > << > \TablatureNotes > >> > == > > I still get an empty ta

Re: Re: conditional formatting

At 21:22 04/10/2010, you wrote: On Mon, 04 Oct 2010 01:03:30 +0200, Marten Visser wrote: Hello again, Typesetting my masterpiece :D, I ran into the following problem: I have a piece for piccolo and guitar. If I typeset the music for guitar, I'd like to have a tablature staff in addition to the

Re: conditional formatting

On Mon, 04 Oct 2010 01:03:30 +0200, Marten Visser wrote: Hello again, Typesetting my masterpiece :D, I ran into the following problem: I have a piece for piccolo and guitar. If I typeset the music for guitar, I'd like to have a tablature staff in addition to the notes, but If I typset for

Re: conditional formatting

On Mon 04 Oct 2010, 01:03 Marten Visser wrote: > Hello again, Hi! > Typesetting my masterpiece :D, I ran into the following problem: > I have a piece for piccolo and guitar. If I typeset the music for > guitar, I'd like to have a tablature staff in addition to the notes, > but If I typset for picc

Re: Conditional compiles

On Thu, Jun 3, 2010 at 2:16 PM, wrote: > Is there a way to compile different parts of a lilypond source file without > needing to edit source. Yes. You might want to read the manual, and/or search the mailing list archives. Cheers, - Graham ___ lily

Re: Conditional runs

Karl: > I try to do conditional lilypond runs. I can do that by having different > files which includes the common parts, but I'd like to have just one > source file and specify which version to use (in my case, mostly different > page sizes). So I'm trying out the #(if (defined ..)) construct. ..

Re: Conditional runs

Reinhold: > Am Donnerstag, 11. Februar 2010 08:47:42 schrieb Karl Hammar: ... > > 1, what is the rationale for "lilypond -d xx" to be restricted to just > >a certain list of variables? > If the given flag is not an officially supported one, then lilypond will > print > out a warning, but the

Re: Conditional runs

Am Donnerstag, 11. Februar 2010 08:47:42 schrieb Karl Hammar: > > I try to do conditional lilypond runs. I can do that by having different > files which includes the common parts, but I'd like to have just one > source file and specify which version to use (in my case, mostly different > p

Re: Conditional input

hi, On Jan 30, 2009, at 12:27 PM, northofscotland wrote: I would like to able to include some simple statements of the kind "if ... then ... else" in the note entry. What I would like to achieve is to have two options for a note so that if I wanted to change the instrument where the regist

Re: Conditional breaks

If each score is very short, you could try forbidding page breaks within each score: \new Score \with { \override NonMusicalPaperColumn #'page-break-permission = ##f } { etc. May depend on the version you are using. David. --- Original Message --- From: "Mark Austin" <[EMAIL PROTECTED

Re: Conditional footers, dependent on a page mark?

Reinhold Kainhofer kainhofer.com> writes: > > PS2: In case you are interested what all my questions are about lately and > what I really did with all the great answers and your help, I put the first > seven pages of my latest edition on our web server: > http://www.fam.tuwien.ac.at/~reinhold/t

Re: conditional

On Thursday 02 October 2003 07:37 am, Mats Bengtsson wrote: > I don't really understand what you mean, but it seems that you > are making things more complicated than necessary. > > If you want to separate the music input, the titling and the > actual definitions of what should be included in a spe

RE: conditional

yes this reminds me of lilypond book a bit. I could make a make file to include pieces after the lilypond process as well, but I now get the idea. now I have some more pieces to get and I will be able to start. Thanks Aaron On Thu, 2003-10-02 at 14:59, Dick Schoeller wrote: > Aaron, > > What I,

RE: conditional

2, 2003 6:15 AM To: Mats Bengtsson Cc: lilypond Subject: Re: conditional Ok I seeOn Thu, how do i make this conditional, What I am thinking of is creating the files with "conditional text" storing them in a database and issing a command that would have the database or a repository out

Re: conditional

On Thu, 2003-10-02 at 14:37, Mats Bengtsson wrote: > I don't really understand what you mean, but it seems that you > are making things more complicated than necessary. believe me I am trying to simplify things. Three hundred files and multiple outcomes. > > If you want to separate the music input

Re: conditional

I don't really understand what you mean, but it seems that you are making things more complicated than necessary. If you want to separate the music input, the titling and the actual definitions of what should be included in a specific score, you could put the definitions in separate files and use t

Re: conditional

Ok I seeOn Thu, how do i make this conditional, What I am thinking of is creating the files with "conditional text" storing them in a database and issing a command that would have the database or a repository output a book with no header info because the info will be in a latex file for instance. F

Re: conditional

You could easily have different header information in different score blocks, just say \score{ ... \header{ title = "The title for this particular score block" ... } } If you want different annotations within the music, it's easiest to put them in separate definition annotationsVersio

Re: Conditional expressions

Dr A V Le Blanc wrote: ... Well, I have only given simple examples. Suppose I want the midi file to have a different rhythm than the source, for example, as is the case in some music styles. In fact, I think my rptarg = "volta" ... \repeat \rptarg 2 method completely simple. If I

Re: Conditional expressions

[EMAIL PROTECTED] writes: > Is it possible to pass two music expressions to a scheme function > as arguments? > no, but you can use \apply #func { arg1 arg2 } this passes a sequential music with 2 elts to func. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen

Re: Conditional expressions

On Mon, Feb 24, 2003 at 04:52:49PM +0100, Mats Bengtsson wrote: > There are probably simpler methods to achieve what you want to do. > Take a look at the two collections of examples at the web page, > Go to lilypond.org, click on Documentation:Index and then on > "tips-and-tricks" and "Regression T

Re: Conditional expressions

There are probably simpler methods to achieve what you want to do. Take a look at the two collections of examples at the web page, Go to lilypond.org, click on Documentation:Index and then on "tips-and-tricks" and "Regression Tests" respectively. The Regression tests document contains an example on