Re: Rotation.

Am 28.12.2015 um 08:44 schrieb Hwaen Ch'uqi: Greetings All, I see from the NR that there are ways of rotating individual objects or text markups. Is there a way of rotating an entire score? If you embed the score in a markup, this should work out of the box, IIRC. Marc Thank you for any hel

Re: Strings as variable names

Johan Vromans writes: > On Mon, 28 Dec 2015 12:05:22 +1100 > Andrew Bernard wrote: > >> The name of a variable must have alphabetic characters only, no numbers, >> underscores, or dashes. >> >> Most lilypond users would write bellaMelodia, conventionally. In terms of >> readability, it’s cleare

\transpose not work working inside define-music-function

I'm trying to define a music function that transposes a chord and a melody multiple times.  But for some reason, the transposition is done only once.   Here's my attempt:   repeatpattern = #(define-music-function (parser location chord pattern) (ly:music?  ly:music?)   #{   <<   \new ChordName

Re: \transpose not work working inside define-music-function

This was answered yesterday. Please check the list. -- Phil Holmes - Original Message - From: John Smith To: lilypond-user@gnu.org Sent: Saturday, December 26, 2015 11:01 PM Subject: \transpose not work working inside define-music-function I'm trying to define a music f

Re: \transpose not work working inside define-music-function

Wols Lists writes: > On 27/12/15 16:32, J Smith wrote: >> I'm trying to define a music function that transposes a chord and a >> melody multiple times. But for some reason, the transposition is done >> only once. >> >> Here's my attempt: >> >> repeatpattern = >> #(define-music-function (pa

Re: Strings as variable names

Consistency with what actually? And so the NR should in fact therefore be updated? Andrew On 28/12/2015, 20:17, "David Kastrup" wrote: The quote syntax is a bit of an ugliness which was added for sort-of consistency reasons. ___ lilypond-user mail

Re: \transpose not work working inside define-music-function

"Phil Holmes" writes: > This was answered yesterday. Please check the list. > > -- > Phil Holmes > > > - Original Message - > From: John Smith > To: lilypond-user@gnu.org > Sent: Saturday, December 26, 2015 11:01 PM > Subject: \transpose not work working inside define-music-

Draw line across staves

How does one go about drawing an arbitrary line across staves, as per the attached image? Andrew ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Strings as variable names

Andrew Bernard writes: > d...@gnu.org> wrote: >> >> The quote syntax is a bit of an ugliness which was added for sort-of >> consistency reasons. > > Consistency with what actually? After xxx = ... you can refer to \xxx. And "xxx" = ... has always been allowed for arbitrary strings. >

Re: Draw line across staves

Hello Andrew,Someone proposed the attached example for diagonal lines, maybe that can help?JM DiagonalStrokeAcrossBars.ly Description: Binary data Le 28 déc. 2015 à 12:49, Andrew Bernard a écrit :How does one go about drawing an arbitrary line across staves, as per the a

Re: Strings as variable names

On Mon, 28 Dec 2015 12:51:51 +0100 David Kastrup wrote: > "xxx" = ... > > has always been allowed for arbitrary strings. > > > And so the NR should in fact therefore be updated? > > It's not really making stuff more readable. Now if only this would work: \version "2.19.33" bella_melodia_c

Re: adding a markup ("sim.") to the end of a SustainPedalBracket

