Re: [Bug] LilyPond Crash (return code -1073741819) - reproduceable?

2014-06-14 Thread Jakob Schöttl
Am 14.06.2014 21:05, schrieb James: On 25/05/14 10:09, Jakob Schöttl wrote: Sorry for that mess.. Am 25.05.2014 08:06, schrieb James: Jakob Don't forget to include the bug list That error code is a general Windows return code. (0xc005) so it doesn't really give anything much to work with

Re: Possible bug with \oneVoice involving rests

2014-06-14 Thread David Kastrup
James writes: > On 02/06/14 17:38, David Kastrup wrote: >> Yes, that's plausible, but your above reasoning about << >> remains >> incorrect. >> >> Things are more readable if you revert to << >> only when you indeed >> want parallel voices rather than just multiple notes in a chord. But >> they

Re: [Bug] LilyPond Crash (return code -1073741819) - reproduceable?

2014-06-14 Thread James
On 25/05/14 10:09, Jakob Schöttl wrote: > Sorry for that mess.. > > Am 25.05.2014 08:06, schrieb James: >> Jakob >> >> Don't forget to include the bug list >> >> That error code is a general Windows return code. (0xc005) so it >> doesn't really give anything much to work with except that it loo

Re: Possible bug with \oneVoice involving rests

2014-06-14 Thread James
On 02/06/14 17:38, David Kastrup wrote: > Urs Liska writes: > >> Am 02.06.2014 09:51, schrieb Brian Eve: >>> \version "2.18.2-1" >>> >>> { >>> \clef bass >>> \compressFullBarRests >>> \override Rest #'staff-position = #0 >>>R1*6 >>> << g4. e >> << f d >> <> >>>a1 >>>R1*6 >>> << b8 e8

Re: simultaneous tempo-change events

2014-06-14 Thread James
On 07/06/14 11:36, Federico Bruni wrote: > 2014-06-02 15:56 GMT+02:00 Knute Snortum : > >> That's fine. It just took me a couple of minutes to figure out that it was >> the compile last measures feature making the warning. Maybe a note in the >> documents saying that the feature can produce oddit