Re: Assertion failed

anders.vin...@bek.no writes: > a> a4cc910a Issue 2787: Sanitize usage of -DDEBUG, -DNDEBUG and assert > > With the change from -NDEBUG to -DEBUG in commit , quite a few > scores makes lilypond crash. The same happens with releases since then > (19.21++). The behavior is the same whether

Re: NR 3.6.1, Displaying LilyPond notation

Federico Bruni writes: > Hi all > > I'm completing the translation of the 3rd chapter of Notation > Reference and I'm having problems with translating this section: > http://www.lilypond.org/doc/v2.19/Documentation/notation/displaying-lilypond-notation > > Isn't it unclear or

Re: NR 3.6.1, Displaying LilyPond notation

Il giorno ven 4 dic 2015 alle 15:52, David Kastrup ha scritto: Well, no, that isn't what is meant by "interpreted". How about: The music function \displayLilyMusic displays the following music expression while also retaining it as part of the surrounding expression. This is

NR 3.6.1, Displaying LilyPond notation

Hi all I'm completing the translation of the 3rd chapter of Notation Reference and I'm having problems with translating this section: http://www.lilypond.org/doc/v2.19/Documentation/notation/displaying-lilypond-notation Isn't it unclear or it's just me? ...in particular the last paragraph of

Kneed beam and subdivisions

Hello bug squad, I would like to report a "ugly" type of bug. When using kneed beams, LilyPond does not set a "main beam" around which all subdivisions are created. The result is not only extremely confusing in some cases, but also absolutely non-standard. For instance, the code below: