Re: lilypond 2.11.50-2 still crashes (windows xp sp3)

Hi Valentin, I have no longer problems for compiling Lily and the docs from recent Git master branch. IIRC the segfault went away a few commits after .50. Cheers, John 2008/7/12, Valentin Villenave <[EMAIL PROTECTED]>: > 2008/7/7 John Mandereau <[EMAIL PROTECTED]>: >> On 2008/07/07 06:16 +, E

Re: [repost] CR/LF regression in Mac OS X Lilypond editor

Hi Valentin, this has now been added as http://code.google.com/p/lilypond/issues/detail?id=643 Thanks! Kieren. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: \set chordChanges troubles

2008/7/11 Werner <[EMAIL PROTECTED]>: > % unfortunately \set chordChanges doesn't work twice... Greetings Werner, Gee, I'm afraid this is too much for me... Could you try to remove anything you can and provide me with a *minimal* example that triggers the bug? Besides, you might want to use \ver

Issue 647 in lilypond: Collision accidentals/TimeSignature

Issue 647: Collision accidentals/TimeSignature http://code.google.com/p/lilypond/issues/detail?id=647 New issue report by v.villenave: % In the following example, the accidentals collide with the second % time signature. \version "2.11.51" \relative { \time 3/4 8-> r r2 \time 4/4 8-> r r4 r2 }

Re: lilypond 2.11.50-2 still crashes (windows xp sp3)

2008/7/7 John Mandereau <[EMAIL PROTECTED]>: > On 2008/07/07 06:16 +, E.Weehaeli wrote: >> Here is the log I get (without the verbose option, the log is empty): >> >> GNU LilyPond 2.11.50 > I got a similar problem with a binary self-compiled source from Git a > few commits before : LilyPond us

Re: 2.11.50-2 crashes mac ppc

2008/7/7 Stan Sanderson <[EMAIL PROTECTED]>: > A file which previously compiled on 2.11.49 crashes on 2.11.50-2. Report > below. Greetings Stan, Is this bug still happening with 2.11.51? Cheers, Valentin ___ bug-lilypond mailing list bug-lilypond@gn

Re: accidentals collide with time signature (was Re: position of accidentals)

2008/7/7 Wilbert Berendsen <[EMAIL PROTECTED]>: >> in the below quoted example, the positions of the accidentals are not >> convincing, in my opinion. Is there a possibilitie to change this >> generally? > > I rewrote your example just to make it more readable (it's a good habit to > place command

Issue 646 in lilypond: Collision note/clef due to translated markup

Issue 646: Collision note/clef due to translated markup http://code.google.com/p/lilypond/issues/detail?id=646 New issue report by v.villenave: % In the following example, the clef collides with the previous note % because of the translated markup. \version "2.11.51" << \new Staff { \clef trebl

Re: Note/clef collision due to translated TextScript markup

2008/7/6 Nicolas Sceaux <[EMAIL PROTECTED]>: > In the following example, the clef collides with the previous note, > because of the translated markup. Hi Nicolas, your bug has been added as http://code.google.com/p/lilypond/issues/detail?id=646 Cheers, Valentin

Re: \transposition + partcombine + midi

2008/7/3 Mark Pim <[EMAIL PROTECTED]>: > OK, accepted, but the basic bug still stands (as I see it); my sample file > causes the flute part (which is not transposed) to be affected by the > \transposition command in the partcombined music. Indeed, this is weird. Added as http://code.google.com

Issue 645 in lilypond: midiInstrument + \transposition + \partcombine = wrong MIDI output

Issue 645: midiInstrument + \transposition + \partcombine = wrong MIDI output http://code.google.com/p/lilypond/issues/detail?id=645 New issue report by v.villenave: % Here's a weird one... \version "2.11.50" untransposed = \relative c'' { c4 c d d } transposed = \relative c'' { % Setting th

Re: LilyPond 2.11.50 crashes on Windows

2008/7/3 Thomas Scharkowski <[EMAIL PROTECTED]>: > LilyPond 2.11.50 crashes on Windows XP SP2 without warning. > No logfile is created. Greetings, have you tried with the latest 2.11.51 version? Cheers, Valentin ___ bug-lilypond mailing list bug-lily

Issue 644 in lilypond: Large files compilation fails on 32-bit GNU/Linux

Issue 644: Large files compilation fails on 32-bit GNU/Linux http://code.google.com/p/lilypond/issues/detail?id=644 New issue report by v.villenave: An user reports that LilyPond-book fails when compiling a large number of snippets on a 4G-RAM machine: http://lists.gnu.org/archive/html/bug-lilyp

Re: lilypond-book runs out of memory: large file compilatioin fails

2008/7/2 Nikita <[EMAIL PROTECTED]>: > The problem is that lilypond-book script tries to dissect any file in one pass > and runs out of memory if the file is very large. The solution that worked for > me was to split the file and process it by parts. That could probably be coded > within lilypond-

Re: [repost] CR/LF regression in Mac OS X Lilypond editor

2008/6/27 Kieren MacMillan <[EMAIL PROTECTED]>: > Has anyone else run into issues with the way the Lilypond editor (Mac OS X > 10.4) handles CR/LF? Hi Kieren, this has now been added as http://code.google.com/p/lilypond/issues/detail?id=643 Hopefully someone with a clue will address it at some

Issue 643 in lilypond: OSX LilyPad editor: end of lines are unconvenient

Issue 643: OSX LilyPad editor: end of lines are unconvenient http://code.google.com/p/lilypond/issues/detail?id=643 New issue report by v.villenave: Kieren had reported that the integrated LilyPond editor (OSX 10.4) doesn't handle CR/LF end of lines correctly. (It might be a regression from 2.10.

Re: Percent repeat killed after line wrap

2008/6/23 Roman Stawski <[EMAIL PROTECTED]>: > When using percent repeats in a score with \RemoveEmptyStaffContext, > repeated bars disappear after a line wrap. Thanks, added as http://code.google.com/p/lilypond/issues/detail?id=642 Cheers, Valentin

Issue 642 in lilypond: Percent repeats are ignored by \RemoveEmptyStaffContext

Issue 642: Percent repeats are ignored by \RemoveEmptyStaffContext http://code.google.com/p/lilypond/issues/detail?id=642 New issue report by v.villenave: % In the following example, there should be two staves on the % second system. \version "2.11.51" << \new Staff { c''1 c'' \break c'' c'' } \