Re: Lilypond bug "Exited with return code-1073741819" & workaround

mclaren, 2016-11-06 2:28 GMT+01:00 mclaren : > This simple example crashes Lilypond. It's not a simple example. If you want to announce a bug provide a minimal example, as others said already. More below. > You wouldn't think putting > 6 broken tuplets into a measure

RE: Lilypond bug "Exited with return code-1073741819" & workaround

o I think I've gotten Lilypond to force page breaks now, so that should be less of an issue in the examples I post. -- View this message in context: http://lilypond.1069038.n5.nabble.com/Lilypond-bug-Exited-with-return-code-1073741819-workaround-tp196195p196199.html Sent from the User mailin

RE: Lilypond bug "Exited with return code-1073741819" & workaround

Hello mclaren (do you have a name for us?) There's a willing community here ready to help, but we expect MWE's - minimal working examples. I think that's only fair and reasonable, and has a long tradition on this list. Please refer to this guideline: http://lilypond.org/tiny-examples.html Do

Re: Lilypond bug "Exited with return code-1073741819" & workaround

Am 06.11.2016 um 02:28 schrieb mclaren: > This simple example crashes Lilypond. This is not a simple example. If you think you've come across a bug please create a "tiny example" (http://lilypond.org/tiny-examples.html), "an example from which nothing can be removed" and report it to

Lilypond bug "Exited with return code-1073741819" & workaround

} c8 \tuplet 7/4 {c8[ c8]} } \bar "|" } >> <http://lilypond.1069038.n5.nabble.com/file/n196195/EXAMPLE_43b-extensive_broken_tuplets_w_large_time_sig-FIXED.jpg> -- View this message in context: http://lilypond.1069038.n5.nabble.com/Lilypond-bug-Exited-with-return-code-1073741819-workaround-tp196195.html Sent from the User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user