questionable unfold-repeats for tremolo

The unfold-all-repeats.ly example in Tips and Tricks demonstrates the unfolding of a tremolo, specifically \repeat tremolo 8 {c'32 e' }. This should expand to 8 sets of 32nd-note pairs, I would think. However, in the output, it shows 8 sets of 16th-note pairs. I think this is a bug, but am prepare

\partcombine terribly broken

hi, I have a copyrighted score that demonstrates a few problems with \partcombine in v2.1.35. 1. Weird autobeaming sometimes during Solo II. 2. The text "Solo II" is repeated each bar even though voice one is silent (using \skip) 3. Voice two disappears after 14 bars of 22. 4. Look at http://lil

\partcombine terribly broken

[EMAIL PROTECTED] writes: > 4. Look at > http://lilypond.org/doc/v2.1/Documentation/user/out-www/lilypond/Automatic-part-combining.html#Automatic% > 20part%20combining > In the first example, the stems of the two voices are merged. According to the > documentation they shouldn't be. Why? -- Ha

Re: \partcombine terribly broken

On Tuesday 30 March 2004 13.23, Han-Wen Nienhuys wrote: > [EMAIL PROTECTED] writes: > > 4. Look at > > http://lilypond.org/doc/v2.1/Documentation/user/out-www/lilypond/Automati > >c-part-combining.html#Automatic% 20part%20combining > > In the first example, the stems of the two voices are merged. A

SIGSEGV, Was: questionable unfold-repeats for tremolo

You are absolutely right, this is a bug! I found (at least) one other bug related to tremolo repeats: When looking at the code in parser.yy, taking care of tremolo repeats, I got curious on what happened when the argument was not a Sequential_music. I soon found out that \repeat tremolo 12 c16 is

Re: 2.1.34: Instrument name in header messes w/justification

I have fixed this bug in the CVS version. /Mats Doug Asherman wrote: Possible bug: if you specify the instrument name in the \header block, it can throw off the justification of the music. Setting raggedright to ##f doesn't fix this; and the problem is stranger than that. - Doug \version "2

convert-ly 2.1.34

Seems to have a regular expression error, but I am not acquainted enough with python's regexps to debug: Using the following file: \version "2.1.0" [EMAIL PROTECTED]:~/lily$ convert-ly foo.ly convert-ly (GNU LilyPond) 2.1.34 Processing `foo.ly' ... Applying conversions: 2.1.1, 2.1.2, 2.1.3, 2.1.4

Results of your commands

> Are you a spammer? (I found your email on a spammer website!?!) Command not understood: ignoring end of message. No command found in message ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

Re: 2.1.35 build error

Fodor Bertalan writes: > I'm trying to build 2.1.35 from the source package. > Compile log attached. Attachments are stripped here, could you send the log to lilypond-devel? What was the last version that built correctly? Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The musi

RE: 2.1.35 build error

32: ok 33: broken 34: not tried 35: broken 36: broken Bert > What was the last version that built correctly? > > Jan. ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

Re: 2.1.35 build error

Bertalan Fodor writes: > 32: ok > > 33: broken Thanks. It's fixed in CVS. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Bug-lilypond mailing l

cationic

dane acorn antares churchmen aureomycin balboa bright besetting couple borealis baronet bromide compartment alpenstock alhambra cherub cruickshank abbott dehumidify deck celluloid colette candlewick ___ Bug-lilypond mailing list [EMAIL PROTECTED] http: