pygments: `\foo` not always rendered as bold
I've noticed in the NR that stuff like `\foo` isn't always coloured as expected (i.e., `\foo` isn't always bold). Attached are two examples from the NR. I wonder whether it makes sense to always embolden stuff starting with `\` (except in a string). This might even include `\1` and friends. Werner
PATCHES - Countdown to September 21
Here is the current countdown report. The next countdown will begin on September 21, mateys! (It be Talk like a pirate day.) A list of all merge requests can be found here: https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority Push: !1625 Remove translation-status - Jonas Hahnfeld https://gitlab.com/lilypond/lilypond/-/merge_requests/1625 !1624 Fix ly:position-on-line? - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1624 !1623 Store accidental glyph name in 'glyph-name property - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1623 Countdown: !1622 Slur should not care for last dotted note - Martín Rincón Botero https://gitlab.com/lilypond/lilypond/-/merge_requests/1622 Review: !1632 skyline.cc: Use binary search in height () method - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1632 !1631 Print warning for unterminated tie at end of input - Martín Rincón Botero https://gitlab.com/lilypond/lilypond/-/merge_requests/1631 !1629 Use safety margin when attributing penalties to non-horizontal slurs - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1629 !1510 Better source locations for Scheme errors - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1510 New: !1616 Add text marks - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1616 Waiting: !1610 RFC: Require Cairo for building - Jean Abou Samra https://gitlab.com/lilypond/lilypond/-/merge_requests/1610 !1578 New margins by default - Martín Rincón Botero https://gitlab.com/lilypond/lilypond/-/merge_requests/1578 Cheers, Colin
Re: LilyPond 2.23.13
Hello Jean !
Error 1073741819
\version "2.23.13"
$@(map (lambda (i)
#{
\bookpart {
\score {
\repeat unfold 100 c'1
}
}
#})
(iota 300))
Block on Fitting music on 171 or 172 pages...
\version "2.23.13"
$@(map (lambda (i)
#{
\score {
\repeat unfold 100 c'1
}
#})
(iota 300))
Le dimanche 18 septembre 2022 à 23:23:27 UTC+2, Jean Abou Samra
a écrit :
Le 18/09/2022 à 18:49, Jonas Hahnfeld via LilyPond user discussion a écrit :
> We are happy to announce the release of LilyPond 2.23.13. This is
> termed a development release, but these are usually reliable. However,
> if you require stability, we recommend using version 2.22.2, the
> current stable release. Please refer to the Installing section in the
> Learning Manual for instructions how to set up the provided binaries:
> https://lilypond.org/doc/v2.23/Documentation/learning/installing
A little call for testing:
There has been a bug for a while in the 2.23 series, happening only
on Windows, which would result in sporadic crashes with return code
-1073741819. See https://gitlab.com/lilypond/lilypond/-/issues/6361
if you are interested in further information.
In this release, the frequency at which the bug occurs seems much reduced,
although it can still be triggered under very specific circumstances
with Scheme code if you really try hard.
If you are on Windows, we encourage you to test this release on any
scores you might have, especially larger scores. If you encounter
any trouble, please get back to us on the bug-lilypond list
(bug-lilyp...@gnu.org). If this bug still occurs under real-world
conditions, we would like to know it.
Thank you.
Re: Fixing regressions and serious issues
Le 18/09/2022 à 18:35, Jonas Hahnfeld a écrit : On Sun, 2022-09-18 at 18:17 +0200, Jean Abou Samra wrote: By the way, if you happen to still have a binary of what is now 2.23.13 with debugging symbols, that would save me time. Yes, I always try to keep around the latest build, for accessing logs and debug symbols. I uploaded the lilypond.exe before stripping here: https://cloud.hahnjo.de/index.php/s/ZB8mG82TNpLwi3b Let me know if you also need the Dlls. I'd like to investigate the crash when loading the edition-engraver, which is 100% reproducible for me, but at a glance doesn't seem related to this GC Heisenbug. I saw your comment, but you need an account to even read the openlilylib forum, so I didn't bother... OK, I've tracked this one down, and sadly it's not going to be fun either. https://gitlab.com/lilypond/lilypond/-/issues/6430