Hello, all! > the bug is a consequence of issue 2504 > . > To fix it, just change line 89 of your attached file into > (stencil-whiteout new-sim-stil 'outline thickness 1) Ah! Hoisted by my own petard, as they say… (I personally sponsored tha

Re: frame engraver & box repeats: what's the current state-of-the-art?

Hi David, Thanks for the quick help. > The linked code with corrections should give you what you need. This is actually going to work! It’s like Christmas… Oh, wait: it *IS* Christmas! Thanks, Kieren. Kieren MacMillan, composer ‣ website: www.kierenmacmillan.i

Re: Strings as variable names

> > From: David Kastrup > > To: Andrew Bernard > > Cc: lilypond-user@gnu.org > > Subject: Re: Strings as variable names > > Date: Mon, 28 Dec 2015 12:51:51 +0100 > > > > Andrew Bernard writes: > > > > > > > d...@gnu.org> wrote: > > >> > > >> The quote syntax is a bit of an ugliness which was

Re: lilypond-devel on MacPorts

Hi. > On 12/27/15 12:32 PM, "Jacques Menu" wrote: >>MacPorts as I understand it is meant to work on its own. Since it keeps >>records of what has been installed, their dependencies and where they >>have been installed, I don¹t think you can tamper with that easily. Actually ports in MacPorts dec

Re: Strings as variable names

David Sumbler writes: >> > From: David Kastrup >> > To: Andrew Bernard >> > Cc: lilypond-user@gnu.org >> > Subject: Re: Strings as variable names >> > Date: Mon, 28 Dec 2015 12:51:51 +0100 >> > >> > Andrew Bernard writes: >> > >> > > > > > behalf of d...@gnu.org> wrote: >> > >> >> > >> The q

Re: Strings as variable names

Am 28.12.2015 um 18:49 schrieb David Kastrup: >> 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? > Whenever you have variables pointing

Re: Strings as variable names

Am 28.12.2015 um 18:49 schrieb David Kastrup: David Sumbler writes: [...] 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? Well, speaking jus

Re: Strings as variable names

Am 28.12.2015 um 13:29 schrieb Johan Vromans: > On Mon, 28 Dec 2015 12:51:51 +0100 > David Kastrup wrote: > >> "xxx" = ... >> >> has always been allowed for arbitrary strings. >> >>> And so the NR should in fact therefore be updated? >> >> It's not really making stuff more readable. > > Now if

Re: Strings as variable names

Urs Liska writes: > Am 28.12.2015 um 18:49 schrieb David Kastrup: >>> 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? >> > > Whenev

Re: Strings as variable names

Hi David, > What's wrong with violinI ? For one thing, arabic numerals sort more easily than roman numerals. > When would you ever want to do that? Unfortunately, I need to do it all the time: until Lilypond handles multi-instrumentalist parts better than it does (you may recall us discussing

Re: Strings as variable names

2015-12-28 18:49 GMT+01:00 David Kastrup : [...] > > Reading people's ideas about those things make them appear like > something we would be better without. They only lead to confusion. > > -- > David Kastrup I rarely use this possibility, but it's very nice to have numbers, etc in identifiers fo

Re: Strings as variable names

On Mon, 28 Dec 2015 19:01:47 +0100 Urs Liska wrote: > > part = cello > > > > \score { > > \"bella_melodia_\part" > > } > > I think something like this should be achievable using a music function > with two string arguments. Yes, but my suggestion was to have a mechanism for interpolation of

Re: Strings as variable names

On Mon, 28 Dec 2015 17:42:03 + David Sumbler wrote: > > > It's not really making stuff more readable. > > I think it would be useful to have it added to the NR. If it's part of the language syntax, it should be documented. If it's experimental, dangerous, or deprecated, it should be docum

Re: Strings as variable names

Am 28.12.2015 um 19:20 schrieb David Kastrup: > What's wrong with violinI ? lexicographical sorting (of file names) ≠ roman numeral sorting >> flute_phrase01 = >> flute_phrase02 = >> >> or similar. > > When would you ever want to do that? Variations (one score per variation): fluteTheme = … fl

Re: Strings as variable names

Johan Vromans writes: > On Mon, 28 Dec 2015 19:01:47 +0100 > Urs Liska wrote: > >> > part = cello >> > >> > \score { >> > \"bella_melodia_\part" >> > } >> >> I think something like this should be achievable using a music function >> with two string arguments. > > Yes, but my suggestion was t

Re: Strings as variable names

On Mon, 28 Dec 2015 18:49:30 +0100 David Kastrup wrote: > > I have always been frustrated by the fact that I can't (or thought I > > couldn't) use underscores in variable names, > > Well, that is hopefully more or less documented though probably not > everywhere. NR refers to http://www.lilyp

Re: Strings as variable names

Malte Meyn writes: > Am 28.12.2015 um 19:20 schrieb David Kastrup: >> What's wrong with violinI ? > > lexicographical sorting (of file names) ≠ roman numeral sorting File names are not variable names. -- David Kastrup ___ lilypond-user mailing list

Re: Beamed Tremolo + Fermata

