Re: Any ideas what is happening here?

On Nov 3, 2021, at 22:10, Dan Eble wrote: > > Using \tuplet 1/1 instead of \volta 1 causes the same problem. \tuplet: https://gitlab.com/lilypond/lilypond/-/issues/6205 \volta: https://gitlab.com/lilypond/lilypond/-/issues/6207 — Dan

Re: compiling MacOS application in LilyDev

On Sun, Nov 7, 2021, 6:46 PM Kieren MacMillan wrote: > is it possible for me to compile a version of Lilypond that will run > natively on my Mac OS machine? > One starting point: >

Re: Manipulating instrument names and staff group names

Hi Harm, > Start slowly, maybe with a markup-command you would like to have Okay! I’ve got one: I’d like to become an official #'style in TimeSignature. (This hasn’t been done yet, right?) Thanks, Kieren. Kieren MacM

compiling MacOS application in LilyDev

Hi all, Now that I can compile master from source, is it possible for me to compile a version of Lilypond that will run natively on my Mac OS machine? (My development/compilation environment is LilyDev running in VirtualBox.) Thanks, Kieren. Kieren MacMillan, c

Re: Issue difficulty tags (was: Manipulating instrument names and staff group names)

Hi Carl, > As far as I can see, this is desirable, but certainly not low-hanging fruit. As I qualified, that’s from the metric of “motivation” (which was what Jean implied should be the main metric!). > If you could come up with a an algorithm that would allow me to Do The Right > Thing given

Re: Manipulating instrument names and staff group names

Hi Jean, >>> "Defect" is for problems within the "core program", >>> which means either C++ or Scheme. I would argue that those two are not >>> really separable in most cases >> Does that mean for someone like me — with a fighting chance of Scheme-ing, >> but very little chance of ever C++-ing —

Re: Issue difficulty tags

Carl Sorensen writes: > As far as I can see, this is desirable, but certainly not low-hanging > fruit. In fact, I think that defining the Right Thing is an extremely > difficult task, let alone implementing it. > > If you have two voices to combine, there are three possible choices: > Voice 1, V

Re: Manipulating instrument names and staff group names

Am So., 7. Nov. 2021 um 22:30 Uhr schrieb Jean Abou Samra : > > Le 07/11/2021 à 21:59, Kieren MacMillan a écrit : > > Hi Jonas, > > > >> "Defect" is for problems within the "core program", > >> which means either C++ or Scheme. I would argue that those two are not > >> really separable in most case

Re: Issue difficulty tags (was: Manipulating instrument names and staff group names)

On 11/7/21, 12:46 PM, "lilypond-devel on behalf of Kieren MacMillan" wrote: Obvious “low-hanging fruit” [at least from the perspective of motivation]: I want — nay, need! — the part combiner to Do The Right Thing™: effectively unlimited voice inputs, no problem with quotes and lyric

Re: Manipulating instrument names and staff group names

Jean Abou Samra writes: > Le 07/11/2021 à 21:59, Kieren MacMillan a écrit : >> Hi Jonas, >> >>> "Defect" is for problems within the "core program", >>> which means either C++ or Scheme. I would argue that those two are not >>> really separable in most cases >> Does that mean for someone like me —

Re: Manipulating instrument names and staff group names

Le 07/11/2021 à 21:59, Kieren MacMillan a écrit : Hi Jonas, "Defect" is for problems within the "core program", which means either C++ or Scheme. I would argue that those two are not really separable in most cases Does that mean for someone like me — with a fighting chance of Scheme-ing, but

Re: Manipulating instrument names and staff group names

Hi Jonas, > "Defect" is for problems within the "core program", > which means either C++ or Scheme. I would argue that those two are not > really separable in most cases Does that mean for someone like me — with a fighting chance of Scheme-ing, but very little chance of ever C++-ing — there are

Re: Fwd: Manipulating instrument names and staff group names

Am Sonntag, dem 07.11.2021 um 11:07 -0500 schrieb Kieren MacMillan: > > > 2. Is there a tag/label on GitLab which identifies all and only > > > those issues which don’t (or at least shouldn’t likely) require > > > any C++ work? > > > > There isn't. We had Frog in the past (good for beginners, > >

Re: Manipulating instrument names and staff group names

Hi Jean, > On Nov 6, 2021, at 4:20 PM, Jean Abou Samra wrote: > >> #1034 seems safe, there's no actual "programming" involved, as far as I can >> see. > > The NR appendix is autogenerated, so you'd need to add > a new optional keyword argument to define-music-function > like #:category for mar

Re: Issue difficulty tags (was: Manipulating instrument names and staff group names)

Le 07/11/2021 à 20:45, Kieren MacMillan a écrit : Hi Jean, The problem for both of these is that often, investigating what the bug is and how it might be fixed is the main part of the work. So if you have a good idea of what language is required and how hard it is, you're close enough to a fix

Re: Issue difficulty tags (was: Manipulating instrument names and staff group names)

