Re: Apply \editionMod to grace note

Am 31.12.2015 um 00:18 schrieb Kieren MacMillan: > Hi Urs, > >> so: what is the incantation for ly:make-moment to address some point in a >> \partial ? > In my current score, > > \editionMod IStoodTiptoe-score 1 #(ly:make-moment 0/4 -0/4) > > let me address the [single] quarter beat/moment i

Re: Apply \editionMod to grace note

; or inside a chord > @ time T. > > OK, now lunch-time ;-) > > All the best for the new year :-) > Cheers, Jan-Peter > > Am 31. Dezember 2015 02:48:29 MEZ, schrieb Urs Liska : > > > > Am 31.12.2015 um 00:18 schrieb Kieren MacMillan: > > Hi Ur

Fwd: [oll-user] Start using OpenLilyLib

Hi Helge, this is the easiest way to tell you that the openlilylib-user list isn't active anymore. I can't tell anything more now as I'm preparing for vacations. Maybe I'll find some time in the evenings, but I don't know for sure. clip-regions is kind of deprecated, better go to /ly/comptools (

Re: A twelve tone matrix engraver

engrave > 12 rows which are equal in all aspects except the pitches I wanted to > create some function that would create a new staff with some specific > configurations and recursively call itself 12 times. The Scheme > tutorial by Urs Liska > (lilypondblog.org/category/using-lilypon

Re: Strange beaming error

Do you also have subdivideBeams = ##t somewhere? If so please show the result with both 2.19.28 and .35.. And if that's the case you should maybe send me (privately?) the full piece so I could test with several builds before and after several recent changes. Urs Am 7. Januar 2016 01:16:43 MEZ,

Re: Strange beaming error

Am 7. Januar 2016 10:16:29 MEZ, schrieb David Kastrup : >Urs Liska writes: > >> Do you also have subdivideBeams = ##t somewhere? >> If so please show the result with both 2.19.28 and .35.. >> >> And if that's the case you should maybe send me (privately?) the

Re: Strange beaming error

aming in each > hand, so if the output is sensitive to that it's probably a bug... > > Anyway, Urs Liska has a Gist with my current code on this project, and > I gather is going to do a regression test in case there's a recent bug > in Lilypond. I've nearly tracked it dow

Re: Strange beaming error

Hi Chris, OK, I've now compiled your score (thanks for the gist, looks nice BTW) and went through the beaming issues I could see. First of all I must say that the new subdivision logic (introduced in 2.19.35) seems to do what I wanted and is actually an improvement: Compare 01.png to 02.png and 0

Re: Fwd: Concerts in Berlin with LilyPond scores

Am 07.01.2016 um 23:50 schrieb Colin Campbell: > Forwarding to the User group, as it's more appropriate there, and for > wider distribution. All the best for the concerts, Aurélien, and > thanks for letting us know. That's partially true. lilypond-user is the better place to let more people know

Re: Strange beaming error

Am 07.01.2016 um 10:16 schrieb David Kastrup: > Urs Liska writes: > >> Do you also have subdivideBeams = ##t somewhere? >> If so please show the result with both 2.19.28 and .35.. >> >> And if that's the case you should maybe send me (privately?) the full &g

Re: ly:one-line-breaking

Am 9. Januar 2016 19:30:56 MEZ, schrieb Richard Shann : >I was wondering if it would be possible to develop a variant of "all on >one line", namely "all on one page", where the page height would be >automatically adjusted to fit the music, leaving the width as set. I had been thinking about "abu

Beaming over a rest before a subdivision

Hi, there is an issue with rests under beams. The comment in the source code says "Invisible stems should be treated as though they have the same number of beams as their least-beamed neighbour." I think this is intended for cases like \relative c'' { a32 [ a a r a16 a] } (first attachmen

Re: Beaming over a rest before a subdivision

Am 12.01.2016 um 16:37 schrieb Kieren MacMillan: > Hi Urs, > >> I see two approaches to this: >> >> a) have the number of beams correspond to the actual duration of the >> note (third attachment) >> b) have *no* beamlets at all and let the subdivision be calculated as >> usual (fourth attachment)

