Updates:
Status: Started
Owner: carl.d.s...@gmail.com
Comment #5 on issue 2215 by carl.d.s...@gmail.com: lost commits jan 7
http://code.google.com/p/lilypond/issues/detail?id=2215
(No comment was entered for this change.)
___
bug-lily
Comment #4 on issue 2215 by carl.d.s...@gmail.com: lost commits jan 7
http://code.google.com/p/lilypond/issues/detail?id=2215
OK. I've used git-gui to look at all branches in gitk.
There are 5 commits in staging-broken-jan7 after it diverges from master:
9b10eba64e43dcb9488366db7ae7723a6df123d
Comment #4 on issue 1412 by plros...@gmail.com: programming error: Going
back in MIDI time
http://code.google.com/p/lilypond/issues/detail?id=1412
Let's take a file with acciaccatura between two ordinary notes. Run
lilypond on it, then midi2ly on the MIDI file. The result shows that the
Updates:
Status: Verified
Comment #11 on issue 2084 by ma...@gregoriana.sk: script-accidental
avoidance fails for articulations
http://code.google.com/p/lilypond/issues/detail?id=2084
(No comment was entered for this change.)
___
bug-lilyp
Comment #9 on issue 2122 by ma...@gregoriana.sk: Regression in
chord-name-exceptions.ly - badly spaced chord names
http://code.google.com/p/lilypond/issues/detail?id=2122
Running chord-name-exceptions.ly with 2.15.24 gives the same layout as on
the picture right.
Updates:
Status: Verified
Comment #7 on issue 1947 by ma...@gregoriana.sk: Stem Tremoli for
double-stemmed notes are too short on the right side.
http://code.google.com/p/lilypond/issues/detail?id=1947
(No comment was entered for this change.)
___
Updates:
Status: Verified
Comment #20 on issue 2059 by ma...@gregoriana.sk: Bar numbering of
alternatives
http://code.google.com/p/lilypond/issues/detail?id=2059
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-l
Updates:
Status: Verified
Comment #7 on issue 2123 by ma...@gregoriana.sk: Patch: Gets cross-staff
collisions right for beams.
http://code.google.com/p/lilypond/issues/detail?id=2123
(No comment was entered for this change.)
___
bug-lilypo
Updates:
Status: Verified
Comment #8 on issue 2153 by ma...@gregoriana.sk: piano pedal bracket should
stop at requested moment
http://code.google.com/p/lilypond/issues/detail?id=2153
(No comment was entered for this change.)
___
bug-lilypo
Comment #3 on issue 1412 by plros...@gmail.com: programming error: Going
back in MIDI time
http://code.google.com/p/lilypond/issues/detail?id=1412
The same happens with \appoggiatura. It looks like Lilypond tries to
borrow time from the previous note, but there is none. It may be OK for
Comment #19 on issue 695 by janek.li...@gmail.com: slurs may take too much
vertical extent
http://code.google.com/p/lilypond/issues/detail?id=695
I think this will impact the way users use Lily, perhaps quite strongly
(thanks, Mike!).
However i don't insist on mentioning this in changes.
2012/1/13 Francisco Vila :
> 2012/1/13 Julien Rioux :
>> I'm not sure why, but it looks like convert-ly.py and lilylib.py are
>> out-of-sync. Could it be that python imports lilylib from a different
>> version of lilypond? Could you please find the line
>>
>> identify ()
>>
>> in convert-ly.py (
2012/1/13 Julien Rioux :
> I'm not sure why, but it looks like convert-ly.py and lilylib.py are
> out-of-sync. Could it be that python imports lilylib from a different
> version of lilypond? Could you please find the line
>
> identify ()
>
> in convert-ly.py (line 346 here) and add below
>
>
On 13/01/2012 10:44 AM, Francisco Vila wrote:
Hello,
When trying to use convert-ly I obtain
$ convert-ly test.ly
convert-ly (GNU LilyPond) 2.15.25
convert-ly: Procesando «test.ly»...
Traceback (most recent call last):
File "/usr/local/bin/convert-ly", line 369, in
main ()
File "/usr/
Hello,
When trying to use convert-ly I obtain
$ convert-ly test.ly
convert-ly (GNU LilyPond) 2.15.25
convert-ly: Procesando «test.ly»...
Traceback (most recent call last):
File "/usr/local/bin/convert-ly", line 369, in
main ()
File "/usr/local/bin/convert-ly", line 357, in main
do_on
wrote in message
news:11-9567054385019064696-16001340212203614722-lilypond=googlecode@googlecode.com...
Updates:
Labels: -Patch-review Patch-needs_work
Comment #11 on issue 2125 by julien.r...@gmail.com: Patch: Build: Don't
rebuild everything each time unless necessary.
http://code.google
Updates:
Labels: -Patch-needs_work Patch-new
Comment #9 on issue 2177 by gra...@percival-music.ca: Patch: Reverts public
interface for simple spacer.
http://code.google.com/p/lilypond/issues/detail?id=2177
err, ok. I guess this patch was waiting for 6 days just for somebody to
chan
Comment #10 on issue 2158 by julien.r...@gmail.com: Patch: Sketch of not
remaking html files
http://code.google.com/p/lilypond/issues/detail?id=2158
I'm not found of a try: block that discards the exception (I think that's
what it currently does).
Updates:
Labels: -Patch-review
Comment #4 on issue 2220 by julien.r...@gmail.com: Undefined references to
node in translated manuals
http://code.google.com/p/lilypond/issues/detail?id=2220
Pushed to lilypond/translation to merge with Francisco's other xref fixes.
Head is now 4a66b6980
Updates:
Status: Fixed
Labels: -Patch-review Fixed_2_15_25
Comment #4 on issue 2221 by julien.r...@gmail.com: Duplicate node errors in
snippets
http://code.google.com/p/lilypond/issues/detail?id=2221
Pushed as e25565e23b6e7a219c594d359495817d7076eff5
Comment #9 on issue 2198 by pkx1...@gmail.com: Document use of PATH
statement in Windows
http://code.google.com/p/lilypond/issues/detail?id=2198
No but you (or anyone else) can add a new tracker issue if you like so this
can be done the 'next time'. This specific request/issue is fixed.
P
Comment #8 on issue 2177 by m...@apollinemike.com: Patch: Reverts public
interface for simple spacer.
http://code.google.com/p/lilypond/issues/detail?id=2177
Could you please check this patch again w/ the new patchy to see if it gets
over the column-description.hh hurdle?
___
Comment #8 on issue 2198 by mats.ben...@ee.kth.se: Document use of PATH
statement in Windows
http://code.google.com/p/lilypond/issues/detail?id=2198
How about the other command-line utilities like convert-ly? Have you added
similar comments in the documentation of these?
/Mats
___
Comment #17 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092
I'm sorry. I forgot to rebase to staging. Should be good to go now.
Carl
___
bug-lilypond
Updates:
Labels: Patch-new
Comment #16 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c16
Update lilygit.tcl (Issue 2092)
Makes lilygit.tcl respect the environment variable $LILYPOND_GIT.
If
Updates:
Status: Fixed
Labels: -Patch-push
Comment #8 on issue 2191 by pkx1...@gmail.com: Web: update to version 2.15,
use it in the "site:" part
http://code.google.com/p/lilypond/issues/detail?id=2191
committer James Lowe
Fri, 13 Jan 2012 11:54:08 + (11:54 +000
Updates:
Status: Fixed
Labels: -Patch-push
Comment #7 on issue 2198 by pkx1...@gmail.com: Document use of PATH
statement in Windows
http://code.google.com/p/lilypond/issues/detail?id=2198
Fri, 13 Jan 2012 11:48:16 + (11:48 +)
commit 1465bed7792a2e2c83dc6643b8
Updates:
Status: Fixed
Labels: -Patch-review
Comment #2 on issue 2218 by pkx1...@gmail.com: Web: Added Concert to
Introduction.itexi
http://code.google.com/p/lilypond/issues/detail?id=2218
Fri, 13 Jan 2012 11:42:01 + (11:42 +)
commit b6731e900a2037112364ad328
Updates:
Labels: Patch-needs_work
Comment #15 on issue 2092 by lilypond...@gmail.com: lily-git.tcl should
using a "working" branch
http://code.google.com/p/lilypond/issues/detail?id=2092#c15
Patchy the autobot says: sorry, I'm getting "patch does not apply". Tested
it twice.
Ralph Palmer-3 wrote:
>
> On Mon, Jan 9, 2012 at 10:54 AM, -Eluze wrote:
>
>>
>> hi
>>
>> everybody knows how cumbersome it is to write parameters in a shell - it
>> would be nice to have them in a lilypond file.
>>
>> LilyPond provides an alternative for many of the command line options but
>
Updates:
Labels: Patch-review
Comment #2 on issue 2200 by lilypond...@gmail.com: Dots shouldn't always be
placed in one column
http://code.google.com/p/lilypond/issues/detail?id=2200#c2
Patchy the autobot says: LGTM.
___
bug-lilypond maili
Updates:
Labels: Patch-review
Comment #3 on issue 2220 by lilypond...@gmail.com: Undefined references to
node in translated manuals
http://code.google.com/p/lilypond/issues/detail?id=2220#c3
Patchy the autobot says: LGTM.
___
bug-lilypond
Updates:
Labels: Patch-review
Comment #9 on issue 2180 by lilypond...@gmail.com: beams are detached from
stems
http://code.google.com/p/lilypond/issues/detail?id=2180#c9
Patchy the autobot says: LGTM.
___
bug-lilypond mailing list
bug-lily
Updates:
Labels: Patch-review
Comment #1 on issue 2218 by lilypond...@gmail.com: Web: Added Concert to
Introduction.itexi
http://code.google.com/p/lilypond/issues/detail?id=2218#c1
Patchy the autobot says: LGTM.
___
bug-lilypond mailing li
Updates:
Labels: Patch-review
Comment #3 on issue 2221 by lilypond...@gmail.com: Duplicate node errors in
snippets
http://code.google.com/p/lilypond/issues/detail?id=2221#c3
Patchy the autobot says: LGTM.
___
bug-lilypond mailing list
bug-
Updates:
Labels: Patch-review
Comment #19 on issue 1846 by lilypond...@gmail.com: Improves horizontal
spacing of axis groups that SpanBar grobs traverse
http://code.google.com/p/lilypond/issues/detail?id=1846#c19
Patchy the autobot says: LGTM.
___
Comment #3 on issue 2215 by gra...@percival-music.ca: lost commits jan 7
http://code.google.com/p/lilypond/issues/detail?id=2215
no wait, I can't find those commits in webgit either. Hmm.
*shrug* ok, the commits are even more lost than I thought. Somebody needs
to figure out if anything's
Comment #2 on issue 2215 by gra...@percival-music.ca: lost commits jan 7
http://code.google.com/p/lilypond/issues/detail?id=2215
try it without a dash in "jan7"
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo
38 matches
Mail list logo
