Updates:
Status: Accepted
Labels: -fixed_2_15_13
Comment #3 on issue 582 by k-ohara5...@oco.net: slur and tie start in
(almost) same spot
http://code.google.com/p/lilypond/issues/detail?id=582
Oops, not fixed.
We now have to say ragged-right = ##f to see the problem.
___
Updates:
Labels: fixed_2_15_13
Comment #4 on issue 304 by k-ohara5...@oco.net: Slurs and phrasing slurs
should not collide at endpoints
http://code.google.com/p/lilypond/issues/detail?id=304
(No comment was entered for this change.)
___
bu
Updates:
Status: Fixed
Labels: fixed_2_15_13
Comment #2 on issue 582 by k-ohara5...@oco.net: slur and tie start in
(almost) same spot
http://code.google.com/p/lilypond/issues/detail?id=582
Fixed sometime before 2.15.13 (maybe by Mike, or maybe Reinhold?)
Updates:
Labels: -Type-Defect -Priority-Low Type-Ugly Needs-design
Comment #1 on issue 1133 by k-ohara5...@oco.net: Linebreaking calculation
problem
http://code.google.com/p/lilypond/issues/detail?id=1133
It seems the request is to have LilyPond dislike the whitespace under the
mark
Updates:
Summary: KeyCancellation and KeySignatures in un-necessarily separated
columns
Comment #5 on issue 448 by k-ohara5...@oco.net: KeyCancellation and
KeySignatures in un-necessarily separated columns
http://code.google.com/p/lilypond/issues/detail?id=448
For examples I went to Mahle
Updates:
Labels: -Patch-review Patch-needs_work
Comment #32 on issue 1852 by colinpkc...@gmail.com: manuals needs more
explicit dependencies
http://code.google.com/p/lilypond/issues/detail?id=1852
Discussion on Rietveld suggests this isn't quite final, yet.
_
Updates:
Summary: Accidental collides with cross-staff beam
Labels: -Priority-Medium
Comment #3 on issue 1324 by k-ohara5...@oco.net: Accidental collides with
cross-staff beam
http://code.google.com/p/lilypond/issues/detail?id=1324
All that remains un-fixed is the collision be
Updates:
Labels: -Patch-countdown Patch-push
Comment #10 on issue 509 by colinpkc...@gmail.com: collision nested tuplet
numbers
http://code.google.com/p/lilypond/issues/detail?id=509
Counted down to 20110930
___
bug-lilypond mailing list
Updates:
Summary: Slur collides with stems
Labels: Needs-design
Comment #3 on issue 1718 by k-ohara5...@oco.net: Slur collides with stems
http://code.google.com/p/lilypond/issues/detail?id=1718
The choice in these situations is to have a very tall slur, raise the slur
very high
Updates:
Status: Fixed
Labels: fixed_2_15_13
Comment #2 on issue 1326 by k-ohara5...@oco.net: Slur collides with note
stem
http://code.google.com/p/lilypond/issues/detail?id=1326
The collision with the flag is avoided as of about version 2.15.10.
(If anyone else, like me, fin
On Fri, Sep 30, 2011 at 10:47 AM, m...@apollinemike.com
wrote:
> On Sep 30, 2011, at 7:43 PM, Peekay Ex wrote:
>> http://code.google.com/p/lilypond/issues/detail?id=1949
Thanks
> #(set! paper-alist (cons '("6x9" cons (* 6 in) (* 9 in)) paper-alist))
> #(set-default-paper-size "6x9")
>
> Is a wor
Comment #1 on issue 1949 by horndud...@gmail.com: add to paper.scm 6 x 9 in
http://code.google.com/p/lilypond/issues/detail?id=1949
Workaround from Mike Solomon:
#(set! paper-alist (cons '("6x9" cons (* 6 in) (* 9 in)) paper-alist))
#(set-default-paper-size "6x9")
On Sep 30, 2011, at 7:43 PM, Peekay Ex wrote:
> hello
>
> On Fri, Sep 30, 2011 at 6:39 PM, Jay Anderson wrote:
>> 6 x 9 in. isn't currently available. I haven't found a standard name
>> for this size. Lulu calls it 'US Trade',
>> http://en.wikipedia.org/wiki/Book_size calls it 'octavo'. In any c
Status: New
Owner:
Labels: Type-Enhancement
New issue 1949 by pkx1...@gmail.com: add to paper.scm 6 x 9 in
http://code.google.com/p/lilypond/issues/detail?id=1949
Jay Anderson horndud...@gmail.com via gnu.org to bug-lilypond
show details 6:39 PM (2 minutes ago)
6 x 9 in. isn't currently ava
hello
On Fri, Sep 30, 2011 at 6:39 PM, Jay Anderson wrote:
> 6 x 9 in. isn't currently available. I haven't found a standard name
> for this size. Lulu calls it 'US Trade',
> http://en.wikipedia.org/wiki/Book_size calls it 'octavo'. In any case
> it seems to be a fairly common size that would be
6 x 9 in. isn't currently available. I haven't found a standard name
for this size. Lulu calls it 'US Trade',
http://en.wikipedia.org/wiki/Book_size calls it 'octavo'. In any case
it seems to be a fairly common size that would be useful to add (and
custom sizes are clunky to add and maintain - is t
Updates:
Status: Duplicate
Mergedinto: 1743
Comment #1 on issue 1948 by pkx1...@gmail.com: Windows install clobbered
system PATH
http://code.google.com/p/lilypond/issues/detail?id=1948
This is supposedly fixed in 2.15.10
see issue 1743
Can you verify this on your system and
lilypond-2.14.2-1.mingw.exe
Windows 7 SP1
After running installer, system PATH was clobbered and only had Lilypond path
in
it. See attached screenshot.
Thankfully I had an open cmd window to restore PATH.
See http://code.google.com/p/lilypond/issues/detail?id=1948
__
Comment #5 on issue 1743 by pkx1...@gmail.com: lilypond-2.15.4-1.mingw.exe
does not install PATH on Windows 7 SP1
http://code.google.com/p/lilypond/issues/detail?id=1743
Issue 1948 has been merged into this issue.
___
bug-lilypond mailing list
bug
Status: New
Owner:
New issue 1948 by luke.bak...@gmail.com: Windows install clobbered system
PATH
http://code.google.com/p/lilypond/issues/detail?id=1948
lilypond-2.14.2-1.mingw.exe
Windows 7 SP1
After running installer, system PATH was clobbered and only had Lilypond
path in it. See
Updates:
Status: Fixed
Labels: -Patch-push fixed_2_15_14
Comment #11 on issue 1321 by bordage@gmail.com: Enhancement: add
partcombineUp and partcombineDown functions
http://code.google.com/p/lilypond/issues/detail?id=1321
Pushed as bb7cac7b276bd7d1335523f3be8df815cf894ece.
Updates:
Labels: -Patch-countdown Patch-needs_work
Comment #9 on issue 1844 by pkx1...@gmail.com: Changes variable names in
include/beam-scoring-problem.hh and beam-quanting.cc
http://code.google.com/p/lilypond/issues/detail?id=1844
there is no Patch on-hold :) so I'll set this back t
Updates:
Labels: -Fixed_215_14 Fixed_2_15_14
Comment #11 on issue 1929 by colinpkc...@gmail.com:
stem-tremolo-position.ly broken
http://code.google.com/p/lilypond/issues/detail?id=1929
(No comment was entered for this change.)
___
bug-lily
Updates:
Labels: Fixed_215_14
Comment #10 on issue 1929 by colinpkc...@gmail.com:
stem-tremolo-position.ly broken
http://code.google.com/p/lilypond/issues/detail?id=1929
(No comment was entered for this change.)
___
bug-lilypond mailing li
Updates:
Labels: Fixed_2_15_14
Comment #5 on issue 1921 by colinpkc...@gmail.com: Creates convert-ly rules
for flag syntax changes
http://code.google.com/p/lilypond/issues/detail?id=1921
(No comment was entered for this change.)
___
bug-li
Updates:
Labels: Fixed_2_15_14
Comment #14 on issue 1855 by colinpkc...@gmail.com: Prevents nested tuplets
from colliding
http://code.google.com/p/lilypond/issues/detail?id=1855
(No comment was entered for this change.)
___
bug-lilypond ma
Updates:
Labels: Fixed_2_15_14
Comment #13 on issue 1846 by colinpkc...@gmail.com: Improves horizontal
spacing of axis groups that SpanBar grobs traverse
http://code.google.com/p/lilypond/issues/detail?id=1846
(No comment was entered for this change.)
___
Updates:
Labels: Fixed_2_15_14
Comment #2 on issue 910 by colinpkc...@gmail.com: Non-allowed span-bars
should not affect Lyrics
http://code.google.com/p/lilypond/issues/detail?id=910
(No comment was entered for this change.)
___
bug-lilypo
Updates:
Status: Fixed
Comment #6 on issue 1491 by percival.music.ca: git-cl hangs when uploading
patches due to bad mime-type
http://code.google.com/p/lilypond/issues/detail?id=1491
fixed in git now, at least for scm + ps + texi. If problem reappears, just
add the relevant extensi
Updates:
Labels: -Patch-needs_work Patch-review
Comment #29 on issue 1852 by janek.li...@gmail.com: manuals needs more
explicit dependencies
http://code.google.com/p/lilypond/issues/detail?id=1852
This seems to work - i see side-by-side diffs of all files:
http://codereview.appspot.
30 matches
Mail list logo
