Re: Centering bass figures on whole notes and longer (issue 325070043 by pkx1...@gmail.com)

dak wrote > I think it quite unusual to have a figure without a note. Quite to the contrary: Both for voice-leading indications (e.g. quick resolution of suspensions) and point d'orgue situations, it's very common to have multiple figures to the same note. For example, see the last two bars of

Re: Terminology of baseMoment, beats, groups

Am 11.11.2017 um 13:25 schrieb Simon Albrecht: > On 11.11.2017 12:30, David Kastrup wrote: > >> I have a hard time seeing a "beat" as something that can have different >> lengths. >> > > Musical notation isn’t well-defined in a mathematical or programming > sense, so there are no such strict

Re: -dcrop not included in 2.20?

> > Not including it would be a pity. I am only one user and of course the > developers know better why or why not they would accept this -dcrop change. > > But from a user’s perspective: this change is the only way (to my > knowledge) to create vector graphics snippets for inclusion in other >

Re: Release schedule for 2.20

Am 09.05.2018 um 17:23 schrieb Phil Holmes: Question: How difficult/costly/... would it be to prepare a "daily build from current master" for download? Very.  We are talking about 6 hours of build time on a pretty solidly powered 8-processor machine.  Actually, we _were_ talking about that

Re: Release schedule for 2.20

But an increasing number of questions asked in forums or on the lists can be answered by “compile current master or wait for 2.21.0”. And a huge number of answers requires at least 2.19.xx but people understandably don’t want to install an “unstable” version. IIUC, the situation used to be:

Re: Extend Whiteout property

Hi Kieren, Well done. Does it also work with other whiteout styles (e.g., outline)? Not yet. Of course, "rounded-box" would be nice to have (and probably not too hard to implement). I expect "outline" would be more involved; tbh, I'm not quite certain what the precise meaning would be for

Re: Non-quadratic form of whiteout

Hi Harm, thanks much for the ideas and pointers to old discussions! So my first suggestion would be to drop the boolean argument for 'whiteout. > Instead let the user decide. Providing a number shouldn't be too hard. > Dropping the boolean was already disussed here: >

Re: Non-quadratic form of whiteout

2018 um 23:52 schrieb Lukas-Fabian Moser: Dear developers, following a feature request on -user I tried my hand at implementing a feature enabling non-quadratic form for box-whiteouts. As I never participated in developing before (and only rarely get down to coding these days), I'm pretty sure

Non-quadratic form of whiteout

\override NoteHead.whiteout = #'(5 . 40)   % Pair of X-thickness and Y-thickness   g'4   r2   \override NoteHead.whiteout = #'(40 . 5)   g'4 } Best Lukas >From c8f83ad9d480bd8c6ba4ed45c8e167ed32bc52b9 Mon Sep 17 00:00:00 2001 From: Lukas-Fabian Moser Date: Thu, 13 Sep 2018 23:41:33 +0200 Subject

Re: Please test gub

Hi, -- 5e44fec38f33997109bc85c099472b2736649fde is the first bad commit commit 5e44fec38f33997109bc85c099472b2736649fde Author: Frederic Gohier Date:   Thu May 10 11:12:44 2018 +0100     Fix

Re: Please test gub

For more than 10 years gub/specs/lilypond.py used /usr/bin/python. That means that during lilypond-test the system's python interpreter is used as the interpreter for the musicxml2ly script, not our own python in target/tools.  At some currently unknown point in time musicxml2ly became

Re: Please test gub

On my system, your description matches: Current Master's musicxml2ly python script runs fine using my local python2 (2.7.15rc1) but has the error using 2.19.82's python2.4 (2.4.5). Given that nobody is really working on musicxml2ly, I strongly suggest that people start testing and using

Re: Please test gub

Hi everybody, For more than 10 years gub/specs/lilypond.py used /usr/bin/python. That means that during lilypond-test the system's python interpreter is used as the interpreter for the musicxml2ly script, not our own python in target/tools.  At some currently unknown point in time