Re: Beaming over a rest before a subdivision

Am 12.01.2016 um 16:47 schrieb Urs Liska: > Hi Kieren, > > thanks for info and opinion. (I really have to get hold of Gould's book > finally ...). > > If I'd implement that > > \relative c'' { > a32 [ a a r a16 a ] > \set subdivideBeam

Re: Beaming over a rest before a subdivision

Am 12.01.2016 um 17:28 schrieb Mark Knoop: > At 17:15 on 12 Jan 2016, Werner LEMBERG wrote: >>> b) have *no* beamlets at all and let the subdivision be calculated >>>as usual (fourth attachment) >> This is what I prefer. >> > +1. Gould seems to always use stemlets with beamlets when the bea

Re: Beaming over a rest before a subdivision

Am 12.01.2016 um 17:49 schrieb Urs Liska: > > Am 12.01.2016 um 17:28 schrieb Mark Knoop: >> At 17:15 on 12 Jan 2016, Werner LEMBERG wrote: >>>> b) have *no* beamlets at all and let the subdivision be calculated >>>>as usual (fourth attachment) >>

Re: Beaming over a rest before a subdivision

Am 12.01.2016 um 18:11 schrieb Kieren MacMillan: > Hi Urs, > >> I must say I find the attached image (with 1/16 subdivision and rests >> before each division) pretty clear. > “Pretty clear”? Yes. > > Could it be clearer? Definitely. > I can’t tell if, for example, the 64ths should be phrased 3+5

Re: Beaming over a rest before a subdivision

Am 12.01.2016 um 18:16 schrieb Urs Liska: >>> What should the behavior of the *last* one be here? >> > Stemlet, for sure. (IMO) > Unfortunately producing stemlets is a completely different business > which I haven't discovered yet (don't even know where this

Re: Beaming over a rest before a subdivision

Am 12.01.2016 um 19:57 schrieb Kieren MacMillan: > Hi Urs, > >> Ah well, producing stemlets is the responsibility of user input code. > Indeed. =) > I have some syntactic sugar for just such efforts. > >> Find attached a solution *with* stemlets (\override >> Staff.Stem.stemlet-length = 1) > Fr

Re: Beaming over a rest before a subdivision

Am 12.01.2016 um 20:59 schrieb Werner LEMBERG: >> What should the behavior of the *last* one be here? > No beams over the rest. Well, default behaviour is to break the beam at all rests here (see attached). But if the user manually enters the beam enclosing the rest there should be *something*.

Re: Beaming over a rest before a subdivision

Am 13.01.2016 um 10:08 schrieb Mark Knoop: > At 22:57 on 12 Jan 2016, Urs Liska wrote: >> Am 12.01.2016 um 20:59 schrieb Werner LEMBERG: >>>> What should the behavior of the *last* one be here? >>> No beams over the rest. >> Well, default behaviour is to b

Behavior of non-flag side with strictBeatBeaming

