Re: \once causes segfault

2004-09-29 Thread Christoph Ludwig
On Wed, Sep 29, 2004 at 01:08:11PM +0200, Mats Bengtsson wrote: > However, your example points to another strange bug/feature, namely > that when you set the properties subdivideBeams or beatLength, > the setting applies also to the beam of the last note before the > setting. Example: [...] > I thi

Re: \once causes segfault

2004-09-29 Thread Mats Bengtsson
When you say \once, the setting basically only applies to the next note, that's why I asked about what you really had in mind. However, your example points to another strange bug/feature, namely that when you set the properties subdivideBeams or beatLength, the setting applies also to the beam of t

Re: \once causes segfault

2004-09-29 Thread Christoph Ludwig
On Wed, Sep 29, 2004 at 10:06:02AM +0200, Mats Bengtsson wrote: > I can confirm that the SIGSEGV remains in 2.3.19. > > Just being curious, what did you expect the \once to > mean in this situation? Should it only apply to the first > 16th note? In the score I am transposing I have \time 2/4

Re: \once causes segfault

2004-09-29 Thread Mats Bengtsson
I can confirm that the SIGSEGV remains in 2.3.19. Just being curious, what did you expect the \once to mean in this situation? Should it only apply to the first 16th note? /Mats Christoph Ludwig wrote: Hi, the attached file causes lilypond to dump core: [EMAIL PROTECTED]:~/lilypond/music/test>

\once causes segfault

2004-09-28 Thread Christoph Ludwig
Hi, the attached file causes lilypond to dump core: [EMAIL PROTECTED]:~/lilypond/music/test> uname -r -m -o 2.4.21-243-default i686 GNU/Linux [EMAIL PROTECTED]:~/lilypond/music/test> lilypond -v | head -n 1 GNU LilyPond 2.3.16 [EMAIL PROTECTED]:~/lilypond/music/test> lilypond beat-lengt