Re: New feature: automatically invert chords or drop/rise chord notes (issue 365840043 by v.villen...@gmail.com)

This statement surprises me. I always thought of 'drop n' (with 'drop 2' being the most common one) as a means to transform closed-harmony _upper_ voices into open harmony _upper_ voices, without changing the bass at all. [...] Much like continued bass, what we’re dealing with here is the

Re: New feature: automatically invert chords or drop/rise chord notes (issue 365840043 by v.villen...@gmail.com)

much like a suspended chord (the whole point of `drop n’ transformations being to change the bass note). This statement surprises me. I always thought of 'drop n' (with 'drop 2' being the most common one) as a means to transform closed-harmony _upper_ voices into open harmony _upper_

Re: New feature: automatically invert chords or drop/rise chord notes (issue 365840043 by v.villen...@gmail.com)

like when using invertChords on a c:11 chord for the fifth inversion. Oh.  Then this becomes a whole other can of worms; what should be the correct inversion of an 11th chord? Should become (as you seem to suggest) or (as the current code produces)? If I understand correctly, the same

Re: Strange space between beam and slur

Hi Andrew, Am 25.06.19 um 10:56 schrieb Andrew Bernard: What is it about 19? Is it some magic borderline number in some unit system in lilypond? Do we know? I'd rather suspect there's some kind of "anthropic principle" at work here: The bugs (at least the one I reported) should probably

Re: Strange space between beam and slur

Hi David, > @gcc experts (hence posting to devel also): Unfortunately, I cannot > > build 2.19.15 on my machine because of errors of the type: > > > > /home/lukas/git/lilypond/lily/include/smobs.tcc:98:25: error: invalid > > conversion from 'int' to 'scm_unused_struct* (*)(SCM, SCM) {aka > >

Strange space between beam and slur

Folks, while engraving a Bach chorale, I stumbled over an overlarge space between a slur and a beam. After a happy hour of trying to boil the problem down to a minimal example, I arrived at: \version "2.19.39" \new Staff <<   {     R1     a''8( b'' b'' a'')   } \\ {     r4   } >> This

Re: Strange space between beam and slur

Hi Carl, thanks for trying this (and forgive me for explicitly CC'ng you as the author of the commit that, on my system, triggered the problem)! On 6/22/19, 3:48 PM, "Lukas-Fabian Moser" wrote: That's about as much as I can contribute, I guess. Does anybody have an

Re: misplaced-note-head bug (issue 5303)

I'm sorry - I didn't realize that this can be done by just adding a file to input/regression. Done now. Lukas >From 36f2d4e768c1a14c668ab5d132099969796cc5fb Mon Sep 17 00:00:00 2001 From: Lukas-Fabian Moser Date: Thu, 4 Jul 2019 16:18:50 +0200 Subject: [PATCH] In loop calculating the attachme

Re: misplaced-note-head bug (issue 5303)

I would think that rounding the int and keeping lastpos as an integer would be less invasive and I would do that. It would be less invasive, the question is what the right thing would be. Anybody have an idea whether non-integer positions can sensibly be employed here for, say, chromatic

Re: misplaced-note-head bug (issue 5303)

bothering you again with this! Lukas >From 0cfeca9c71bde48e2cc969b0075d1cebf801b600 Mon Sep 17 00:00:00 2001 From: Lukas-Fabian Moser Date: Fri, 5 Jul 2019 16:45:31 +0200 Subject: [PATCH 2/2] Maintain float precision during calculation of attachment of noteheads to chord (thus completing

Re: stem.cc - issue 5303 - misplaced notehead (issue 570830043 by pkxgnugi...@runbox.com)

Hi Carl, Perhaps this patch should also revert 87eb2f9fe1be3a532675fe4b7322bbba5a60ba5c since that patch was a workaround, rather than a real fix, as demonstrated during this troubleshooting thread. Carl https://codereview.appspot.com/570830043/ I'm afraid I do not understand the

Re: misplaced-note-head bug (issue 5303)

Folks, only now was I able to do regression tests regarding my proposed fix(es) of the misplaced-note-head-bug (issue 5303): The bug is caused by the integer-cast lastpos = int (p); in lily/stem.cc:629. Replacing it by either i) lastpos = p; // use float value or ii) lastpos = int (round

Re: misplaced-note-head bug (issue 5303)

Hi David, Aah, I'm sorry - I was not aware that casting to int works by /truncating/. Then it's quite obvious what's happening here. Which code do you think has a problem related to your example? Compile \version "2.19" \score {   {     4 \clef bass   }   \layout {    

misplaced-note-head bug (issue 5303)

Folks, I think I isolated the rounding (?) issue leading to the misplaced note head in https://sourceforge.net/p/testlilyissues/issues/5303/ Please forgive the horrible C/C++ jumble - it's been quite long since I did this kind of stuff and usually only ever wrote vanilla C: #include

Re: misplaced-note-head bug (issue 5303)

Folks, I think I isolated the rounding (?) issue leading to the misplaced note head in https://sourceforge.net/p/testlilyissues/issues/5303/ Please forgive the horrible C/C++ jumble - it's been quite long since I did this kind of stuff and usually only ever wrote vanilla C: #include

German translation

Folks, [tl;dr: Whom should I contact for improvement suggestions for the German PO file?] The German PO file contains some translations that seem to suffer from the "false friend"-syndrome, for instance #: convertrules.py:549 msgid "point-and-click argument changed to procedure." msgstr

Re: Staging broken.

The build log talks about autogen.sh --noconfigure can you confirm that with " ./autogen.sh && make -j4" it also fails? Fwiw, I had the same compile error as David yesterday. (It had been quite a while since I last pulled & compiled, so I was not very much surprised when make didn't

Re: Staging broken.

Le mer. 19 févr. 2020 à 09:08, David Kastrup a écrit : Color me curious: why would you try building staging? The whole point > of the staging system was to avoid breakage for developers. Only patchy > processes are supposed to care about staging. > Master didn't compile, and I tried staging

Re: can a Scheme engraver "solve" Issue #34 (grace note bug)? [cross-posted]

Am 08.02.20 um 21:44 schrieb Han-Wen Nienhuys: I think the right solution would be to kill grace timing altogether, and initiate some sort special "embedded" engraving pass that creates the Grace grobs all at once. That would have another downside: if we construct the grace note grobs in a

2.21.7: dead download links

Folks, I'm sorry if this is already being discussed and I just missed it: Right now, http://lilypond.org/development.html lists 2.21.7 as the current version, but the download links are dead (e.g. https://lilypond.org/download/binaries/linux-64/lilypond-2.21.7-1.linux-64.sh). Lukas

Re: 2.21.7: dead download links

Folks, I'm sorry if this is already being discussed and I just missed it: Right now, http://lilypond.org/development.html lists 2.21.7 as the current version, but the download links are dead (e.g. https://lilypond.org/download/binaries/linux-64/lilypond-2.21.7-1.linux-64.sh). Yes, there was

Re: tie over clef change

However, this gets *never* notated as such. I gave the example of augment sixth chords, that seem to never be notated as diminished sevenths. https://en.wikipedia.org/wiki/Augmented_sixth_chord I assume you meant "dominant sevenths"? (Augmented sixth chords, at least "Italian" and

Re: tie over clef change

I seem to remember that even in Bach's B minor mass (where E12 was not yet a thing) there is an enharmonic tie (or at least tonal repetition?) in the transition from "Confiteor" to "Et expecto". I mean, that transition is a tonal center nightmare anyway. In bar 138: Basically that is an

Re: tie over clef change

The tonal center collapse is done purely vocally in an a cappella passage and when the instruments come back in, it's in a resurrection key and instrument groups (like brass) that are typical for it. [...] Here is a link to a Herreweghe version.

Re: Accidentals' font

Hi Han-Wen, 6) Look at the glyph of forcing: it forms a single word, and not the union of three different characters (which is very distracting, in my opinion) what is 'forcing' ? I assumed it meant sfz, coming from an Italian native speaker - Paolo, please correct me if I'm wrong. 7) Look

Re: GSoC 2020 update, July 18

Hi Pál, in ancient (ars subtilior) notation there actually are noteheads with two stems (which may also be flagged differently), called "dragma". a picture search for "dragma ars subtilior" returned poor images; one not entirely useless is

Re: incomplete tuplets in non-standard time signatures

Hi Michael, I just filed a bug report http://lilypond.1069038.n5.nabble.com/Wrongly-read-property-with-MetronomeMark-td237659.html 2c2908c905ba822ef656b06b1cc4f0ca33960c9c is the first bad commit commit 2c2908c905ba822ef656b06b1cc4f0ca33960c9c Author: Malte Meyn Date:   Sun Sep 29

Re: How to shift trill to below phrasing slur?

Hi Harm, avoid-slur is the correct method: %#(ly:set-option 'debug-skylines #t) \score { { \time 12/8 \relative c' { a8 b\( c a b c d e f d e f g a b g a b c2. \once \override Script.avoid-slur = #'inside d2.\trill \grace { c16 d } e2.\) }

Re: incomplete tuplets in non-standard time signatures

Hi Harm, I just filed a bug report http://lilypond.1069038.n5.nabble.com/Wrongly-read-property-with-MetronomeMark-td237659.html 2c2908c905ba822ef656b06b1cc4f0ca33960c9c is the first bad commit commit 2c2908c905ba822ef656b06b1cc4f0ca33960c9c Author: Malte Meyn Date:   Sun Sep 29 10:10:35 2019

Re: Cairo

Hi Knut, Am 25.06.21 um 01:35 schrieb Knut Petersen: For those who are interested: here is an updated version of my cairo patch. This time around, I could get it to compile. :-) After testing it against a bunch of my recent everyday LilyPond documents: For most of the files, it seems to

Re: [PoC] EXPERIMENTAL binaries of LilyPond 2.22.1

Hi Jonas, Am 13.05.21 um 22:46 schrieb Jonas Hahnfeld via Discussions on LilyPond development: Before starting: These builds are not official, highly experimental, and not meant for "production" installations. They use Guile 2.2 and are slower, might not compile all scores or break some

Re: [PoC] EXPERIMENTAL binaries of LilyPond 2.22.1

Hi Jonas, Am 14.05.21 um 21:59 schrieb Jonas Hahnfeld: Am Freitag, dem 14.05.2021 um 20:35 +0200 schrieb Lukas-Fabian Moser: I just remembered that I have another encoding problem with LilyPond, namely special characters in \bootOutputSuffix lead to replacement characters __ in the name

Re: [PoC] EXPERIMENTAL binaries of LilyPond 2.22.1

Hi Jonas, Obviously some encoding/unicode problem, but I'm not sure if the culprit is LilyPond or Frescobaldi? Umm, so if it works from the command line but not from Frescobaldi, it could be that the invocation from there doesn't pass the filename as UTF-8 and Guile 1.8 works by chance due to

Re: [PoC] EXPERIMENTAL binaries of LilyPond 2.22.1

but frankly I'm surprised that plain gcc's char type and printf seem to be able to deal with multi-byte characters. But this probably has to do with the fact that this was my first #include "stdio.h" since (I think) 1998, and the world has moved on... I don't think "char *" and printf care, they

Re: [PoC] EXPERIMENTAL binaries of LilyPond 2.22.1

Hi Jonas, Do you have any suggestion which route I could try to find out? Not really, other than maybe writing a small C program that dumps the arguments as binary in hex code? I did: #include "stdio.h" void dump_char(char c) { printf("%02hhX(%c)", c, c); } void dump_string(char *c) {

\numericTimeSignature works on Staff level?

Hi, \numericTimeSignature works on Staff level - it has been this way since its first introduction by Graham Percival in 2008 (929abcd11cf5305b0929e5ca75b12ffee9f57785). As a consequence, \version "2.22.1" <<   \new Staff {     \numericTimeSignature     \time 2/2     s1   }   \new Staff {   

Re: Cairo based backend

Hi Knut, Am 05.07.21 um 00:10 schrieb Knut Petersen: The attached patch implements a new backend based on Cairo. To test select the desired output formats by any combination of the '--pdf', '--ps' and '--svg' command line options and  add '-dbackend=cairo'. The '--svg' option must precede the

Re: Cairo based backend

How hard would it be to also add support for -dpreview and -dcrop in the Cairo backend? ... and same question for output-attributes as demonstrated in input/regression/output-attributes.ly ? Lukas

Re: Proposal: Automatically adjusting indents for instrument names

Hi Johannes, I 'd like to propose the enhancement below to LilyPond. It will increase the indent and short-indent of a score to fit all of its instrument names and instrument short names. This is a great idea (and a feature I've been missing for quite some time). In the current version,

Re: Reading files as byte array

Would it be considered okay if we included a scheme function to read a binary file to a byte array? GUILE already supports this out of the box. Have you seen https://www.gnu.org/software/guile/manual/html_node/Binary-I_002fO.html ? Yes, of course GUILE supports this. But the problem is

Re: Reading files as byte array

Just from comparing those statements: Would it be reasonable (and maybe generally useful) to make global_path.find (used in gulp_file_to_string, lily-guile.cc) available at scheme level? see ly:find-file. Aah, thanks much (sorry I didn't see it). So then, Valentin, want you asked for seems

Re: Re-building Appendix A of notation.pdf

but the kerning of "Av" in doesn't seem right to me. Is that as it should be? (The image is from the pdf in the official 2.22/2.23 build.) ... no image... Sorry, shouldn't use inline images. See attached. Lukas

Re: Re-building Appendix A of notation.pdf

Hi James, See: https://lilypond.org/doc/v2.21/Documentation/contributor-big-page.html#building-a-single-document Did you do the 'touch' command? Now I did :-) (thanks!), but touch'ing notation.tely doesn't do the trick. If I'm not wrong, my question is how to force a re-build of

Re: Re-building Appendix A of notation.pdf

Hi Jonas, If I'm not wrong, my question is how to force a re-build of out-www/en/identifiers.tely. I think you need to delete out{,-www}/en/internals.texi. This will retrigger the rule to dump the internal documentation, which is partly included into the Notation Reference. That did it.

Re-building Appendix A of notation.pdf

Hi, I'm probably missing something very obvious: After changing a docstring in ly/music-functions-init.ly, what steps are necessary to re-build notation.pdf in order to check the result in "A.19 Available music functions"? If I only delete notation.pdf and re-build it using make -C

Re: Shortcut for \repeat unfold

Just as a counter-point, while I'm a light user / copyist, I don't think I've EVER used repeat unfold, while repeat percent happens a lot. I actually quite like the "\x16 d8" idea as a shortcut, but what I'm saying is don't think it's a good idea, just because YOU do it a lot. Other people

Re: Shortcut for \repeat unfold

IS unfold the best candidate? Just because the OP makes extensive use of it, doesn't mean everyone else does. I'd rather it was percent, but I suspect I genuinely am a minority. One of the reasons I argue against making \repeat $n \music equivalent to some \repeat X $n \music. An

Re: Shortcut for \repeat unfold

But your special-character argument made me think: Maybe it would be possible to get rid of the * sign? Maybe I'm missing something, but isn't \{unsigned int} still "available" so one could do \16 d8 instead of \*16 d8 ? Of course, probably only David K. can say for sure what implications that

Re: Shortcut for \repeat unfold

Hi, In short, I propose to make the first argument to \repeat optional, making \repeat n music equivalent to \repeat unfold n music. Thanks for working on that! The issue I have with your idea is that to me, \repeat unfold and \repeta volta/tremolo have slightly different semantics:

Re: Shortcut for \repeat unfold

"\*" = #(define-music-function (n mus) (index? ly:music?) #{ \repeat $repeat-shorthand $n { #mus } #}) Instead of debating a default repeat type and function, why not provide access to repetition as a music function with a clear name like \repeatFunction type n music And let the

Re: Shortcut for \repeat unfold

Hi Jean, I think it's a trap to see \repeat unfold as syntactic sugar for repeating a sequence of characters n times in the input. For instance, \relative { \repeat unfold 4 c'1 } is not the same as \relative { c'1 c'1 c'1 c'1 } Yes, of course. But I'd be very surprised if a large

Re: Proposing commit access for Lukas-Fabian Moser

Don't worry about breaking something! In almost all cases this gets caught by the CI infrastructure. I think we all agree that it would be very beneficial if you have commit rights. Thanks! So I clicked the "Request access" button yesterday. Should I do anything else? Lukas

Re: Proposing commit access for Lukas-Fabian Moser

No, that was the only required step after writing to the mailing list (as documented in the CG), afterwards somebody with Owner permissions (currently Han-Wen and me) have to press the button to accept, which I just did. The complication here is that GitLab doesn't send email notifications

Re: markup-command rounded-box is broken

So in my impression, rounded-box-stencil might deserve a refactoring anyway? I would propose: lukas@Aquarium:~/git/lilypond/scm(dev/lfm/rounded-box)$ git diff master diff --git a/scm/define-markup-commands.scm b/scm/define-markup-commands.scm index cb99a960fe..8b54fd048a 100644 ---

Re: markup-command rounded-box is broken

Hi Harm, I noticed a bug with recent master: \markup \rounded-box "foo" prints completely black. First bad commit is: commit 0772e38398972d6c2b4ba9e6f42e7725d973e08b Author: Han-Wen Nienhuys Date: Sun Aug 1 11:15:02 2021 +0200 Stop passing color names to output backends Well,

Re: markup-command rounded-box is broken

this would have the advantage to be inline with the doc-string and solve the issue at hand. Should I prepare a MR? Though, speaking of refactoring rounded-box-stencil. It always bugs me to see some stencil overlaying to get a simple line. Yes, that's an obvious and unpleasant limitation:

Re: Shortcut for \repeat unfold

I answer somewhat orthogonally to your question: I think that for many people it's a lot easier to digest the information "\* creates unfolded repeats; this behaviour may be changed using \defaultRepeatType percent" That is one step forward, one step back: one advantage of a fixed shorthand

Re: Shortcut for \repeat unfold

Maybe it helps to give some context: The discussion started with the problem of skipping notes in lyrics (using \addlyrics {} / \lyricsto {}) in the documentation. In order to skip multiple notes, the documentation currently suggests ugly things like \repeat unfold 2 { \skip 1 } that a)

Re: Shortcut for \repeat unfold

28x { d a b fs | g d g a } https://gitlab.com/lilypond/lilypond/-/merge_requests/937 That is a clever proposal. I am already fond of it. Thank you. This looks so "natural" (in the non-computer science-way of the meaning) one is surprised it works. :-) What this means is that if you

Re: Proposing commit access for Lukas-Fabian Moser

Am 06.10.21 um 21:21 schrieb Jean Abou Samra: Hi all, Rebasing and merging Lukas' \after patch this morning, I had a wonder moment — wait, he still doesn't have commit access? Seeing his recent patches, which all required substantial discussion and refinement as well as documentation and

Lyric extenders in/out of alternatives

Folks, in my quest to maybe get rid of the recommendations of "\skip 1" for lyrics in the NR I stumbled upon the following example in http://lilypond.org/doc/v2.23/Documentation/notation/techniques-specific-to-lyrics.html: % If you wish to show extenders and hyphens into and out % of

Re: Lyric extenders in/out of alternatives

Does anybody see a better solution that might be good enough for the NR? Well-invented. I don't see anything better. Thanks (also for looking at this in the first place). My feeling is that this should replace the "_something" example in the NR, but because of its complexity, it should

Re: Lyric extenders in/out of alternatives

Am 05.10.21 um 01:41 schrieb Dan Eble: I'd basically be interested in trying to understand the mechanics involved, but seeing as term started today at our university, I'm sceptical I can spend serious time on this before Christmas break. (And there's a fair chance it would be above my head

Re: Lilypond is now on Homebrew for macOS Mojave or higher (Intel or M1)

Folks, Am 05.10.21 um 14:39 schrieb Jefferson Felix: No problem, I was just pointing out the reasons why Guile 1.8.8 was not approved by the homebrew core. I even believe this will help advance Guile 2 compatibility, and certainly the Lilypond development community will pick up on any bugs.

Re: Lilypond is now on Homebrew for macOS Mojave or higher (Intel or M1)

[Jean] What kind of next version, next minor of current stable, i.e. 2.22.2, or next stable release, 2.24? Which leads me to ask: @Jefferson: Would it be conceivable to do Homebrew builds also for (odd-numbered) development versions of LilyPond? LilyPond tends to have a conservative policy

Re: Updating alists (was: Tenuto marking too close to note)

Hi Jean, Both of these cases seem to work the same as in current versions if I do [...]  SCM  assq_tail (SCM key, SCM alist, SCM based_on = SCM_EOL)  { -  for (SCM p = alist; !scm_is_eq (p, based_on); p = scm_cdr (p)) +  for (SCM p = alist; scm_is_pair (p) && scm_is_pair (scm_car (p)) &&

Re: point-and-click default

Hi David, I've been using Lilypond for a few years, and only yesterday learned about the point-and-click feature in pdf output. In particular, I had no idea that by default Lilypond includes absolute pathnames to local source files on my system as metadata in the pdf output files. So when I

Re: balloonText and DoublePercentEngraver

Hi Werner, Am 21.12.21 um 23:07 schrieb Werner LEMBERG: Please have a look at the following example. ``` \new Score \with { \consists "Balloon_engraver" } \new Staff { \repeat "percent" 2 { e'4 e' e' e' | \balloonGrobText #'PercentRepeat #'(0 . 1) \markup "Repeat" }

Re: balloonText and DoublePercentEngraver

\new Score \with {   \consists "Balloon_engraver" } Ah, sorry, I forgot one: \new Score \with {   \consists Balloon_engraver } Lukas

Re: balloonText and DoublePercentEngraver

Hi Dan & Werner, Am 22.12.21 um 15:41 schrieb Dan Eble: ``` { \override DoublePercentRepeat.slope = #.3 \repeat percent 2 { e'2 e' e' e' } \revert DoublePercentRepeat.slope } ``` I'd recommend using \temporary\override in to mimic \once behaviour more closely: \version "2.23.5"

Re: CodaMark and friends not included in skyline

Yes. This overrides the default after-line-breaking callback, which causes trouble if that callback was supposed to do something important. Harm's code was written at a time where the grob-transformer was not available. It's now possible to write this code in a way that works for grobs with an

Updating alists (was: Tenuto marking too close to note)

Hi Jean, (CCing devel because of the stuff below the asterisks) Although this approach manipulates internal data structures of LilyPond, it has the advantage of dealing with your issue at the root and not causing side effects for other scripts. Unfortunately, this approach does not work

Re: Updating alists

\version "2.23.6" myScripts = \default-script-alist myScripts.tenuto.padding = 5 \layout {   \context {     \Score     scriptDefinitions = #myScripts   } } {   a-- } (One might also skip defining a new variable and instead change default-script-alist directly, but it has to be re-read

Re: RFC: Adding syntax highlighting to the official documentation

Hi Jean, Feedback is appreciated. For what it's worth: I like that design (only having looked at the style-test.zip file) a lot. It's unobtrusive, yet makes it easier to parse the structure of a code sample at first glance. Of course, that doesn't help at all with the issues raised by

Re: TimeSignature with note in denominator

Hi Elaine, The first is, how is the usage of \time different in lyrics than anywhere else? Frankly, I was not aware that using \time inside lyrics was a thing. What is the reason to use \time inside lyrics? It is a suggested practice, is it the only way of doing certain things? I'm not

Re: TimeSignature with note in denominator

Hi Kieren, Am 13.11.21 um 16:19 schrieb Kieren MacMillan: 1. Is there any objection to me adding a TimeSignature style which would immediately apply to all already-accepted time signatures? 2. If not, does anyone have opinions on what that style name should be? (Ones that seem like obvious

Re: TimeSignature with note in denominator

Hi Kieren, See my “stylesheet” comment earlier in the thread: in a perfect world, a user should be able to take any existing score and simply add \override Score.TimeSignature.style = #'note-denom and the output would be “as expected” — with a new function, a search-and-replace (with

Re: TimeSignature with note in denominator

Wouldn't it be easier to define an independent \kierenTime function that expects an integer (index?) numerator and a music (ly:music?) denominator? Then we could just write \version "2.22" kierenTime = #(define-void-function (num den) (index? ly:music?)    (format #t "~a\n" num)   

Re: TimeSignature with note in denominator

Hi Kieren, You’re not extrapolating the concept, as I have been asking people to, so I’ll once again make it more explicit for you: I want the user to be able to say \tweak style #'note-denom \time 3/4. or \tweak style #'note-denom \time #'(3 . "4.") or \tweak style

Re: TimeSignature with note in denominator

Hi Carl, Although the time signature looks like a fraction, it is not. A fraction has numbers in the denominator and the numerator (and strictly speaking, a fraction properly has integers in the numerator and denominator -- if they are not integers, it's a quotient, not a fraction, IIUC).

Re: TimeSignature with note in denominator

Yes. The numerical representation of traditional time signatures is a pair of integers. But the "numerator" can be any integer. While the "denominator" can also be any integer, it doesn't really represent an integer. It represents a duration; a fraction of a whole note. To make

Re: TimeSignature with note in denominator

Hi Kieren, Am 14.11.21 um 15:00 schrieb Kieren MacMillan: There just is no uniquely identified print form using a note in the denominator for that time signature representation. As I’ve explained several times, there is. I don't think you're right. It's well possible that I'm missing the

Re: TimeSignature with note in denominator

When Thomas Adès switches from 4/4 to 4/5, there is no way of knowing which "graphical" note length (combination of notehead style and flag count) is supposed to be used for the basic unit (of which 4 make up a bar, and of which five equal the duration of a semibreve). Example: \version

Re: TimeSignature with note in denominator

It's great that you show so much patience with rank beginners in LilyPond. Gentlemen, please. It's obvious and well-known that few people know LilyPond's design and inner workings as well as David, so if he raises concerns about a design question, it's a pretty safe bet that there's a

Re: TimeSignature with note in denominator

So can we please try to avoid sarcasm and try to assume best intent on the respective other's side? Having met both of you, I am sure this assumption is actually quite reasonable. Sorry for hitting the limits of my English language skills: I wanted to say that I'm sure that the assumption of

Engraver_group with parent context type?

Folks, while trying to tidy up ly/engraver-init.ly a bit (which seems to have experienced some rank growth over the years) I stumbled upon: \context {   \Staff   \type "Engraver_group"   \name "DrumStaff"   \alias "Staff"   % (etc.) } That's the only instance of a context definition that

Re: Engraver_group with parent context type?

Am 01.11.21 um 21:40 schrieb Jean Abou Samra: In short: useless but not problematic. Am 01.11.21 um 21:08 schrieb David Kastrup: It's redundant. Not incorrect, at worst slightly inconsistent/ugly. Thanks much to both of you (and also for the very enlightening code snippets that make the

  1   2   >