Hi Jean, > The problem for both of these is that often, > investigating what the bug is and how it > might be fixed is the main part of the work. > So if you have a good idea of what language > is required and how hard it is, you're > close enough to a fix that it's worth it > to actually prepare

Issue difficulty tags (was: Manipulating instrument names and staff group names)

Le 07/11/2021 à 17:07, Kieren MacMillan a écrit : Hello developers! Thanks to Lukas and Jean, I’ve got a working LilyDev environment *and* have successfully done the GitLab branch/push/delete/etc. thing. In other words: For the first time in almost 20 years of Pond-ing, I’m ready to actively c

Re: strange bbox of 'flat' glyph

On Sun, Nov 7, 2021 at 10:20 AM Werner LEMBERG wrote: > > > Does anybody know why the top and the bottom of the bounding box of > the 'Flat' glyph, contrary to 'Sharp' and 'Natural', don't coincide > (more or less) with the extrema of the glyph's outline? A small I can't remember any reason. --

PATCHES - Countdown for November 7th

Hello, Here is the current patch countdown list. The next countdown will be on November 9th. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !987 Use Grob_info_t<> to reduce dynamic casting - Dan Eble https

Fwd: Manipulating instrument names and staff group names

Hello developers! Thanks to Lukas and Jean, I’ve got a working LilyDev environment *and* have successfully done the GitLab branch/push/delete/etc. thing. In other words: For the first time in almost 20 years of Pond-ing, I’m ready to actively contribute code directly to the codebase!! So… firs

Re: cross-staff, broken Glissando

Le 07/11/2021 à 14:15, Thomas Morley a écrit : Am So., 7. Nov. 2021 um 14:00 Uhr schrieb Jean Abou Samra : That said,... If I always compensate the right ending-point with (pseudo-code) (ly:grob-relative-coordinate Y) Then the crosses are at those positions Mike's patch promises. Really S

Re: cross-staff, broken Glissando

Am So., 7. Nov. 2021 um 14:00 Uhr schrieb Jean Abou Samra : > >>> That said,... > >>> If I always compensate the right ending-point with (pseudo-code) > >>> (ly:grob-relative-coordinate Y) > >>> Then the crosses are at those positions Mike's patch promises. > >> Really System? Isn't this going t

Re: cross-staff, broken Glissando

Am So., 7. Nov. 2021 um 13:47 Uhr schrieb Aaron Hill : > > On 2021-11-07 4:26 am, Jean Abou Samra wrote: > > (Adding Aaron in CC.) > > Thanks, Jean. I am subscribed to lily-devel, so I did see the thread. > > > >> Alas, because my lack of C++-knowledge, I can't do it myself. > > > > You should lea

Re: cross-staff, broken Glissando

Le 07/11/2021 à 13:47, Thomas Morley a écrit : Am So., 7. Nov. 2021 um 13:26 Uhr schrieb Jean Abou Samra : (Adding Aaron in CC.) Le 07/11/2021 à 12:39, Thomas Morley a écrit : Hi, commit 94860164493ab3a209986b0e3662ff7bd8958cb5 Author: Mike Solomon Date: Mon Mar 28 10:58:29 2011 -0400

Re: cross-staff, broken Glissando

Am So., 7. Nov. 2021 um 13:26 Uhr schrieb Jean Abou Samra : > > (Adding Aaron in CC.) > > Le 07/11/2021 à 12:39, Thomas Morley a écrit : > > Hi, > > > > commit 94860164493ab3a209986b0e3662ff7bd8958cb5 > > Author: Mike Solomon > > Date: Mon Mar 28 10:58:29 2011 -0400 > > > > Assures smooth t

Re: cross-staff, broken Glissando

On 2021-11-07 4:26 am, Jean Abou Samra wrote: (Adding Aaron in CC.) Thanks, Jean. I am subscribed to lily-devel, so I did see the thread. Alas, because my lack of C++-knowledge, I can't do it myself. You should learn C++ someday :-) As my work schedule allows, I would be willing to assi

Re: cross-staff, broken Glissando

(Adding Aaron in CC.) Le 07/11/2021 à 12:39, Thomas Morley a écrit : Hi, commit 94860164493ab3a209986b0e3662ff7bd8958cb5 Author: Mike Solomon Date: Mon Mar 28 10:58:29 2011 -0400 Assures smooth transitions at glissando line breaks. When a glissando breaks over lines, the left poi

cross-staff, broken Glissando

Hi, commit 94860164493ab3a209986b0e3662ff7bd8958cb5 Author: Mike Solomon Date: Mon Mar 28 10:58:29 2011 -0400 Assures smooth transitions at glissando line breaks. When a glissando breaks over lines, the left point of the beginning-of-line glissando picks up on the y-axis where the

strange bbox of 'flat' glyph

Does anybody know why the top and the bottom of the bounding box of the 'Flat' glyph, contrary to 'Sharp' and 'Natural', don't coincide (more or less) with the extrema of the glyph's outline? A small overshoot outside of the box make sense (although Feta doesn't handle this consistently), but the