Updates:
Labels: backport
Comment #22 on issue 1555 by k-ohara5...@oco.net: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
Although this issue became non-critical, the repeated warnings were so
annoying and the patch is so safe
Updates:
Status: Fixed
Labels: -Patch-review fixed_2_15_0
Comment #21 on issue 1555 by k-ohara5...@oco.net: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
Patch pushed in commit 6ca4748f reduces the warnings to just one.
Updates:
Status: Fixed
Labels: fixed_2_15_0
Comment #3 on issue 1547 by k-ohara5...@oco.net: Too many colliding rests
http://code.google.com/p/lilypond/issues/detail?id=1547
With the patch pushed in 1edd0, the original example generates no warning,
but my counterexample (above af
Updates:
Status: Fixed
Labels: -Patch-review fixed_2_15_0
Comment #7 on issue 1618 by k-ohara5...@oco.net: unpredictable placement of
rests
http://code.google.com/p/lilypond/issues/detail?id=1618
patch pushed in 1edd0
___
bug-lilyp
Comment #11 on issue 1633 by carl.d.s...@gmail.com: pdf utf-16be breaks doc
compile
http://code.google.com/p/lilypond/issues/detail?id=1633
Backported the third commit as well.
03ec2b777e64d65be50f03d18f64ba642a9c1c9c
___
bug-lilypond mailing li
Updates:
Status: Verified
Comment #10 on issue 1633 by colinpkc...@gmail.com: pdf utf-16be breaks doc
compile
http://code.google.com/p/lilypond/issues/detail?id=1633
Verified 2.13.62
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https
Comment #2 on issue 1615 by colinpkc...@gmail.com: lily-git.tcl not
working: savannah no longer likes git fetch --depth
http://code.google.com/p/lilypond/issues/detail?id=1615
The given instructions seem to match the contents of lily-git.tcl, and I've
just deleted my existing ~/lilypond-git
Updates:
Labels: -backport fixed_2_13_62
Comment #9 on issue 1633 by carl.d.s...@gmail.com: pdf utf-16be breaks doc
compile
http://code.google.com/p/lilypond/issues/detail?id=1633
Backported.
Two commits:
d6fcf3af68676af106c285919b15050c44ed36c8
aa730216358403d7a94ff54195de9f4dfd27f4
Updates:
Labels: -Patch-new Patch-review
Comment #20 on issue 1555 by colinpkc...@gmail.com: Multiple warnings
concerning staff-affinities
http://code.google.com/p/lilypond/issues/detail?id=1555
Clean compile and regtests with 2.13.61
___
wrote in message
news:4-9567054385019064696-5306556395545786802-lilypond=googlecode@googlecode.com...
Comment #4 on issue 1626 by percival.music.ca: Articulate produces faulty
barcheck warnings
http://code.google.com/p/lilypond/issues/detail?id=1626
does anybody have an email address for
Comment #4 on issue 1626 by percival.music.ca: Articulate produces faulty
barcheck warnings
http://code.google.com/p/lilypond/issues/detail?id=1626
does anybody have an email address for Helge Hafting? I'd like to make
sure that he (or she? who knows with German names) gets credit for the
Comment #1 on issue 1615 by percival.music.ca: lily-git.tcl not working:
savannah no longer likes git fetch --depth
http://code.google.com/p/lilypond/issues/detail?id=1615
complete list of instructions:
mkdir new-lilypond-dir
cd new-lilypond-dir
git init
git config core.bare false
git remote
Comment #12 on issue 1630 by karin.ho...@googlemail.com: Completion heads
engraver produces duplicate ties
http://code.google.com/p/lilypond/issues/detail?id=1630
He has not replied yet, but then it't Sunday and the weather is nice (at
least here) :-) ...
It was no problem to get the source
Comment #11 on issue 1630 by percival.music.ca: Completion heads engraver
produces duplicate ties
http://code.google.com/p/lilypond/issues/detail?id=1630
Have you heard from Janek yet? Our development process is somewhat "iffy"
and the documentation is sometimes out of date (for example, a
Updates:
Labels: backport
Comment #8 on issue 1633 by percival.music.ca: pdf utf-16be breaks doc
compile
http://code.google.com/p/lilypond/issues/detail?id=1633
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-li
Comment #10 on issue 1630 by karin.ho...@googlemail.com: Completion heads
engraver produces duplicate ties
http://code.google.com/p/lilypond/issues/detail?id=1630
Thanks for the link! The instructions give exactly the overview I was
looking for ...
If bugfixes are discussed on the review
Comment #9 on issue 1630 by karin.ho...@googlemail.com: Completion heads
engraver produces duplicate ties
http://code.google.com/p/lilypond/issues/detail?id=1630
Thanks for the link! The instructions give exactly the overview I was
looking for ...
If bugfixes are discussed on the review s
Neil Puttock wrote:
>On 29 April 2011 12:49, Helge Hafting wrote:
>
>> The Tie_engraver is already capable of not tieing all notes in a chord, so I
>> hope this is fixable.
>
>The Tie_engraver isn't designed to work at the Staff level, so there's
>no guarantee you'll get workable results. There i
"Federico Bruni" wrote in message
news:1304243606.2496.18.ca...@fede-laptop.fede...
Is this a bug? (the comments in the example explain everything)
Thanks
\version "2.13.61"
music = \relative c' {
% connect wrong strings in TabStaff
dis\2\glissando
\glissando dis\2
% glissando direction
Is this a bug? (the comments in the example explain everything)
Thanks
\version "2.13.61"
music = \relative c' {
% connect wrong strings in TabStaff
dis\2\glissando
\glissando dis\2
% glissando direction in TabStaff
e8\2\glissando dis % correct
\glissando % correct
4\glissando
20 matches
Mail list logo
