Updates:
Status: Verified
Comment #15 on issue 1506 by colinpkc...@gmail.com: \tempo after
StopStaff/StartStaff forces extension of staff symbol
http://code.google.com/p/lilypond/issues/detail?id=1506
(No comment was entered for this change.)
Updates:
Status: Started
Labels: -Priority-Medium Patch-new
Comment #8 on issue 1216 by k-ohara5...@oco.net: DynamicTextSpanners should
end like hairpins
http://code.google.com/p/lilypond/issues/detail?id=1216
http://codereview.appspot.com/5489044
___
Comment #31 on issue 460 by colingh...@gmail.com: bar numbers for broken
bars
http://code.google.com/p/lilypond/issues/detail?id=460
I've verified that the default behaviour is not to add parenthesized bar
numbers, see image. I had a look at the patch and could not see how to turn
on the
Comment #17 on issue 409 by colingh...@gmail.com: Using whiteout and layer
properties for ties avoiding collision with staff objects
http://code.google.com/p/lilypond/issues/detail?id=409
I've used branch staging to build 2.15.22 and the rhythms section of
Notation. The documentation is fin
Updates:
Labels: Patch-needs_work
Comment #5 on issue 2100 by lilypond...@gmail.com: Patch: CG: explanation
of branches for the impatient
http://code.google.com/p/lilypond/issues/detail?id=2100#c5
Patchy the autobot says: does not apply to master
Comment #4 on issue 2102 by plros...@gmail.com: vertical spacing of a
nonstaff line below the system
http://code.google.com/p/lilypond/issues/detail?id=2102
If this bug is deemed invalid, then the example in "Piano centered
dynamics" should be changed. I followed that example and everythin
Updates:
Labels: Patch-new
Comment #3 on issue 2104 by julien.r...@gmail.com: Patch: Fix .dep file
from lilypond-book when include paths are involved.
http://code.google.com/p/lilypond/issues/detail?id=2104#c3
Fix .dep file from lilypond-book when include paths are involved.
Don't re
Comment #2 on issue 1272 by julien.r...@gmail.com: remove old /web/
http://code.google.com/p/lilypond/issues/detail?id=1272
(Clarifying details from the discussion "Release news, development news,
state of the world" on lilypond-devel)
The old lilypond.org/web/ pages are still up (and probab
Comment #2 on issue 2085 by carl.d.s...@gmail.com: Overriding stencil of
StringNumber leads to "programming error" messages
http://code.google.com/p/lilypond/issues/detail?id=2085
This is probably caused in New_fingering_engraver, in the position_scripts
() function.
To quote from the cod
Comment #9 on issue 1935 by paulwmor...@gmail.com: Doc: internal ledger
lines need to be documented in NR
http://code.google.com/p/lilypond/issues/detail?id=1935
Hi James, I actually just edited an image with an image editor... But I
had some time today so I went ahead and worked up the Li
Updates:
Labels: Patch-new
Comment #4 on issue 2100 by lilypond...@gmail.com: Patch: CG: explanation
of branches for the impatient
http://code.google.com/p/lilypond/issues/detail?id=2100#c4
CG: explanation of branches for the impatient
http://codereview.appspot.com/5484043
Comment #13 on issue 2070 by carl.d.s...@gmail.com: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
I will take a look at the tablature stuff when I get done grading finals
(probably about a week out). I think the prop
Updates:
Labels: Patch-review
Comment #2 on issue 2107 by lilypond...@gmail.com: new patch for
lilypond-book on windows
http://code.google.com/p/lilypond/issues/detail?id=2107#c2
Patchy the autobot says: LGTM.
___
bug-lilypond mailing list
Comment #1 on issue 2107 by julien.r...@gmail.com: new patch for
lilypond-book on windows
http://code.google.com/p/lilypond/issues/detail?id=2107
See Issue 1815 for a test file and in particular Comment 25
http://code.google.com/p/lilypond/issues/detail?id=1815#c25 for the latest
problem.
Comment #5 on issue 2103 by julien.r...@gmail.com: Patch: Output a newline
by default at the end of progress messages.
http://code.google.com/p/lilypond/issues/detail?id=2103
It seems to depend on the particular order in which you would test patches.
Maybe you have .dep files left over from
Updates:
Status: Fixed
Labels: -Patch-needs_work fixed_2_15_15
Comment #34 on issue 1815 by gra...@percival-music.ca: lilypond-book fails
on Windows
http://code.google.com/p/lilypond/issues/detail?id=1815
going back to previous fixed state.
__
Status: Accepted
Owner: julien.r...@gmail.com
Labels: Type-Defect Patch-new
New issue 2107 by gra...@percival-music.ca: new patch for lilypond-book on
windows
http://code.google.com/p/lilypond/issues/detail?id=2107
lilylib.py : Wrap arguments with double quotes and clarify a comment.
I misu
Comment #33 on issue 1815 by gra...@percival-music.ca: lilypond-book fails
on Windows
http://code.google.com/p/lilypond/issues/detail?id=1815
never mind, patchy found the wrong url.
... the google code python API only gives the first 25 comments or
something. Anybody know how to get more?
Updates:
Labels: Patch-needs_work
Comment #32 on issue 1815 by lilypond...@gmail.com: lilypond-book fails on
Windows
http://code.google.com/p/lilypond/issues/detail?id=1815#c32
Patchy the autobot says: does not apply to master
___
bug-lily
Comment #4 on issue 2103 by gra...@percival-music.ca: Patch: Output a
newline by default at the end of progress messages.
http://code.google.com/p/lilypond/issues/detail?id=2103
hmm... maybe not.
https://github.com/gperciva/lilypond-extra/blob/master/patches/compile_lilypond_test.py#L259
it
Bug squad,
Please remember that verifying issues is part of your 20 minutes a
day. Once you have finished handling any new emails, you should
spend your remaining time looking at these. It is a *huge* pain
when developers believe that bugs are fixed, when in fact they are
not.
If you are not ce
Comment #31 on issue 1815 by julien.r...@gmail.com: lilypond-book fails on
Windows
http://code.google.com/p/lilypond/issues/detail?id=1815
It wasn't verified, I don't think. I cannot test on Windows, unfortunately,
so we keep fixing issues as they are being reported. Comment 25 points to
Updates:
Status: Accepted
Labels: -fixed_2_15_15
Comment #30 on issue 1815 by gra...@percival-music.ca: lilypond-book fails
on Windows
http://code.google.com/p/lilypond/issues/detail?id=1815
err, how was this fixed if you misunderstood the question? Or rather, how
was it ve
Comment #2 on issue 2104 by julien.r...@gmail.com: Patch: Fix .dep file
from lilypond-book when include paths are involved.
http://code.google.com/p/lilypond/issues/detail?id=2104
This is with make check? I think I know what the problem is. I did make doc
but not make check.
Comment #3 on issue 2103 by julien.r...@gmail.com: Patch: Output a newline
by default at the end of progress messages.
http://code.google.com/p/lilypond/issues/detail?id=2103
Was it from a clean build dir?
___
bug-lilypond mailing list
bug-lilypon
Comment #2 on issue 2103 by gra...@percival-music.ca: Patch: Output a
newline by default at the end of progress messages.
http://code.google.com/p/lilypond/issues/detail?id=2103
huh, I tested it twice, and it failed both times. But I really don't see
how this patch can lead to this!
If y
Updates:
Labels: Patch-needs_work
Comment #1 on issue 2103 by lilypond...@gmail.com: Patch: Output a newline
by default at the end of progress messages.
http://code.google.com/p/lilypond/issues/detail?id=2103#c1
Patchy the autobot says: regtest check fail: lilypond-book.py: error: fil
Updates:
Labels: Patch-needs_work
Comment #1 on issue 2104 by lilypond...@gmail.com: Patch: Fix .dep file
from lilypond-book when include paths are involved.
http://code.google.com/p/lilypond/issues/detail?id=2104#c1
Patchy the autobot says: regtest check fail: Dissecting...lilypond-b
Updates:
Summary: Patch: Remove warning and .aux file left over by lilypond-book.
Comment #3 on issue 2105 by julien.r...@gmail.com: Patch: Remove warning
and .aux file left over by lilypond-book.
http://code.google.com/p/lilypond/issues/detail?id=2105
(No comment was entered for this
Updates:
Labels: Patch-review
Comment #2 on issue 2106 by lilypond...@gmail.com: Patch: Build fixes for
translated manuals: dependencies and a typo
http://code.google.com/p/lilypond/issues/detail?id=2106#c2
Patchy the autobot says: LGTM.
_
Updates:
Labels: Patch-review
Comment #2 on issue 2105 by lilypond...@gmail.com: Patch: Don't blindly
issue the warning
http://code.google.com/p/lilypond/issues/detail?id=2105#c2
Patchy the autobot says: LGTM.
___
bug-lilypond mailing list
Updates:
Labels: Patch-needs_work
Comment #3 on issue 2100 by lilypond...@gmail.com: Patch: CG: explanation
of branches for the impatient
http://code.google.com/p/lilypond/issues/detail?id=2100#c3
Patchy the autobot says: fails make
___
bu
Comment #1 on issue 2105 by julien.r...@gmail.com: Patch: Don't blindly
issue the warning
http://code.google.com/p/lilypond/issues/detail?id=2105
...when running lilypond-book on a .lytex file.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
ht
Comment #1 on issue 2106 by julien.r...@gmail.com: Patch: Build fixes for
translated manuals: dependencies and a typo
http://code.google.com/p/lilypond/issues/detail?id=2106
The idea is that translated manuals should also benefit from the work done
towards Issue 1852.
___
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2106 by julien.r...@gmail.com: Patch: Build fixes for translated
manuals: dependencies and a typo
http://code.google.com/p/lilypond/issues/detail?id=2106
Build fixes for translated manuals: dependencies and a typo
Adding th
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2105 by julien.r...@gmail.com: Patch: Don't blindly issue the
warning
http://code.google.com/p/lilypond/issues/detail?id=2105
Don't blindly issue the warning
"lilypond-book: warning: Unable to auto-detect default page
sett
Updates:
Labels: Patch-new
Comment #29 on issue 1815 by julien.r...@gmail.com: lilypond-book fails on
Windows
http://code.google.com/p/lilypond/issues/detail?id=1815#c29
lilylib.py : Wrap arguments with double quotes and clarify a comment.
I misunderstood what this function does befo
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2104 by julien.r...@gmail.com: Patch: Fix .dep file from
lilypond-book when include paths are involved.
http://code.google.com/p/lilypond/issues/detail?id=2104
Fix .dep file from lilypond-book when include paths are involved
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2103 by julien.r...@gmail.com: Patch: Output a newline by default
at the end of progress messages.
http://code.google.com/p/lilypond/issues/detail?id=2103
Output a newline by default at the end of progress messages.
For lil
Updates:
Status: Fixed
Labels: -Patch-push fixed_2_15_22
Comment #4 on issue 2087 by gra...@percival-music.ca: Patch: Fixes various
warnings from clang++
http://code.google.com/p/lilypond/issues/detail?id=2087
pushed 814dd7be6256476f43f3923033c2da95e460ce2f
_
Comment #2 on issue 1005 by fedel...@gmail.com: syntax highlighting in the
docs
http://code.google.com/p/lilypond/issues/detail?id=1005
It seems that Valentin has dropped this issue, right?
I'd like to do #1.
I've already started the basics (comments, strings, operators).
I'll post a draft o
Comment #12 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
That's ok. I will likely edge a few changes into master at the meantime
that make the transition smoother: while the default of
42 matches
Mail list logo
