LilyPond 2.25.23

We are happy to announce the release of LilyPond 2.25.23. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.4, the current stable release. Please refer to the

Re: Urs Liska

On Sat, 2025-01-04 at 12:44 +0100, Lukas-Fabian Moser wrote: > git --shortlog --author=Urs shows 70 commits to LilyPond and literally > hundreds of substantial commits to Frescobaldi. I'd propose that there > should be a commemorative release of at least one of the projects. Giv

Re: Urs Liska

serious illness. I wish his family consolation and help in this dark and difficult time. I met Urs on several occasions and always benefited from his commitment. Above all, however, I am very sad that this kind man had to go. The gap he leaves behind in the Lilypond developer community already opened

Re: Urs Liska

I second this. Michael Am 4. Januar 2025 23:31:44 MEZ schrieb "Janek Warchoł" : >sob., 4 sty 2025 o 12:44 Lukas-Fabian Moser via Discussions on LilyPond >development napisał(a): > >> git --shortlog --author=Urs shows 70 commits to LilyPond and literally >> hun

Re: Urs Liska

difficult time. I met Urs on several occasions and always benefited from his commitment. Above all, however, I am very sad that this kind man had to go. The gap he leaves behind in the Lilypond developer community already opened up when he had to retire due to his health. But now it is certain that

Re: Compiling on MacOS

; been added with GNU make 4.0. Contributor docs currently list GNU make 3.78 > > as the minimum. > > Yes, LilyPond requires at least GNU make 4.2. This is also checked by > configure, but not enforced when actually typing [g]make. I have a > patch series from last July work

Re: Compiling on MacOS

3.78 > as the minimum. Yes, LilyPond requires at least GNU make 4.2. This is also checked by configure, but not enforced when actually typing [g]make. I have a patch series from last July working on configure.ac and also fixing up the documentation, but never found the time to clean it up properly...

LilyPond 2.24 in Debian 13 (was: Thoughts on next stable release(s))

Hi all, On Sun, 2024-06-16 at 22:24 +0200, Jonas Hahnfeld wrote: > Looking at the bigger picture, we released LilyPond 2.22.0 in early > 2021 (it slipped from late 2020) and version 2.24.0 in late 2022. That > said, I'm not sure there is already "enough" to plan for 2.26

LilyPond 2.25.22

We are happy to announce the release of LilyPond 2.25.22. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.4, the current stable release. Please refer to the

LilyPond 2.25.21

We are happy to announce the release of LilyPond 2.25.21. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.4, the current stable release. Please refer to the

LilyPond 2.25.20

We are happy to announce the release of LilyPond 2.25.20. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.4, the current stable release. Please refer to the

LilyPond 2.25.19

We are happy to announce the release of LilyPond 2.25.19. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.4, the current stable release. Please refer to the

Re: Lilypond dependencies

22.04 I tried build-dep lilypond but I get a fairly vague reply from it $ sudo apt-get build-dep lilypond Reading package lists... Done E: You must put some 'deb-src' URIs in your sources.list Does anyone have a quick breadcrumb or two to share with me about how to resolve this please?

Re: Joining the development team

hes to https://gitlab.com/lilypond/lilypond/ is not strictly necessary, you can just push branches to your fork and open merge requests from there. (In fact, that's how I work all the time because I find it "cleaner".) > I have ready a fix for issue #6202 including a regtest. And I plan

Re: search for better regtest comparison algorithm

normalization. In other scenarios, you may also want to normalize brightness / color / white balanve and other stuff, but I think this does not apply well for lilypond scores... Best wishes, Jürgen (being curious if my email this time makes it through the devel list, after it

LilyPond 2.24.4 released!

We are proud to announce the release of GNU LilyPond 2.24.4. LilyPond is a music engraving program devoted to producing the highest-quality sheet music possible. It brings the aesthetics of traditionally engraved music to computer printouts. This version contains a number of fixes since the

Re: Thoughts on next stable release(s)

On Mon, 2024-07-08 at 22:30 +0200, Jonas Hahnfeld wrote: > On Sun, 2024-06-16 at 22:24 +0200, Jonas Hahnfeld wrote: > > Hi all, > > > > it's been 7 months since the last stable (bugfix) release, LilyPond > > 2.24.3. Today I went through the list of all (smalle

LilyPond 2.25.18

We are happy to announce the release of LilyPond 2.25.18. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.3, the current stable release. Please refer to the

Re: PGP key rollover

On Sun, 2024-07-14 at 10:54 +0200, Jonas Hahnfeld wrote: > Hi all, > > heads-up for people verifying my emails: I generated a new PGP key, > attached to this message and uploaded to keyservers, that I will use > to sign my future emails. The old key has not been compromised, I > only took the oppo

PGP key rollover

Hi all, heads-up for people verifying my emails: I generated a new PGP key, attached to this message and uploaded to keyservers, that I will use to sign my future emails. The old key has not been compromised, I only took the opportunity to use newer cryptography options. Cheers Jonas 621780CB46

Re: Thoughts on next stable release(s)

On Tue, 2024-07-09 at 14:22 +0200, Thomas Morley wrote: > Please have a look at https://gitlab.com/lilypond/lilypond/-/issues/6726 > A showstopper for next stable? Thanks for the heads-up. As far as I can tell, and from local testing, this only affects the current master / unstable releas

Re: Thoughts on next stable release(s)

list of essential syntax > elements in the NR. I had a quick look through the git history since branching stable/2.24 and it seems there were many other index entries added since then, for example https://gitlab.com/lilypond/lilypond/-/commit/63da9aaeb6ed0c4e79169cdf41350a3a9244ba6e http

Re: Thoughts on next stable release(s)

On Sun, 2024-06-16 at 22:24 +0200, Jonas Hahnfeld wrote: > Hi all, > > it's been 7 months since the last stable (bugfix) release, LilyPond > 2.24.3. Today I went through the list of all (smaller) merge requests > and marked those that we might want to apply to the stable/2.

Re: Thoughts on next stable release(s)

On Mon, 2024-06-17 at 03:16 +, Werner LEMBERG wrote: > > [...] we could think about having LilyPond 2.24.4 in early / mid > > July.  What do you think? > > +1 > > I also suggest !2359. So far I didn't backport any documentation improvements to stable/2.24. Is

Thoughts on next stable release(s)

Hi all, it's been 7 months since the last stable (bugfix) release, LilyPond 2.24.3. Today I went through the list of all (smaller) merge requests and marked those that we might want to apply to the stable/2.24 branch with the Backport label: https://gitlab.com/lilypond/lilypond/-/merge_req

LilyPond 2.25.17

We are happy to announce the release of LilyPond 2.25.17. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.3, the current stable release. Please refer to the

LilyPond 2.25.16

We are happy to announce the release of LilyPond 2.25.16. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.3, the current stable release. Please refer to the

Any active Chinese translator?

Dear developers of Lilypond, I'm Lex, a regular Lilypond user now.  And I'm planning to translate the website / manuals into Chinese. Still trying to sort out the translation process. Any help / reminder would be very welcome. Done: - Gitlab account and repository cloning / for

Re: [RFC] Move GitLab testing to Ubuntu 22.04

On Wed, 2024-05-01 at 22:20 +0200, Michael Käppler wrote: > > > There is one caveat here that I would like to mention: During initial > > testing in my fork, one test job unexpectedly hang during a lilypond > > execution, using 100% CPU and eventually being killed after 60 mi

Re: [RFC] Move GitLab testing to Ubuntu 22.04

Hi Jonas, Hi all, I mentioned this during the transition to Guile 3.0, and now I had the time to prepare the required changes to move the base of our GitLab testing to Ubuntu 22.04. The merge request to do so is here: https://gitlab.com/lilypond/lilypond/-/merge_requests/2318 Many thanks for

[RFC] Move GitLab testing to Ubuntu 22.04

Hi all, I mentioned this during the transition to Guile 3.0, and now I had the time to prepare the required changes to move the base of our GitLab testing to Ubuntu 22.04. The merge request to do so is here: https://gitlab.com/lilypond/lilypond/-/merge_requests/2318 There is one caveat here that

Re: LilyPond 2.25.15

Great !!!Thanks for fixing the guile 3 bug on Windows... GillesLe samedi 20 avril 2024 à 18:18:24 UTC+2, Jonas Hahnfeld via LilyPond user discussion a écrit : We are happy to announce the release of LilyPond 2.25.15. This is termed a development release, but these are usually reliable

LilyPond 2.25.15

We are happy to announce the release of LilyPond 2.25.15. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.3, the current stable release. Please refer to the

Music property articulations

Hey all, I am trying to add articulations to my music braille generator. As stated before, I am using the event listening system proposed by the "event-listener.ly" example. Browsing through the documentation, I found the music property articulations on https://lilypond.org/doc/v2.24/Docume

Re: [RFC] Transition to Guile 3.0

Am 08.04.2024 um 23:40 schrieb Jonas Hahnfeld: Thanks for testing! I assume this is also enabling Guile optimizations during LilyPond runtime? It would be interesting to see if there's a gain from just compiling the bytecode with optimizations. That would be a one-time cost that may be

Re: [RFC] Transition to Guile 3.0

Am 08.04.2024 um 23:40 schrieb Jonas Hahnfeld: [snip] Thanks for testing! I assume this is also enabling Guile optimizations during LilyPond runtime? It would be interesting to see if there's a gain from just compiling the bytecode with optimizations. That would be a one-time cost tha

Re: [RFC] Transition to Guile 3.0

On Tue, 2024-04-02 at 16:40 +0200, Michael Käppler wrote: > Am 01.04.2024 um 22:03 schrieb Jonas Hahnfeld via Discussions on LilyPond > development: > > As pointed out by Han-Wen in November, this is actually fairly little > > code that gets dropped; we need to keep some relate

Re: [RFC] Transition to Guile 3.0

Am 01.04.2024 um 22:03 schrieb Jonas Hahnfeld via Discussions on LilyPond development: This is now up for review in the following merge request: https://gitlab.com/lilypond/lilypond/-/merge_requests/2293 As pointed out by Han-Wen in November, this is actually fairly little code that gets

Re: extracting markup texts for braille

Hi Aaron, That is a great suggestion. Thanks a lot! I have been playing around with it and noticed that in order to keep the order of the generated braille identical to the Lilypond code, I would need to also override the top-level-score-handler, and possibly others to keep track of the

Re: [RFC] Transition to Guile 3.0

On Sun, 2023-11-05 at 22:36 +0100, Jonas Hahnfeld wrote: > Step 4: Remove compatibility code for Guile 2.2 > This can happen after we made one or two releases with only Guile 3.0. This is now up for review in the following merge request: https://gitlab.com/lilypond/lilypond/-/merge_request

extracting markup texts for braille

Hey all, I also asked this question on the lilypond-user mailing list, but I gather it is a rather complex question for that list. As you might be aware, I have been working on a braille extension for Lilypond which (based on the music info extraction example) renders Lilypond scores into

Re: LilyPond 2.25.14

Hello, Here are my results for MSDM.ly on a M2 Max MacBook Pro: real 12.11 user 11.02 sys 1.06 Thanks a lot! Mathieu

Re: LilyPond 2.25.14

Am 24.03.2024 um 11:50 schrieb Jonas Hahnfeld: Just out of interest, do we tweak the JIT_THRESHOLD somewhere or do we use the default value? I don't think we change it from LilyPond, so likely using the default value. I did a test with the opposite extremes. Again, 10 subsequent runs

Re: LilyPond 2.25.14

  0m0.090s > sys 0m0.185s > > without JIT: > real    4m45.295s > user    0m0.046s > sys 0m0.277s Thanks for testing on a larger score! > Just out of interest, do we tweak the JIT_THRESHOLD somewhere or do we > use the default value? I don't think we change it from LilyP

Re: LilyPond 2.25.14

On Sat, 2024-03-23 at 14:08 -0700, Kenneth Wolcott wrote: > Hi Jonas; > > I hope that the following information is useful: > > Lilypond performance stats for the engraving of one very small and one > medium sized pieces > > native = Apple Silicon build > foreign = x

Re: LilyPond 2.25.14

On Sat, 2024-03-23 at 14:24 -0500, Karlin High wrote: > On 3/23/2024 2:00 PM, Jonas Hahnfeld wrote: > > Would be interesting to see how this compares to the "vanilla" package > > I tried it, 3 runs. First one maybe unfair because font cache > initialization or something. > > real0m48.643s >

Re: LilyPond 2.25.14

On Sun, 2024-03-24 at 03:20 -0700, Aaron Hill wrote: > The error occurred from my WSL1 environment running Ubuntu 18.04. > Probably my own fault for keeping bionic around. Ah ok; yes, Ubuntu 18.04 is end-of-life since last year already, so I didn't check its versions. > I do have Ubuntu 20.04 u

Re: LilyPond 2.25.14

On Sat, 2024-03-23 at 18:18 -0700, Aaron Hill wrote: > On 2024-03-23 6:25 am, Jonas Hahnfeld wrote: > > We are happy to announce the release of LilyPond 2.25.14. This is > > termed a development release, but these are usually reliable for > > testing new features and recent b

Re: LilyPond 2.25.14

ce in the second and third page, as if I had inserted > a forced page break in two or three places. There were no conversion > errors or warnings in any of my engravings. > > I don't know what was the cause of the speedup, but it is > appreciated! I have been using the MacPorts v

Re: LilyPond 2.25.14

On Sat, 2024-03-23 at 17:46 +0100, Jean Abou Samra wrote: > Le samedi 23 mars 2024 à 16:02 +0100, Jonas Hahnfeld via Discussions on > LilyPond development a écrit : > > Native Apple Silicon build: https://cloud.hahnjo.de/s/x9D62eASSn6Ng7D > > This is a native arm64 ve

Re: LilyPond 2.25.14

On Sat, 2024-03-23 at 11:41 -0500, Karlin High wrote: > On 3/23/2024 10:02 AM, Jonas Hahnfeld via LilyPond user discussion wrote: > > Windows build with Guile JIT: https://cloud.hahnjo.de/s/Ek5x9rybpiPNtoj > > This turns on just-in-time compilation that was added in Guile 3.0, but

Re: LilyPond 2.25.14

On Sat, 2024-03-23 at 14:25 +0100, Jonas Hahnfeld wrote: > We are happy to announce the release of LilyPond 2.25.14. This is > termed a development release, but these are usually reliable for > testing new features and recent bug fixes. Following this release, I made two special builds

LilyPond 2.25.14

We are happy to announce the release of LilyPond 2.25.14. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.3, the current stable release. Please refer to the

[RFC] Upgrade platforms for official binaries

Hi all, as noted in https://gitlab.com/lilypond/lilypond/-/merge_requests/2246, we are starting to run into some issues because of dated software in CentOS 7 and Ubuntu 20.04. For that reason, I'm proposing in https://gitlab.com/lilypond/lilypond/-/merge_requests/2261 to upgrade our plat

LilyPond 2.25.13

We are happy to announce the release of LilyPond 2.25.13. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.3, the current stable release. Please refer to the

Auto-resetting of context properties

Folks, the following is triggered mainly (but not solely) by my short exchange with Dan (https://gitlab.com/lilypond/lilypond/-/merge_requests/1617#note_1735195563): We have some context properties that are persistent (e.g. figuredBassPlusDirection), whereas others are effective once and

Re: [RFC] Transition to Guile 3.0

mple because the system is missing the development package for Guile > 3.0... This next step (requiring Guile 3.0 and removing automatic detection of Guile 2.2 from configure) is now available as https://gitlab.com/lilypond/lilypond/-/merge_requests/2228 Jonas signature.asc Description: This is a digitally signed message part

LilyPond 2.25.12

We are happy to announce the release of LilyPond 2.25.12. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.3, the current stable release. Please refer to the

Re: numbers

On 2023-12-27 10:51 pm, Werner LEMBERG wrote: Well, both `#+3` and `#-3` work, so it might be tempting to assume that `+3` and `-3` also work (outside of `\markup`). So does ##e+3.0 and so does #3/1 so should we be supporting those as well? The former? Rather not. The latter, maybe. I can

Re: Can't automatically merge

On Thu, 2023-12-14 at 17:43 +, Werner LEMBERG wrote: > > > > Looks like it was fixed? > > > > https://status.gitlab.com/pages/history/5b36dc6502d06804c08349f7 > > > > > > Yep, thanks. > > > > I spoke too early – it's still not working properly. > > On this page I read: > >   For self-hosted

LilyPond 2.25.11

We are happy to announce the release of LilyPond 2.25.11. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.3, the current stable release. Please refer to the

Re: [RFC] Transition to Guile 3.0

On Sun, 2023-11-05 at 22:36 +0100, Jonas Hahnfeld wrote: > Step 3: Switch to Guile 3.0 > Afterwards, we can merge > https://gitlab.com/lilypond/lilypond/-/merge_requests/2163 I put the merge request back on Patch::review, along with https://gitlab.com/lilypond/lilypond/-/merge_requests

LilyPond 2.24.3 released!

We are proud to announce the release of GNU LilyPond 2.24.3. LilyPond is a music engraving program devoted to producing the highest-quality sheet music possible. It brings the aesthetics of traditionally engraved music to computer printouts. This version contains a number of fixes since the

Re: Plan for LilyPond 2.24.3

, in case anybody wants to test before the official announcement tomorrow (evening): https://gitlab.com/lilypond/lilypond/-/packages/20395285 Cheers, Jonas signature.asc Description: This is a digitally signed message part

Re: LilyPond 2.25.10 with Guile 3.0

On Thu, 2023-11-16 at 11:11 -0600, Karlin High wrote: > On Sun, Nov 12, 2023 at 6:26 AM Jonas Hahnfeld via LilyPond user > discussion wrote: > > If you have some time, please test them in your setups and report back in > > case of problems! > > Seems OK so far. Window

Plan for LilyPond 2.24.3

er 18, and the final release on Sunday, November 19 - in the worst case this may slip to Monday, but I don't really have much time then so hopefully not... The draft release announcement text is: --- We are proud to announce the release of GNU LilyPond 2.24.3. LilyPond is a music engraving pro

LilyPond 2.25.10 with Guile 3.0

On Sat, 2023-11-11 at 19:37 +0100, Jonas Hahnfeld wrote: > We are happy to announce the release of LilyPond 2.25.10. And here are the binaries with Guile 3.0, built using https://gitlab.com/lilypond/lilypond/-/merge_requests/2163 and https://gitlab.com/lilypond/lilypond/-/merge_requests/2

Re: [RFC] Transition to Guile 3.0

On Sat, 2023-11-11 at 18:37 +0100, Han-Wen Nienhuys wrote: > On Sun, Nov 5, 2023 at 10:36 PM Jonas Hahnfeld wrote: > > Hi all, > > > > I hear LilyPond hasn't changed its Guile version since some time (more > > than 18 months). So before we get too comfortable wit

LilyPond 2.25.10

We are happy to announce the release of LilyPond 2.25.10. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.2, the current stable release. Please refer to the

Plan for LilyPond 2.24.3 and Transition to Guile 3.0

On Sun, 2023-11-05 at 22:36 +0100, Jonas Hahnfeld wrote: > Step 1: Officially support Guile 3.0 and add optional CI testing > I opened https://gitlab.com/lilypond/lilypond/-/merge_requests/2162 to > add some compatibility with earlier versions of Guile 3.0 and then > implement detectio

Re: [RFC] Transition to Guile 3.0

On Sun, 2023-11-05 at 22:48 +0100, Jean Abou Samra wrote: > What I don't really understand is why you want to add compatibility > with Guile 3.0.x for small x. Upstream completely breaks the normal > expectation from what you would find in a point release, by putting > features and even severely ba

[RFC] Transition to Guile 3.0

Hi all, I hear LilyPond hasn't changed its Guile version since some time (more than 18 months). So before we get too comfortable with the current situation, let me propose to move to Guile 3.0. Below is a plan for that switch, with a transition period to test the official binaries. Last

SVGs in Documentation

I noticed that the online documentation often uses PNG images of the engraving output, rather than SVG images.  Now that SVG images are widely supported in browsers, perhaps we should consider transitioning the documentation to SVG images.  I'm sure that this would be a low priority, but it woul

LilyPond 2.25.9

We are happy to announce the release of LilyPond 2.25.9. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.2, the current stable release. Please refer to the

Re: [RFC] HTML documentation with texi2any

On Sun, 2023-09-03 at 14:40 +0200, Jonas Hahnfeld via Discussions on LilyPond development wrote: > For a possible timeline, we could wait for the release of LilyPond > 2.25.8 (probably September 16/17 because I'm travelling next weekend, > unless Jean wants to do it again) and

Re: Add a property `jianpuBeaming` needed to support Jianpu (numbered musical notation).

t does not interfere with the existing code, which I agree is quite complex. -- Sent with Tutanota, enjoy secure & ad-free emails. Sep 21, 2023, 06:37 by j...@abou-samra.fr: > Le mercredi 20 septembre 2023 à 05:06 +0200, yuanyelele--- via Discussions on > LilyPond developme

Re: Add a property `jianpuBeaming` needed to support Jianpu (numbered musical notation).

Attached is a sample of Jianpu notation. The two patches I submitted are necessary for the underlines to function correctly here. -- Sent with Tutanota, enjoy secure & ad-free emails. Sep 20, 2023, 14:41 by w...@gnu.org: >> These two patches introduce a boolean context property called >> j

Add a property `jianpuBeaming` needed to support Jianpu (numbered musical notation).

Dear list, I'm currently bug fixing and improving an older script, jianpu10a.ly <https://github.com/nybbs2003/lilypond-Jianpu/blob/master/jianpu10a.ly>, which aims to introduce Jianpu (numbered musical notation) <https://en.wikipedia.org/wiki/Numbered_musical_notation>

Re: [RFC] HTML documentation with texi2any

On Sun, 2023-09-03 at 14:40 +0200, Jonas Hahnfeld wrote: > For a possible timeline, we could wait for the release of LilyPond > 2.25.8 (probably September 16/17 because I'm travelling next weekend, > unless Jean wants to do it again) and then merge the changes right > afte

LilyPond 2.25.8

We are happy to announce the release of LilyPond 2.25.8. This is termed a development release, but these are usually reliable for testing new features and recent bug fixes. However, if you require stability, we recommend using version 2.24.2, the current stable release. Please refer to the

Re: Source tarballs on lilypond.org

On Sun, 2023-09-03 at 15:18 +0200, Jean Abou Samra wrote: > Le dimanche 03 septembre 2023 à 14:48 +0200, Jonas Hahnfeld a écrit : > > Can you please > > change it to something more like: > > "IMPORTANT: Binaries and documentation archives are NOT updated on > > lilypond.org anymore, please refer to

Re: Source tarballs on lilypond.org

On Sun, 2023-09-03 at 14:29 +0200, Jean Abou Samra wrote: > Le vendredi 01 septembre 2023 à 19:56 +0200, Jonas Hahnfeld a écrit : > > Yes, could be a good idea. Looking at the directory, it seems like the > > contents of README.html are displayed below the list of directories, > > maybe we should u

[RFC] HTML documentation with texi2any

reverting https://gitlab.com/lilypond/lilypond/-/merge_requests/1109 It is (in my opinion) a very minor cosmetic change and, as you can read up in that merge request, it already hit some objections when it was introduced one and a half years ago. With texi2any, we do not have the same customization hook

Re: Source tarballs on lilypond.org

On Fri, 2023-09-01 at 16:25 +0200, Jean Abou Samra wrote: > > As for the issue, I consider that somewhat of an outlier: Most users > > will follow the links on the website, and everything will work for > > them. A small fraction tries to find the binaries where they used to be > > (and I'm surprise

Re: Source tarballs on lilypond.org

On Fri, 2023-09-01 at 14:31 +0200, Jean Abou Samra wrote: > Hi, > > Per the release procedure > https://lilypond.org/doc/v2.25/Documentation/contributor/release-checklist , > GitLab releases for LilyPond contain both binaries + doc tarballs and source > tarballs generate by &quo

Prototype for HTML documentation with texi2any

Hi all, after months of preparations (if not years) and actual implementation work during the last few weekends, I would like to share the first complete prototype for generating LilyPond's HTML documentation with texi2any: https://gitlab.com/lilypond/lilypond/-/merge_requests/2089 Befor

LilyPond 2.24.2 released!

We are proud to announce the release of GNU LilyPond 2.24.2. LilyPond is a music engraving program devoted to producing the highest-quality sheet music possible. It brings the aesthetics of traditionally engraved music to computer printouts. This version contains a number of fixes since the

Re: Plan for LilyPond 2.24.2

On Tue, 2023-08-08 at 10:57 +0200, Jonas Hahnfeld via Discussions on LilyPond development wrote: > I finally have (fixed) internet again! With that, the plan would be to > first check for additional backports and then build the binaries during > the week, probably tomorrow or Thursday.

Re: Plan for LilyPond 2.24.2

Hi all, On Fri, 2023-07-28 at 08:28 +0200, Jonas Hahnfeld via Discussions on LilyPond development wrote: > On Sat, 2023-07-08 at 15:29 +0200, Jonas Hahnfeld via Discussions on > LilyPond development wrote: > > On Sat, 2023-07-01 at 15:02 +0200, Jonas Hahnfeld via Discussions on

Re: Flex on macOS

On Mon, 2023-07-31 at 09:54 +0200, Jean Abou Samra wrote: > > Yes, but flex has always been there as a dependency of some other > > package I think, only not added in your environment variables. We can > > explicitly add it to the Brewfile if you think that's better, but it > > shouldn't change the

Re: Flex on macOS

On Mon, 2023-07-31 at 01:15 +0200, Jean Abou Samra wrote: > Hi, > > As a follow-up to the release: on macOS I encountered a quirk which is > that the compiler spit out build errors on the Flex-generated lexer > out/lexer.cc. (Now I find myself stupid for not saving the error messages > somewhere.)

Re: fix-docsize errors in build-doc.sh

On Sun, 2023-07-30 at 18:31 +0200, Jean Abou Samra wrote: > Trying to do the release, I got these messages during "./build-doc.sh": > > [...] > > Is that expected? Yes, it has always been there for the online pages because the big- pages use language content negotiation and aren't valid file nam

Re: Plan for LilyPond 2.24.2

On Sat, 2023-07-08 at 15:29 +0200, Jonas Hahnfeld via Discussions on LilyPond development wrote: > On Sat, 2023-07-01 at 15:02 +0200, Jonas Hahnfeld via Discussions on > LilyPond development wrote: > > I plan to build the binaries next weekend, July 8th or 9th, for > > th

Re: Cannot build latest master branch

On 2023-07-27 05:22, Jean Abou Samra - jean(a)abou-samra.fr wrote: By the way, where are all those compiler flags coming from? Did you write them by hand? Did you copy them from somewhere? These flags are mostly for a better debugging experience and strengthened security. A lot of them are co

Re: Cannot build latest master branch

On 2023-07-26 14:13, Jean Abou Samra - jean(a)abou-samra.fr wrote: Yes, I deleted the build directory before redoing autogen.sh, redid `mkdir build && cd build` in between autogen.sh and configure Then you failure is pretty strange. Can you show the output of "build/out/bi

Re: Cannot build latest master branch

On 2023-07-26 11:51, Jean Abou Samra - jean(a)abou-samra.fr wrote: I'm not sure we understand "clean build" in the same way. I get that you rerun autogen and configure, but are you starting from a completely empty build directory? Yes, I deleted the build directory before redoing autogen.sh,

Re: Cannot build latest master branch

On 2023-07-26 11:17, Jean Abou Samra - jean(a)abou-samra.fr wrote: I also got the compilation error, but after adding , my locally built LilyPond works fine. Is this from a clean build? Yes. After redoing: * ./autogen.sh --noconfigure * ../configure --prefix=/home/lj/projects/internships

Re: Plan for LilyPond 2.24.2

On Mon, 2023-07-17 at 07:08 +0200, Jean Abou Samra wrote: > Le samedi 08 juillet 2023 à 15:29 +0200, Jonas Hahnfeld via Discussions on > LilyPond development a écrit : > > Unfortunately, this won't happen: My fiber is cut and I don't have > > (fixed) internet 😞 and wh

Re: Plan for LilyPond 2.24.2

On Sat, 2023-07-01 at 15:02 +0200, Jonas Hahnfeld via Discussions on LilyPond development wrote: > I plan to build the binaries next weekend, July 8th or 9th, for > the final release on Wednesday, July 12th. Unfortunately, this won't happen: My fiber is cut and I don't have (fi

Re: `make bytecode && make doc` broken

On Sat, 2023-07-08 at 10:20 +, Werner LEMBERG wrote: > Currently, `make bytecode && make doc` is broken: https://lists.gnu.org/archive/html/lilypond-devel/2023-07/msg8.html (it's not like there are hundreds of messages every day, a duplicate thread doesn

  1   2   3   4   5   6   7   8   9   10   >