Hi all, one more beaming question, given the following input \relative a' { \time 6/8 \set strictBeatBeaming = ##t a8.. a32 a16 a } which of the attached engravings do you prefer, LilyPond's current or the modified? Would it make sense to add a beaming option (e.g. "strictBeatBeamingNonFl

Re: Behavior of non-flag side with strictBeatBeaming

Am 13.01.2016 um 18:09 schrieb Urs Liska: > Hi all, > > one more beaming question, > > given the following input > > \relative a' { > \time 6/8 > \set strictBeatBeaming = ##t > a8.. a32 a16 a > } > > which of the attached engravings do you

Re: Behavior of non-flag side with strictBeatBeaming

Am 13.01.2016 um 18:23 schrieb Urs Liska: > > > Am 13.01.2016 um 18:09 schrieb Urs Liska: >> Hi all, >> >> one more beaming question, >> >> given the following input >> >> \relative a' { >> \time 6/8 >> \set strictBe

Re: Behavior of non-flag side with strictBeatBeaming

Am 13.01.2016 um 20:07 schrieb Pierre Perol-Schneider: > The second is simply the easiest to read. > HTH > Pierre > > 2016-01-13 18:59 GMT+01:00 Kieren MacMillan > mailto:kieren_macmil...@sympatico.ca>>: > > Hi Urs, > > > which of the attached engravings do you prefer, LilyPond's > cu

Re: Behavior of non-flag side with strictBeatBeaming

Am 14.01.2016 um 12:33 schrieb Kieren MacMillan: >> So I suggest the following: >> >• Default behaviour is (as currently): point the extra beam to the side >> > with more stems (i.e. join them) >> >• strictBeatBeaming produces (as currently) the extra stemlet but (new) >> > joins the be

Re: Behavior of non-flag side with strictBeatBeaming

Am 15.01.2016 um 01:19 schrieb Simon Albrecht: > On 15.01.2016 01:09, Urs Liska wrote: >> F) is interesting as it*only* has strictBeatBeaming set. >> There is no subdivision in the middle of the beam (7-8) because >> subdivideBeams is not set. However, the beamlets at

Re: Behavior of non-flag side with strictBeatBeaming

Am 15.01.2016 um 06:52 schrieb Werner LEMBERG: >> I have pulled together a complicated example, which is engraved with >> a number of option combinations. For ease of discussion I have >> numbered the stems. > Thanks. My comments below are of general nature, not specific to > subdivisions. That

Re: Behavior of non-flag side with strictBeatBeaming

Am 15.01.2016 um 08:49 schrieb Urs Liska: >> In solution G), I think that position 2 is really invalid. How can it >> > have a duration of 1/32 and 1/64 at the same time? > That's true. > I'll have to look into that (obviously the stem is also looking to the &g

Re: Behavior of non-flag side with strictBeatBeaming

Am 15.01.2016 um 08:49 schrieb Urs Liska: >> > Actually, I'm missing a solution that looks like F) but has three >> > beams between 2 and 3. > I've been thinking about that too. This would somehow be like a "partial > subdivision" where the beam count

Re: Help with unexpexted double barline trouble and \markup

Am 15.01.2016 um 08:07 schrieb Carl-Henrik Buschmann: > I'm working on a lead sheet but being a novice i'm hitting my head > against the wall at some noob problems. > > Bar 1) > Stemlets. Do it have to be this hard creating them? Is there a way to > make it global? Also, i want the stemlet to r

Re: Help with unexpexted double barline trouble and \markup

Am 15.01.2016 um 15:37 schrieb Kieren MacMillan: >> Bar 1) >> > Stemlets. Do it have to be this hard creating them? Is there a way to make >> > it global? Also, i want the stemlet to reach down towards the rest. How? > This may be related to the issue Urs is working on at the moment. In any >

Beamlets when first/last element of a beam is a rest

Hey all, one more beaming question (I deliberately keep these questions on -user as I think *user* input is important here): When the user has requested manual beaming over rests at the end like c16 [ c c r ] (Hi Carl-Henrik ;-) ) what should the beam do at that moment? If you look at the fi

Re: Help with unexpexted double barline trouble and \markup

Am 15.01.2016 um 17:46 schrieb Simon Albrecht: > On 15.01.2016 16:58, Carl-Henrik Buschmann wrote: >> 1) My experience is that reading rhythms with the stemlets over the >> rests helps alot. It is a tad "modern" but generally approved. Is >> there a way to make it global? > > No problem: just in

Re: Programmatically building music-function names

Am 15.01.2016 um 18:06 schrieb Chris Yate: > Hi, > > I'm trying to typeset a number of short pieces into multiple scores in > one file. I can do this manually, as: > ... > > I've attached a ly file including the code I've pasted here. > > thanks, > > Chris > Hi Chris, I think (if I didn't

Configuring beam count at subdivisions

Hi again, some aspects of the discussion about beaming made me realize again that we shouldn't always/only look for "the" solution but rather provide the choices and set a sensible default. And this is probably true also for the beam count at subdivisions. Earlier (up to ca. 2.19.20) LilyPond alw

