Updates:
Labels: Patch
Comment #4 on issue 1096 by v.villenave: ly:parser-parse-string segfaults
when directly called at toplevel
http://code.google.com/p/lilypond/issues/detail?id=1096
The patch works, but I'm getting a weird difference in some horizontal
spacing (see
attached)...
Status: Accepted
Owner:
Labels: Priority-Critical Type-Defect Regression
New issue 1103 by brownian.box: Typo in engraver name while defining new
contexts causes lilypond to segfault
http://code.google.com/p/lilypond/issues/detail?id=1103
% -
\version
Alexander Deubelbeiss deubelba at gmx.net writes:
Typo: In the penultimate paragraph of _1.3 Automated engraving - Getting
things right_, please replace
acceptible with acceptable (twice)
Typo: In _1.4 Building software - Music representation_,
replace heirarchical with hierarchical
(just
Comment #8 on issue 1013 by Carl.D.Sorensen: lilypond-book regression test
http://code.google.com/p/lilypond/issues/detail?id=1013
It seems to me that in order to move this forward, we need an owner for the
patch. I don't feel qualified to own
this one; it seems (given the history) that it
Updates:
Status: Invalid
Comment #1 on issue 1101 by Carl.D.Sorensen: PATCH: accessors for
note-column's dot-column, accidentals
http://code.google.com/p/lilypond/issues/detail?id=1101
This was applied on 2010-04-05. Commit
4490687a923832d9c79475d165e3445d5437e334
Comment #9 on issue 1060 by will.fitzgerald: Add Funk-style shape note heads
http://code.google.com/p/lilypond/issues/detail?id=1060
Carl,
The point of asking James's opinion is that he has, more than anyone else
in the world, typeset music in
Funk shapes. So, he understands the design
Comment #5 on issue 1096 by Carl.D.Sorensen: ly:parser-parse-string
segfaults when directly called at toplevel
http://code.google.com/p/lilypond/issues/detail?id=1096
test-output-distance is intended to get a different output distance every
time, so you can be sure the regtests
have been
Comment #10 on issue 1060 by Carl.D.Sorensen: Add Funk-style shape note
heads
http://code.google.com/p/lilypond/issues/detail?id=1060
Thanks for elucidating. Now I see the 26th edition, which is more
consistent.
___
bug-lilypond mailing list
Updates:
Owner: reinhold.kainhofer
Comment #9 on issue 1013 by reinhold.kainhofer: lilypond-book regression
test
http://code.google.com/p/lilypond/issues/detail?id=1013
I've been working on making lilypond-book more modular in the last few
weeks.
Actually, I had plannd myself to
Updates:
Status: Verified
Comment #2 on issue 1101 by percival.music.ca: PATCH: accessors for
note-column's dot-column, accidentals
http://code.google.com/p/lilypond/issues/detail?id=1101
(No comment was entered for this change.)
___
Comment #10 on issue 1013 by percival.music.ca: lilypond-book regression
test
http://code.google.com/p/lilypond/issues/detail?id=1013
I was hoping that chhitz would keep on working on the patch, but evidently
that's not
happening. I'm very happy to have Reinhold take it over.
If/when I
Updates:
Status: Started
Comment #6 on issue 1096 by v.villenave: ly:parser-parse-string segfaults
when directly called at toplevel
http://code.google.com/p/lilypond/issues/detail?id=1096
Oh, I guess I'm just plain wrong then :-)
OK, as far as testing goes, there's nothing wrong
Updates:
Status: Fixed
Labels: Fixed_2_13_22
Comment #10 on issue 881 by Carl.D.Sorensen: Arpeggios may collide with
laissezVibrer ties
http://code.google.com/p/lilypond/issues/detail?id=881
(No comment was entered for this change.)
Comment #4 on issue 1089 by Carl.D.Sorensen: DynamicTextSpanner not printed
http://code.google.com/p/lilypond/issues/detail?id=1089
There was a decision to add a bit of space to separate the cresc. from the
p. In so doing, the available space
became too short to fit both. If there were a
Status: Accepted
Owner:
Labels: Type-Enhancement Priority-Low
New issue 1104 by brownian.box: Enhancement: underline markup function
needed (and proposed)
http://code.google.com/p/lilypond/issues/detail?id=1104
http://lists.gnu.org/archive/html/lilypond-devel/2010-05/msg00491.html :
%
Updates:
Labels: -Priority-Critical -Regression Priority-Medium Warning
Comment #5 on issue 1089 by percival.music.ca: DynamicTextSpanner not
printed
http://code.google.com/p/lilypond/issues/detail?id=1089
Good rationale; adjusting priority accordingly.
Updates:
Labels: Patch
Comment #1 on issue 1104 by percival.music.ca: Enhancement: underline
markup function needed (and proposed)
http://code.google.com/p/lilypond/issues/detail?id=1104
Thanks for the thought, Dmytro, but in the future, I would leave patches up
to Marek.
In
Comment #1 on issue 1103 by musiccomposition: Typo in engraver name while
defining new contexts causes lilypond to segfault
http://code.google.com/p/lilypond/issues/detail?id=1103
Attaching patch.
Attachments:
0001-don-t-segfault-on-invalid-engraver-names.patch 2.5 KB
Updates:
Status: Started
Owner: pnorcks
Comment #11 on issue 1031 by pnorcks: constantly-changing
input/regression/rest-collision-beam-note.ly
http://code.google.com/p/lilypond/issues/detail?id=1031
Update:
I have discovered the culprit function call. See below. The result
Comment #12 on issue 1031 by pnorcks: constantly-changing
input/regression/rest-collision-beam-note.ly
http://code.google.com/p/lilypond/issues/detail?id=1031
I also wanted to mention that I *do* have a reproducible test case,
discovered
through a guess-and-check approach, but it might not
20 matches
Mail list logo