Ooooh! I really like this idea as it would solve the horizontally-centered problem, but I just realized that it would inherit the unknown of the fermata's vertical position that escapes collisions with other elements. I don't know if it could still be treated like a Script object (to take care of v

Re: Strings as variable names

On Mon, 28 Dec 2015 20:27:22 +0100 David Kastrup wrote: > The above is mainly confused. Remember that \n in a string stands for > newline. So there's already some kind of processing done. \{varname} would be an alternative. But it is just a suggestion. > But what _programming_ languages allow

Re: Strings as variable names

> Reading people's ideas about those things make them appear like > something we would be better without. They only lead to confusion. +1 Werner ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond

Re: Strings as variable names

On 28.12.2015 20:28, 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 Ugh, that’s bad. Especially since it’s an important feature in interlocking

Re: Strings as variable names

Am 28.12.2015 um 20:30 schrieb David Kastrup: > Malte Meyn writes: > >> Am 28.12.2015 um 19:20 schrieb David Kastrup: >>> What's wrong with violinI ? >> >> lexicographical sorting (of file names) ≠ roman numeral sorting > > File names are not variable names. > That’s true. I just don’t like

Re: Strings as variable names

> Whenever you have variables pointing to indexed parts or to > consecutive snippets you may want to use variables like > > violin1 = > violin2 = > > or > > flute_phrase01 = > flute_phrase02 = > > or similar. This is expressive as LilyPond code per se, and would > be accessible for scripting, e.g

Re: Beamed Tremolo + Fermata

2015-12-28 20:33 GMT+01:00 tisimst : > Ooooh! I really like this idea as it would solve the horizontally-centered > problem, but I just realized that it would inherit the unknown of the > fermata's vertical position that escapes collisions with other elements. I > don't know if it could still be tr

Re: Notation snippets

2015-12-27 23:10 GMT+01:00 Jayaratna : > Thank you so much, Harm. > > Maybe I could/should draw the glyphs for petrucci style flags. They should > not be too much work if I can start from a draft. > > Andy Would be great. Patches are always welcome. I can't help with this, though. I have no clue h

Re: adding a markup ("sim.") to the end of a SustainPedalBracket

2015-12-28 1:25 GMT+01:00 David Kastrup : > Thomas Morley writes: > >> (1) >> stencil-whiteout-box uses define*-public and optional arguments, I >> thought it's broken in guilev2 > > Only in connection with currying. So > > (define*-public ((... > > is (possibly) going to cause trouble while > >

Re: Beamed Tremolo + Fermata

Harm, > How about overriding TupletNumber? #BOOM or #FTW or whatever the kids would say nowadays. =) Nicely done! Although it’s a [tiny] pimple on the ‘Pond that these kind of [incredibly elegant] hacks must be done, it’s a [giant] shiny platinum crown on the ‘Pond that it’s so easy. Best, K

Re: Strings as variable names

On Mon, 28 Dec 2015 21:39:05 +0100 (CET) Werner LEMBERG wrote: > I suggest to use the m4 preprocessor > [https://en.wikipedia.org/wiki/M4_(computer_language)] to convert, Yikes. Speaking of overkill... > say, `violin1' to `violinI'. Add the line > > define(`violin1', `violinI') This will h

Re: Strings as variable names

Simon Albrecht writes: > On 28.12.2015 20:28, 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 > > Ugh, that’s bad. > Especially since it’s

Re: adding a markup ("sim.") to the end of a SustainPedalBracket

Thomas Morley writes: > Though I'm not sure with the following one. May I ask: curried or not? > (define (foo a b) > (let ((x2 (lambda (arg) (* 2 arg > (map x2 (list a b Why would that one be curried? It's completely boring, returns a list, and its internal function x2 is totally

Re: Strings as variable names

Johan Vromans writes: > On Mon, 28 Dec 2015 20:27:22 +0100 > David Kastrup wrote: > >> The above is mainly confused. Remember that \n in a string stands for >> newline. > > So there's already some kind of processing done. \{varname} would be an > alternative. > > But it is just a suggestion. >

Re: Beamed Tremolo + Fermata

2015-12-28 22:41 GMT+01:00 Kieren MacMillan : > Harm, > >> How about overriding TupletNumber? > > #BOOM or #FTW or whatever the kids would say nowadays. =) > Nicely done! > > Although it’s a [tiny] pimple on the ‘Pond that these kind of [incredibly > elegant] hacks must be done, it’s a [giant] sh

Re: Beamed Tremolo + Fermata

Thomas Morley writes: > 2015-12-28 20:33 GMT+01:00 tisimst : >> Ooooh! I really like this idea as it would solve the horizontally-centered >> problem, but I just realized that it would inherit the unknown of the >> fermata's vertical position that escapes collisions with other elements. I >> don'

Re: Strings as variable names

Johan Vromans writes: > On Mon, 28 Dec 2015 21:39:05 +0100 (CET) > Werner LEMBERG wrote: > >> I suggest to use the m4 preprocessor >> [https://en.wikipedia.org/wiki/M4_(computer_language)] to convert, > > Yikes. Speaking of overkill... > >> say, `violin1' to `violinI'. Add the line >> >> def

Re: adding a markup ("sim.") to the end of a SustainPedalBracket

2015-12-28 23:13 GMT+01:00 David Kastrup : > Thomas Morley writes: > >> Though I'm not sure with the following one. May I ask: curried or not? >> (define (foo a b) >> (let ((x2 (lambda (arg) (* 2 arg >> (map x2 (list a b > > Why would that one be curried? It's completely boring, ret

Re: Beamed Tremolo + Fermata

2015-12-28 23:47 GMT+01:00 David Kastrup : >> \once \override TupletNumber.text = >> #(lambda (grob) >> (let ((dir (ly:grob-property grob 'direction))) > ^^ That one calls > Tuplet_bracket::get_default_dir which references a

Ragged right on last 2 bars.

Dear People, Is it possible to apply the ragged-right paper option in such a way that only the last 2 bars will be effected? Thanks in advantage! Example: \version "2.18.2" \paper { indent = 0 ragged-last-bottom = ##t ragged-right = ##t } \score { \relative c' { \repeat unfold 12 {a'4

Re: Ragged right on last 2 bars.

2015-12-29 0:41 GMT+01:00 Peter Terpstra : > Dear People, > Is it possible to apply the ragged-right paper option in such a way that only > the last 2 bars will be effected? > > Thanks in advantage! > > Example: > \version "2.18.2" > \paper { > indent = 0 > ragged-last-bottom = ##t > ragged-

Re: Ragged right on last 2 bars.

At 15:41 28/12/2015 -0800, Peter Terpstra wrote: Is it possible to apply the ragged-right paper option in such a way that only the last 2 bars will be affected? Example: \version "2.18.2" \paper { indent = 0 ragged-last-bottom = ##t ragged-right = ##t } \score { \relative c' { \repea

Re: Ragged right on last 2 bars.

Thomas Morley wrote: > Use > ragged-last = ##t > instead Thank you kindly, so simple :) Peter ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Music running off page, yet passes bar line check

I have the following music : \tempo 4=40 \time 4/4 \clef bass \barNumberCheck #1 b,1\glissando \barNumberCheck #2 \once \hide NoteHead bes4\glissando a2\glissando \once \hide NoteHead a4\glissando \barNumberCheck #3 \once \hide NoteHead a4\glissando b-\markup{"don't articulate b. stop gliss e

Re: Music running off page, yet passes bar line check

At 18:05 28/12/2015 -0800, Ryan Michael wrote: I have the following music : \tempo 4=40 \time 4/4 \clef bass \barNumberCheck #1 b,1\glissando \barNumberCheck #2 \once \hide NoteHead bes4\glissando a2\glissando \once \hide NoteHead a4\glissando \barNumberCheck #3 \once \hide NoteHead a4\glissan

Re: Music running off page, yet passes bar line check

Hi all, > If you drop one of the glissandi Or use \override Glissando.breakable = ##t (For more information, see .) Hope this helps! Kieren. Kieren MacMillan, c

Re: Strings as variable names

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 But does it really matter? The point is, is it something we would want (i.e., is useful)

Re: Strings as variable names

On Mon, 28 Dec 2015 23:52:27 +0100 David Kastrup wrote: > So, no. I stand corrected. It's a very long since ago that I stopped using m4. > It would not be my choice of tool here nevertheless. Preprocessors in general add the disadvantage of having unmaintainable sources (you cannot edit the un