Re: Configuring beam count at subdivisions

n, and so I'm inclined to throw it out again (no big deal of course) and only provide the #'base-moment option. While I wouldn't use it personally I can think of scores where the new default beaming (with differing beam numbers on the different positions) might look too inconsistent.

Handling of subdivisions with shortened beams

One more from this round of review ... I had changed the subdivision behaviour (which is already in 2.19.35) for shortened beams. c32 [ c c c c c c] r (i.e. a beam shortened by 1/32) subdivided by 1/8 currently has *two* beams at the subdivision - to indicate that the remaining group is shorter

Re: Handling of subdivisions with shortened beams

ehm, attachment? Am 18.01.2016 um 18:20 schrieb Urs Liska: > One more from this round of review ... > > I had changed the subdivision behaviour (which is already in 2.19.35) > for shortened beams. > > c32 [ c c c c c c] r > > (i.e. a beam shortened by 1/32) subdivided b

Re: Handling of subdivisions with shortened beams

Am 18.01.2016 um 18:24 schrieb Kieren MacMillan: > Hi Urs, > >> c) >> Take a) as the default and provide a context property > This. > > Thanks, > Kieren. > Any suggestions for a better name than \set subdividedBeamCountAddForShortenedBeam = ##t ? __

Re: Configuring beam count at subdivisions

Am 18.01.2016 um 18:28 schrieb Kieren MacMillan: > Hi Urs, > >> deep in my heart I also feel we shouldn't support incorrect notation > Well, okay, then… Let's eliminate the ability to move NoteHead to the wrong > side of Stem, block \rotate from affecting e.g., Rest, etc. etc. ;) > > Just a Dev

Re: Handling of subdivisions with shortened beams

Am 18.01.2016 um 18:37 schrieb Simon Albrecht: > On 18.01.2016 18:27, Urs Liska wrote: >> Am 18.01.2016 um 18:24 schrieb Kieren MacMillan: >>> Hi Urs, >>> >>>> c) >>>> Take a) as the default and provide a context property >>> This. >

platform specific variables

Hi all, I'd be glad if Windows and Mac users could send me the output of the following code: testVariables = #(define-scheme-function ()() (display PLATFORM)(newline) (display DOS)(newline) ; you may comment out the following if you don't want to ; show your working directory (display (

Re: platform specific variables

' > Parsing... > Success: compilation successfully completed > Completed successfully in 0.4". > > > Cheers, > Pierre > > 2016-01-19 9:43 GMT+01:00 Urs Liska <mailto:u...@openlilylib.org>>: > > Hi all, > > I'd be glad if Windows

Re: platform specific variables

Am 19.01.2016 um 09:43 schrieb Urs Liska: > Hi all, > > I'd be glad if Windows and Mac users could send me the output of the > following code: Thanks to all, I have now enough information (and seemingly found a bug ...). Urs

Re: Displaying variables and parameter values

Am 19.01.2016 um 16:20 schrieb David Sumbler: > Is there a way of displaying the current value of particular variables > and parameters during Lilypond compilation? Of course. For example: var = "three" #(display var) #(newline) #(ly:message var) varList = #'(one two three) #(ly:message (for

Re: Setting a directory for .ly documents, when using LaTEX

Am 20.01.2016 um 13:48 schrieb hbezemer: > > > > > > Dear Members, > > I'm using LaTEX to create a chord and scale book and have a lot of .ly > files, which starts to clutter the directory where the main TEXt-file is. > Ehm, what is it you want to include in your book? If it's PDF files they

Re: [OT] Linking to threads in this list Re: Infinite page length

Am 20.01.2016 um 15:04 schrieb Richard Shann: > On Wed, 2016-01-20 at 14:00 +0100, Simon Albrecht wrote: >> On 20.01.2016 12:18, Richard Shann wrote: >>> see the thread: >>> >>> Re: ly:one-page-breaking (was: ly:one-line-breaking) >>> >>> the last email in this thread was yesterday! Is there an e

Beam subdivisions under tuplets

How should beam subdivisions work under tuplets? \version "2.19.35" \relative c'' { \set subdivideBeams = ##t \set baseMoment = #(ly:make-moment 1/16) c32 [ c c c \tuplet 3/2 { c c c c c c c c c c c c ]} } will create beam subdivisions after the first group of four 1/32s and another one

Re: Beam subdivisions under tuplets

__ > > Kieren MacMillan, composer > ‣ website: www.kierenmacmillan.info > ‣ email: i...@kierenmacmillan.info > -- Urs Liska www.openlilylib.org ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Determine the including file

If I have % file a.ly \include "b.ily" % file b.ily \include "c.ily" % file c.ily can I somehow refer to file b.ily from file c.ily? In other words: If b.ily includes c.ily can I know from within c.ily that it was b.ily who included me? I suppose not, but one should never give up without askin

Re: Determine the including file

Am 22.01.2016 um 12:04 schrieb Chris Yate: > On 22 January 2016 at 10:44, Urs Liska <mailto:u...@openlilylib.org>> wrote: > > If I have > > % file a.ly <http://a.ly> > \include "b.ily" > > % file b.ily > \include "c

Re: Algorithm for calculating slur shape

Am 22.01.2016 um 12:24 schrieb Mike Solomon: > None of it is published but all of it is in the C++ source code and is > pretty clear! Maybe it would have been nice to point the OP to http://git.savannah.gnu.org/cgit/lilypond.git/tree/lily There is a bunch of files starting with "slur" in that d

Accessing Grob properties (was: Handling of subdivisions with shortened beams)

Am 18.01.2016 um 20:20 schrieb Urs Liska: > Am 18.01.2016 um 18:37 schrieb Simon Albrecht: >> On 18.01.2016 18:27, Urs Liska wrote: >>> Am 18.01.2016 um 18:24 schrieb Kieren MacMillan: >>>> Hi Urs, >>>> >>>>> c) >>>

Re: Accessing Grob properties

Am 22.01.2016 um 18:49 schrieb David Kastrup: > Urs Liska writes: > >> ... >> I am now trying to implement configuration through >> >> \override Beam.subdivide-details.beam-count = #'metric >> \override Beam.subdivide-details.ignore-shortenin

Re: Accessing Grob properties

Am 22.01.2016 um 20:29 schrieb Urs Liska: > beaming_options_.subdivided_beam_count_ = > (scm_eqv_p (ly_symbol2scm("one"), ly_symbol2scm("one"))) > ? ONE > : (scm_eqv_p (subdiv_beam_count_prop, > ly_symbol2scm("base-mo

Re: Accessing Grob properties

Am 22.01.2016 um 21:54 schrieb David Kastrup: >> However, from there I don't get any further, and it seems I totally >> > don't understand how the Scheme types are matched in C++. >> > Any attempt to compare the content of beam_count_prop with a set of >> > predefined values seems to fail, and ev

Re: Line break in beam including rests

Am 23.01.2016 um 12:09 schrieb Robert Schmaus: > Hi Nils, > > Add > > \override Beam. breakable = ##t > > before the break in the second example. That should do it ... Yes, and just for the record: it's not the rest that's changing the behaviour. Urs > > Best, Robert > > > __ > > The cure

Re: Edition-engraver: Multiple editions in same file

Am 22.01.2016 um 22:00 schrieb Ben Strecker: > I’m working on a project that would have the same melody appearing in > different ranges in the same document. Each range has its own set of > modifications through the edition-engraver, but using \removeEdition anywhere > in the file appears to

Re: Blank bars for scribbling in

Am 24.01.2016 um 10:55 schrieb Richard Shann: > In some contexts people want music interspersed with blank bars to be > filled in later by hand. Spacer rests achieve this, but I can't track > down any straight-forward way of controlling the size of the blank bar. > Anyone any ideas on this? > > R

Re: Font of accidentals changes after line break

Am 24. Januar 2016 22:56:56 MEZ, schrieb Robert Schmaus : >Dear Lilyponders, > >I usually engrave jazz lead sheets using LilyJazz, and I've noticed the > >following odd behaviour: If I tie a note across a manual line break, >and >the note has an accidental, then the LilyJazz font is not applied

Re: Font of accidentals changes after line break

Am 24.01.2016 um 23:01 schrieb Urs Liska: > > Am 24. Januar 2016 22:56:56 MEZ, schrieb Robert Schmaus > : >> Dear Lilyponders, >> >> I usually engrave jazz lead sheets using LilyJazz, and I've noticed the >> >> following odd behaviour: If I tie a not

Re: Font of accidentals changes after line break

LilyLib's Stylesheet library is substantially different as it transparently replaces the font loaded by LilyPond itself. Urs > > >> On 24 Jan 2016, at 23:33, Urs Liska wrote: >> >> >> >>> Am 24.01.2016 um 23:01 schrieb Urs Liska: >>> >>> Am 2

Re: Font of accidentals changes after line break

Am 25. Januar 2016 21:20:38 MEZ, schrieb Robert Schmaus : >Unfortunately, it doesn't work ... LP v2.19.34 exits ungracefully with >an error message "fatal error: cannot find font: `LilyJAZZ-11'" > >Well, the font is there, as the output of >lilypond -dshow-available-fonts x >shows. This shows t

Re: Henle app

Am 25.01.2016 um 23:11 schrieb Boris Lau: > Any idea what they use for engraving? Given the features for changing > staff sizes as well as individual note and fingerings, it's probably > done on-the-fly... I know that for their printed editions they use quite diverse tools: Sibelius, (I think Fi

Re: simplifying chromatic scale notation

Am 26.01.2016 um 00:05 schrieb musicus: > @Simon: I was not aware of Clairnote, but that direction was not my > intention... > > @Kieren: I agree with you regarding reading... > my point is that this notation could help to understand and remember > the structure. > Especially in modern/ contempor

Re: Compiling a file results in message: Exited with return code -1073741819.

Am 26.01.2016 um 01:04 schrieb Joseph N. Srednicki: > > Please see the attached file. > > > > Go to line 253. > > > > The file compiles cleanly up until this point. > > > > However, when I try to add more than one note to the line 253, I > receive the error message: *Exited with return code

Re: simplifying chromatic scale notation

Am 26.01.2016 um 13:57 schrieb Sharon Rosner: >> Of course a good musician needs to focus on every detail, but only the > "bad" ones neglect the bigger >> context. > What like Florence Foster Jenkins-type bigger context? > >> The key is to focus on the "right" thing, which is in many cases NOT e

Re: Henle app

Am 26.01.2016 um 14:11 schrieb Kieren MacMillan: > Hi Andrew (et al.), > >> I would hazard a guess that the sizing is handled by rendering SVG – the >> whole point of which is that is is scalable and resizeable – output from >> whatever engraving program Henle uses. I doubt that the app is doin

Re: simplifying chromatic scale notation

Am 26.01.2016 um 16:58 schrieb Paul Morris: >> On Jan 26, 2016, at 5:35 AM, Chris Yate > > wrote: >> >> BTW, is there a standard term for non-accidental notes? You >> would think it would be “natural notes” but sometimes natural >> notes are also accidenta

Re: Rests in Dynamics context

Am 26.01.2016 um 17:49 schrieb Caio Giovaneti de Barros: > Is there a way to write rests in the Dynamics context? (or something > like it) I don't think so. But you can try using a regular Staff and adjust it by hiding/omitting everything you don't want: \score { \new PianoStaff << \new

Re: Rests in Dynamics context

Am 26.01.2016 um 18:01 schrieb Caio Giovaneti de Barros: > I think that's it. You saved me again, Pierre! Yes, definitely better than my suggestion. And semantically more appropriate. > > On 26-01-2016 14:57, Pierre Perol-Schneider wrote: >> \new PianoStaff << >> \new Staff { s4 e'4 s2 e'4 }

Understanding ly:parser-include-string

Hi, I'm running into an issue with including files using ly:parser-include-string. The underlying task is that I want to conditionally include files, so I have the pseudo-code: #(if (some-condition) (ly:parser-include-string "\\include \"some-file.ily\"")) This works pretty well for single

Re: Understanding ly:parser-include-string

Am 27.01.2016 um 18:22 schrieb David Kastrup: > Urs Liska writes: > >> Hi, >> >> I'm running into an issue with including files using >> ly:parser-include-string. >> >> The underlying task is that I want to conditionally include files, so I >

Fwd: [MEI-L] Registration Open: Music Encoding 2016

Forwarding this and asking for further distribution. >From last year's experience I can say that the Music Encoding Conference is a very fruitful event if one is interested in any of the discussed topics. Anybody within reach of Montréal should consider it. Best Urs Weitergeleitete Nac

Re: Henle app

Am 28.01.2016 um 12:55 schrieb Andrew Bernard: > And, amusingly, I read on the blog from the MD of Henle that one of > the selling points of the Henle Library is that you can download > different fingerings from many different editors for a given piece. > Well, I suppose some teachers and student

RE: lyp - a Package Manager for Lilypond

pond-user@gnu.org Subject: lyp - a Package >Manager for Lilypond >Hello all, > >I'd like to announce lyp - a package manager for Lilypond: > >   https://github.com/noteflakes/lyp ><https://github.com/noteflakes/lyp>  > >I started writing lyp a couple of m

let assoc-set! append to the right

Hi all, assoc-set! either replaces a value in an alist *in-place* or prepends a new pair if the key isn't present in the alist. However, I need a function the *appends* the entry if it is created newly. I came up with swapping the first element to the end if assoc-set! has modified the length of

Re: let assoc-set! append to the right

Am 29.01.2016 um 10:29 schrieb David Kastrup: > Urs Liska writes: > >> Hi all, >> >> assoc-set! either replaces a value in an alist *in-place* or prepends a >> new pair if the key isn't present in the alist. >> However, I need a function the *appends*

Re: lyp - a Package Manager for Lilypond

Git repository" is in practice almost the same thing as "a > public repository on Github," and Github in particular has had some recent > issues with both technical reliability and human governance. They had a > big outage yesterday. It's not good to put all the community

Re: lyp - a Package Manager for Lilypond

pick about. Best Urs -- Urs Liska www.openlilylib.org ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: digital music editions - is Lilypond a suitable tool for it?

Digital music edition is a rather broad field and there exists a very active scholarly community around it. You nay want to have a look at http://music-encoding.org. With regard to SVG rendering there is Verovio, a tool that can provide instant rendering of scores (encoded in XMK) including re

Passing along variable-number arguments

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

Re: Passing along variable-number arguments

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

Re: Four Part Piano Staff

Am 03.02.2016 um 00:17 schrieb Simon Albrecht: > On 03.02.2016 00:09, Mark Stephen Mrotek wrote: >> Thank you for your reply and the suggested code. What you provide >> works well >> with a single staff - as presented in the documentation. When >> inserted into >> a piano staff two additional sta

Re: Very fast typesetting regardless of beauty?

Am 04.02.2016 um 11:20 schrieb Simon Albrecht: > On 04.02.2016 02:51, Isaac Reilly wrote: >> And since it will always be rendering to a single page wide enough to >> hold it all on one line, I'd like to turn off the line break >> calculations. > > At least there are the ly:one-line-breaking and >

Re: Super and sub

Am 6. Februar 2016 22:24:41 MEZ, schrieb John Gourlay : >Joram, > >As you say, LaTeX is for producing beautiful mathematics and LilyPond >is for producing beautiful music. It’s possible that the conventions in >the two different kinds of typography differ in their placement of sub >and superscri

Re: Super and sub

h that exception. Urs > > HTH, Simon > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-user -- Urs Liska www.openlilylib.org ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: beam breaking with tuplets

Hi Andrew, I can't compile your example on the mobile, but you are most certainly experiencing an issue where LilyPond doesn't behave according to its declared intention. (Assuming that with "broken" you mean subdivided). The proper handling of subdivisions under tuplets is on my agenda in rew

Discussing and helping with openlilylib.org relaunch

uot;Home" link to openlilylib.org will be the exception to the self-containedness). So as said I'd be happy about anyone approaching me who - is interested in openLilyLib and - knows - Bootstrap - LESS - the visual part of web design - (Python based) static site builde

Re: [Correction] Is there a bug in the way Lilypond handles SLURS?

Hi Devin, you're welcome, but this is not a bug but a characteristic of LilyPond's syntax. Slurs (and beams) are not use in an "enclosing" way but are written after the note they affect. So the end of a slur is written after the final note. In your first example (the non-functional) the closing s

Re: [Correction] Is there a bug in the way Lilypond handles SLURS?

Am 15.02.2016 um 17:09 schrieb N. Andrew Walsh: > (just saw that Urs replied. Here's hoping I'm not redundant!) > Nope. You delivered the link that I had already copied but forgot to paste ;-) ___ lilypond-user mailing list lilypond-user@gnu.org https

Difficulty to pass a Scheme expression on the command line

When I have a file.ly containing %%% \version "2.19.37" #(use-modules (guile-user)) #(display whatever) %%% and run this with lilypond -e '(define-public whatever 4)' file.ly I get the error /home/uliska/blob/software/lilypond/builds/current/out/share/lilypond/cur

Re: Difficulty to pass a Scheme expression on the command line

Thanks. Somehow this led me on the right track: it didn't work when injected through Frescobaldi's custom compile dialog. I'll have to look into it, but on the command line it works. Best Urs Am 16.02.2016 um 01:56 schrieb Andrew Bernard: > Works fine for me on 2.19.36 on openSUSELeap 42.1 linux.

Re: There is no key signature in the generated Midi file ?

Am 16.02.2016 um 08:43 schrieb Pierre Perol-Schneider: > Hi Esko, > > See: > http://www.lilypond.org/doc/v2.18/Documentation/usage/invoking-midi2ly IIUC Esko *produces* MIDI files with LilyPond, it's not about converting MIDI *to* LilyPond. Urs > > HTH. > > Cheers, > Pierre > > 2016-02-16 7:38

Re: There is no key signature in the generated Midi file ?

Am 16.02.2016 um 17:29 schrieb Phil Holmes: > - Original Message - From: "David Kastrup" > To: "Esko Teerilahti" > Cc: > Sent: Tuesday, February 16, 2016 4:09 PM > Subject: Re: There is no key signature in the generated Midi file ? > > >> Esko Teerilahti writes: >> >>> David Kastrup

Re: There is no key signature in the generated Midi file ?

Am 16. Februar 2016 20:44:30 MEZ, schrieb Esko Teerilahti : >I also made a quick test with Finale Songwriter. >I created a simple woodwind-quintet composition from the template and >exported to midi file. Key signature is in the control track and has >only one value, >eventhough there is e.g. on

Re: Tie chord between staves

Hi John, before you are wondering about the code example you got by Pierre, let me tell you that you have already managed to run into one of the more annoying and embarrassing issues with LilyPond. There actually is no proper support for ties that are not strictly horizontal, which affect staff ch

Re: moving slur attachment points globally

Am 17.02.2016 um 13:32 schrieb David Kastrup: > Kieren MacMillan writes: > >> Hi David, >> >> Thanks for the response. >> >>> it is hard to guess which cases you are trying to cover or not. >> Essentially all of them (this is for a stylesheet, which intends to >> mimic an existing publishing hou

Re: Arbitrary number of arguments in Scheme function?

Am 17.02.2016 um 22:42 schrieb Peter Crighton: > 2016-02-17 14:02 GMT+01:00 David Kastrup : >> That requires a change in the parser. If you put up a respective >> request, I'll take a look whether I can implement it in one of the next >> versions. > How and where do I do that? Write a request t

<    1   2   3   4   5   6   7   8   9   10   >