Issue 380: cycling markup reference segfaults
http://code.google.com/p/lilypond/issues/detail?id=380
Comment #6 by lemzwerg:
IMHO, it *must* be fixed, this is, lilypond should exit with an error
but without a crash.
--
You received this message because you are listed in the owner
or CC fields
Issue 395: Stems too long in case of feathered kneed beams.
http://code.google.com/p/lilypond/issues/detail?id=395
Comment #1 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you are listed in the owner
Issue 404: request: setting the output filename
http://code.google.com/p/lilypond/issues/detail?id=404
Comment #2 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you are listed in the owner
or CC field
Issue 399: clef can take too much space when changing staffs in piano music
http://code.google.com/p/lilypond/issues/detail?id=399
Comment #6 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you are lis
Your project notifications generated too many emails to send
individually. Here are the subject lines of the emails you would have
received:
Issue 330 in lilypond: missing notes with \cadenzaOn and
Completion_heads_engraver
Issue 357 in lilypond: slurs with \slurDashed don't count towards skylin
Issue 254: ./configure chokes on mftrace-1.1.19 (bug in STEPMAKE_GET_VERSION)
http://code.google.com/p/lilypond/issues/detail?id=254
Comment #7 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you are l
Issue 98: collision bar numbers and StaffGroup
http://code.google.com/p/lilypond/issues/detail?id=98
Comment #5 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you are listed in the owner
or CC fields
Issue 62: trill not always centered
http://code.google.com/p/lilypond/issues/detail?id=62
Comment #3 by gpermus:
By "TextSpanner version no longer works", are you referring to behavior like
issue 401?
Other than that problem, the bug is fixed, and since we have another report for
that
problem,
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=417
Cheers,
- Graham
Panteck wrote:
Lilypond 2.11.29, Windows XP.
When you put a rehearsal mark on a measure that is a full measure rest (or
where the previous measure is a full measure rest), the rest is pushed
off-center.
Issue 417: Rehearsal marks take up extra space when used on full-measure rests
http://code.google.com/p/lilypond/issues/detail?id=417
New issue report by gpermus:
%{
When you put a rehearsal mark on a measure that is a full measure rest (or
where the previous measure is a full measure rest), the r
Issue 405: tupletBracket not printed despite #'bracket-visibility=##t
http://code.google.com/p/lilypond/issues/detail?id=405
Comment #2 by gpermus:
IMO, setting #'bracket-visiblity == ##t means that the user wants _all_
brackets,
even if they look silly or ugly.
I'll downgrade the priority, but
Issue 380: cycling markup reference segfaults
http://code.google.com/p/lilypond/issues/detail?id=380
Comment #5 by gpermus:
Hmm... in that case, we simply let the user crash his system? ;)
If nobody has any brilliant ideas about this bug, shall I mark it closed?
Perhaps
add a sentence somewher
Issue 414: Hairpin through piano staff change cases explosions
http://code.google.com/p/lilypond/issues/detail?id=414
Comment #3 by gpermus:
(No comment was entered for this change.)
Issue attribute updates:
Status: Verified
--
You received this message because you are listed in the ow
Thaks; I've started a new issue for this. (trying to avoid the
confusion with 343)
http://code.google.com/p/lilypond/issues/detail?id=416
Cheers,
- Graham
Mats Bengtsson wrote:
Related to the somewhat confused discussions in Issue 343, I have
updated both
the examples in the manual to actual
Issue 416: removing Forbid_line_break_engraver doesn't always work
http://code.google.com/p/lilypond/issues/detail?id=416
New issue report by gpermus:
% Mats writes:
%{
When I try the following example with version 2.10.25, I do get three
score lines, as desired, but when I try the same example in
Joe Neeman wrote:
I found the problem: sections 8.1.4 and 8.2.3 duplicate information and I only
updated section 8.1.4. The attached patch replaced the duplicated information
in 8.2.3 with a link to 8.1.4 -- can I apply it?
Yes, please. (sorry for the delay)
- Graham
---
Issue 413: PNG image is offset an therefore cropped a little
http://code.google.com/p/lilypond/issues/detail?id=413
Comment #2 by vaclav.kocian:
Well, here is a batch, which I use:
1 #!/bin/sh
2
3 FILE=$( find . -name "*.ly" )
4 NAME=${FILE%.ly}
5 lilypond --png --pdf $FILE || read foo
Apropos, I
> I'm not top posting.
Hi Graham,
%
Here you are the three tries until I've come to a solution
(which is not musically correct, but the Midi output (with \unfoldRepeats)
is apparently correct and sounds identical for the
Dear Mats
Yes you're right. I did indeed try the latest stable and dev versions
2.10.29 and 2.11.29 on both platforms (OSX and debian linux x86). I
am using the emacs lilymode for compilation and opening manually the
pdfs. I tried the verbose also and i don;t think there's a special
19 matches
Mail list logo
