This doesn’t crash in current master.
Am 19.10.19 um 21:11 schrieb Mats Bengtsson:
Sorry, here comes the buggy example:
\version "2.19.83"
\relative c'{
\time 2/4
% This first line gives the error:
d16 d64-. ( d-. d-. d-. ) e16 e16:64 fis16 fis16:64 g16 g16:64 |
% Explicitly shortening the bea
Sorry, here comes the buggy example:
\version "2.19.83"
\relative c'{
\time 2/4
% This first line gives the error:
d16 d64-. ( d-. d-. d-. ) e16 e16:64 fis16 fis16:64 g16 g16:64 |
% Explicitly shortening the beam helps:
d16 [ d64-. ( d-. d-. d-. )] e16 e16:64 fis16 fis16:64 g16 g16:64 |
% Very s
Hi,
The following example illustrates a bug in 2.19.83 that's a regression
against 2.18. Compiling with 2.19.83 gives
GNU LilyPond 2.19.83
Processing `bug.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...lilypond:
/home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.
