Re: BDWGC fix in 2.24?
Le 23/11/2022 à 23:47, Jonas Hahnfeld a écrit : I played a bit this week, and at least the crash for the score in https://lists.gnu.org/archive/html/lilypond-user/2022-11/msg00272.html (which is finally a crash that I can reproduce) seems to be solved by the current tip of the release-8_2 branch. A minimal backport of that commit on its own also seems to work. However, my original plan was to keep the current workaround in place *and* backport a minimal version of the fix. For some inexplicable reasons, this avoids the crash but then just hangs after printing the warning (that I did not patch). This doesn't make me feel comfortable doing any last minute change in that area, potentially breaking things even worse, and I will not do it for this weekend. Makes sense. Let's try this for 2.24.1, then? Jean OpenPGP_signature Description: OpenPGP digital signature
Guile potentially changing its GC a second time
Had anyone seen this?? https://github.com/wingo/whippet-gc This looks like something we will need to watch. If Guile switches from BDWGC to whippet-gc, I really hope LilyPond won't need too much adapting and crazy debugging, but only God knows. If even... There is quite a bit of chat about it on https://wingolog.org/ Jean OpenPGP_signature Description: OpenPGP digital signature
PATCHES - Countdown to November 25
Here is the current countdown report. The next countdown will begin on November 25th. A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !1721 Unify and fix grob property type checks - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1721 Countdown: !1742 Matrix cleaning - Dan Eble https://gitlab.com/lilypond/lilypond/-/merge_requests/1742 !1741 Avoid SCM_I_* macros - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1741 !1740 hyphenate-internal-words.scm: Minor improvement - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/1740 !1739 Make generated web pages valid HTML - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/1739 !1738 Doc: Use braces in \scaleDurations example - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1738 !1737 Whole note tremolos (and longer) don't collide with accidentals - Martín Rincón Botero https://gitlab.com/lilypond/lilypond/-/merge_requests/1737 !1736 Improvements for generated appendix section titles - Werner Lemberg https://gitlab.com/lilypond/lilypond/-/merge_requests/1736 !1735 Doc: Explain the dangers of \postscript - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1735 Review: No patches in Review at this time. New: No patches in New at this time. Waiting: !1710 Web: Update Download part for 2.24 - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1710 Cheers, Colin
Re: BDWGC fix in 2.24?
On Sat, 2022-11-19 at 22:29 +0100, Jonas Hahnfeld via Discussions on LilyPond development wrote: > > In https://github.com/ivmai/bdwgc/issues/454#issuecomment-1313127991 > > the BDWGC maintainer said the release of his fix would > > probably happen in January, which is later than what we > > hope for our 2.24 release. > > > > What should we do? Do we accept releasing 2.24 from > > the release-8_2 branch in BDWGC even though it is not > > released? Do we keep the current workaround, which still > > gives some crashes? Do we replace our workaround > > with Ivan Maidanski's patch, which seems to apply cleanly > > on the v.8.2.2 tag? > > I personally think this should not block the release, simply because > big scores have been a pain point on Windows before due to 32-bit > limitations [1]. It would of course be nice to fix it (and _maybe_ we > can patch in only the minimal parts of the patch) I played a bit this week, and at least the crash for the score in https://lists.gnu.org/archive/html/lilypond-user/2022-11/msg00272.html (which is finally a crash that I can reproduce) seems to be solved by the current tip of the release-8_2 branch. A minimal backport of that commit on its own also seems to work. However, my original plan was to keep the current workaround in place *and* backport a minimal version of the fix. For some inexplicable reasons, this avoids the crash but then just hangs after printing the warning (that I did not patch). This doesn't make me feel comfortable doing any last minute change in that area, potentially breaking things even worse, and I will not do it for this weekend. Jonas signature.asc Description: This is a digitally signed message part
Re: Prefer luatex for documentation
Le 22/11/2022 à 22:57, Jean Abou Samra a écrit : OK, I'll do a one-core test. pdfTeX: real 29m37,883s user 28m28,375s sys 2m9,725s LuaTeX: real 30m42,967s user 29m14,973s sys 2m31,694s This is with a single core, in the same configuration as in CI (with --ci passed to autogen.sh, implying the use of the GS API, and without extractpdfmark). As you can see, the difference is noticeable but not worrisome. Jean OpenPGP_signature Description: OpenPGP digital signature
Re: Prefer luatex for documentation
> On 19 Nov 2022, at 11:19, Werner LEMBERG wrote: > > In https://gitlab.com/lilypond/lilypond/-/merge_requests/1714 I > suggest that we prefer luatex for building the documentation. What do > people think? The people that developed LuaTeX also developed ConTeXt, but the latter has now switched to LMTX (LuaMetaTeX). This means that the font support has been varied between the two. I found it difficult to extract the ConTeXt parts for use with LuaTeX only, but that may be how LaTeX does it.
