Updates:
Status: Duplicate
Comment #2 on issue 1937 by mts...@gmail.com: Patch: Uses
Stem::beam_end_corrective to get tremolo heights right
http://code.google.com/p/lilypond/issues/detail?id=1937
This is a duplicate from the new git-cl.
__
Updates:
Status: Duplicate
Comment #1 on issue 1940 by mts...@gmail.com: Patch: Creates convert-ly
rules for flag syntax changes
http://code.google.com/p/lilypond/issues/detail?id=1940
the splitting rule in the new git-cl doesn't like parentheses...deleting
duplicated issue :)
__
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 1940 by mts...@gmail.com: Patch: Creates convert-ly rules for
flag syntax changes
http://code.google.com/p/lilypond/issues/detail?id=1940
Creates convert-ly rules for flag syntax changes
http://codereview.appspot.com/505004
Comment #20 on issue 1852 by janek.li...@gmail.com: manuals needs more
explicit dependencies
http://code.google.com/p/lilypond/issues/detail?id=1852
2011/9/27 Janek Warchoł :
I have an idea: you have used Graham's new git-cl, didn't you? Maybe
it forgot to add CC:lilypond-de...@gnu.org to t
Comment #19 on issue 1852 by janek.li...@gmail.com: manuals needs more
explicit dependencies
http://code.google.com/p/lilypond/issues/detail?id=1852
Julien > I did click publish now, hope it works. Do I need to add reviewers?
You don't need to add reviewers, but i still don't see it. Strang
Updates:
Labels: -Patch-push
Comment #18 on issue 155 by percival.music.ca: \parenthesize does not take
accidentals into account
http://code.google.com/p/lilypond/issues/detail?id=155
(No comment was entered for this change.)
___
bug-lilyp
Updates:
Labels: Patch-needs_work
Comment #18 on issue 1852 by percival.music.ca: manuals needs more explicit
dependencies
http://code.google.com/p/lilypond/issues/detail?id=1852
we can't review anything until it's uploaded. See issue 1491.
_
Updates:
Labels: -Patch-review Patch-countdown
Comment #7 on issue 1844 by colinpkc...@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
(No comment was entered for this change.)
Updates:
Labels: -Patch-review Patch-countdown
Comment #9 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: -Patch-review Patch-countdown
Comment #10 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.)
___
Updates:
Labels: -Patch-review Patch-countdown
Comment #2 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.)
__
Updates:
Labels: -Patch-review Patch-countdown
Comment #10 on issue 1871 by colinpkc...@gmail.com: Several fixes for
annotate-spacing
http://code.google.com/p/lilypond/issues/detail?id=1871
(No comment was entered for this change.)
___
bug
Updates:
Labels: -Patch-review Patch-countdown
Comment #8 on issue 1812 by colinpkc...@gmail.com: NR Context Layout Order
rewrite (5.1.7)
http://code.google.com/p/lilypond/issues/detail?id=1812
(No comment was entered for this change.)
___
Updates:
Labels: -Patch-review Patch-countdown
Comment #25 on issue 1477 by colinpkc...@gmail.com: suppress output for
expected warnings
http://code.google.com/p/lilypond/issues/detail?id=1477
(No comment was entered for this change.)
___
Updates:
Labels: -Patch-review Patch-countdown
Comment #9 on issue 1321 by colinpkc...@gmail.com: Enhancement: add
partcombineUp and partcombineDown functions
http://code.google.com/p/lilypond/issues/detail?id=1321
(No comment was entered for this change.)
__
Updates:
Labels: -Patch-review Patch-countdown
Comment #11 on issue 307 by colinpkc...@gmail.com: collision slur with
tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=307
(No comment was entered for this change.)
___
bug-l
Updates:
Labels: -Patch-review Patch-countdown
Comment #7 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-lil
Updates:
Labels: -Patch-review Patch-needs_work
Comment #4 on issue 1925 by colinpkc...@gmail.com: fingering misplaced when
avoiding slur, on some operating systems
http://code.google.com/p/lilypond/issues/detail?id=1925
Apparently, Keith is suggesting changes to this (see Rietveld).
Updates:
Labels: -Patch-review Patch-needs_work
Comment #2 on issue 1922 by colinpkc...@gmail.com: Adds StemTremolo to the
note column's element list.
http://code.google.com/p/lilypond/issues/detail?id=1922
See comments on Rietveld re extra spaciong in beamed tremolos.
_
Updates:
Labels: -Patch-review Patch-needs_work
Comment #3 on issue 1778 by colinpkc...@gmail.com: slashedGrace function
(graces with slashed stems but no slur, e.g. when grace is tied) needs
documenting
http://code.google.com/p/lilypond/issues/detail?id=1778
Neil has a couple of sp
Updates:
Labels: -Patch-review Patch-needs_work
Comment #18 on issue 11 by colinpkc...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Has there been a new patchset since Aug 30? AFAICS, this is still being
worked over.
_
Updates:
Labels: Patch-new
Comment #17 on issue 155 by joenee...@gmail.com: \parenthesize does not
take accidentals into account
http://code.google.com/p/lilypond/issues/detail?id=155#c17
Fix 155: parentheses include accidentals and dots.
Make parentheses around noteheads include acc
On 11-09-26 05:40 PM, Reinhold Kainhofer wrote:
Am Monday, 26. September 2011, 22:40:00 schrieb Nick Payne:
I haven't been able to create a small example that gets the bogus
warning in the log, but while trying to do so I managed to reproduce
what looks like a related/similar problem.
Thanks a
Status: Accepted
Owner:
Labels: Type-Defect Regression
New issue 1939 by colinpkc...@gmail.com: showLastLength with hidden tie
error message
http://code.google.com/p/lilypond/issues/detail?id=1939
Reported by Nick Payne and Reinhold Kainhofer:
Nick: I'm setting Bach's BWV853 (Prelude fro
Am Monday, 26. September 2011, 22:40:00 schrieb Nick Payne:
> I haven't been able to create a small example that gets the bogus
> warning in the log, but while trying to do so I managed to reproduce
> what looks like a related/similar problem.
Thanks a lot, it is your very problem (you just happen
Hi Heikki,
2011/9/25 Janek Warchoł :
> I will add a tracker issue for this bug tomorrow.
Added as issue 1938 http://code.google.com/p/lilypond/issues/detail?id=1938
> I'll also test your patch against current master.
I've checked that your patch can be applied to current master and that it work
Updates:
Summary: MIDI volume can exceed maximum value (Rietveld 5134047)
Comment #1 on issue 1938 by janek.li...@gmail.com: MIDI volume can exceed
maximum value (Rietveld 5134047)
http://code.google.com/p/lilypond/issues/detail?id=1938
Patch here http://codereview.appspot.com/5134047
Status: Started
Owner: janek.li...@gmail.com
Labels: Type-Defect Patch-new MIDI
New issue 1938 by janek.li...@gmail.com: MIDI volume can exceed maximum
value
http://code.google.com/p/lilypond/issues/detail?id=1938
http://lists.gnu.org/archive/html/lilypond-devel/2011-09/msg01029.html
Dynamic
Comment #17 on issue 1852 by julien.r...@gmail.com: manuals needs more
explicit dependencies
http://code.google.com/p/lilypond/issues/detail?id=1852
Old issue applied to .tely files and comment 10 comfirms that it works.
New issue applies to .texi files and is independent of the previous one.
Comment #16 on issue 1852 by janek.li...@gmail.com: manuals needs more
explicit dependencies
http://code.google.com/p/lilypond/issues/detail?id=1852
Hi,
as i'm the formal owner of this issue, i'd like to know what's its current
status. Should 1b99f1907fb77b0f3a0e65725776782c3eeaa025 be re
On 26/09/11 21:47, Reinhold Kainhofer wrote:
Hi Nick,
Am Monday, 26. September 2011, 11:27:01 schrieb Nick Payne:
I'm setting Bach's BWV853 (Prelude from WTC 1), using showLastLength to
just engrave the last six bars added, and as I add bars I'm getting
warnings about unterminated ties that com
Comment #15 on issue 1852 by julien.r...@gmail.com: manuals needs more
explicit dependencies
http://code.google.com/p/lilypond/issues/detail?id=1852
The sed code might be a bit obscure; here's what it produces for
contributor.dep:
./out/contributor.texi: contributor.texi
./out/contributor.
David Kastrup gnu.org> writes:
> Rational grace_part_.set_infinite (-1)
>
> should do. When make-moment is called omitting the grace part of the
> argument list, this should become the default.
>
Another interesting question, I think, is whether get_length() should
return 1/2 G-inf or 1/2 G0
Comment #14 on issue 1852 by julien.r...@gmail.com: manuals needs more
explicit dependencies
http://code.google.com/p/lilypond/issues/detail?id=1852
OK apparently git-cl crashed *while* the stuff was being uploaded to
Rietveld. The patch there is complete but you can't see the side-by-side
Comment #13 on issue 1852 by julien.r...@gmail.com: manuals needs more
explicit dependencies
http://code.google.com/p/lilypond/issues/detail?id=1852
Since speed is a concern I went with sed. New patch uploaded to
http://codereview.appspot.com/5131045
_
Comment #2 on issue 1931 by brownian.box: Doc: Snippet in NR (LSR snippet
591) MMRs 'staff-position = #0 should be revised
http://code.google.com/p/lilypond/issues/detail?id=1931
Are we still using priorities?
___
bug-lilypond mailing list
bug-lil
Updates:
Summary: Doc: Snippet in NR (LSR snippet 591) MMRs 'staff-position = #0
should be revised
Labels: Priority-Low
Comment #1 on issue 1931 by pkx1...@gmail.com: Doc: Snippet in NR (LSR
snippet 591) MMRs 'staff-position = #0 should be revised
http://code.google.com/p/lilypond/
Updates:
Summary: HTML Manuals on website do not have vertical scroll on Mobile
Versions of Safari Browser
Labels: -Needs-evidence
Comment #1 on issue 1934 by pkx1...@gmail.com: HTML Manuals on website do
not have vertical scroll on Mobile Versions of Safari Browser
http://code.goo
Updates:
Labels: Priority-Medium
Comment #1 on issue 1874 by pkx1...@gmail.com: some stems are no longer
transparent in the docs
http://code.google.com/p/lilypond/issues/detail?id=1874
(No comment was entered for this change.)
___
bug-lily
Updates:
Labels: Priority-Low
Comment #2 on issue 1935 by pkx1...@gmail.com: Doc: internal ledger lines
need to be documented in NR and added to Changes
http://code.google.com/p/lilypond/issues/detail?id=1935
(No comment was entered for this change.)
Comment #8 on issue 1919 by stans...@gmail.com: lilypond 2.15.12 fails on
darwin-ppc
http://code.google.com/p/lilypond/issues/detail?id=1919
I don't usually use the wife's iMac, so I haven't checked versions for some
time. I found that 2.15.8 is the last version which will run. Subsequent
Updates:
Status: Fixed
Labels: -Patch-review fixed_2_15_13
Comment #3 on issue 1909 by janek.li...@gmail.com: Doc: add a note about
\relative f to notation (Rietveld 5096046)
http://code.google.com/p/lilypond/issues/detail?id=1909
pushed 0d4c0b0979c200e54cffc6b68671df50d6b90a4
Updates:
Labels: -Type-Defect -Priority-Medium Type-Ugly
Comment #2 on issue 1266 by brownian.box: Dots in chords can not be moved
http://code.google.com/p/lilypond/issues/detail?id=1266
(No comment was entered for this change.)
___
bug-lilyp
Updates:
Status: Accepted
Comment #1 on issue 1937 by brownian.box: Patch: Uses
Stem::beam_end_corrective to get tremolo heights right
http://code.google.com/p/lilypond/issues/detail?id=1937
(No comment was entered for this change.)
___
bu
"m...@apollinemike.com" writes:
> On Jul 21, 2011, at 11:10 AM, lilyp...@googlecode.com wrote:
>>
>> I think that is a promising approach. I looked through the code
>> thinking about this issue two days ago, and began to look for a way
>> to default-initialize the grace_part_ of a Moment to som
Comment #4 on issue 1932 by d...@gnu.org: error: need \paper for paper block
http://code.google.com/p/lilypond/issues/detail?id=1932
The actual cause of the error was a problem in the docs, which you fixed
with a patch.
The documentation no longer gives invalid equivalent code, but it still
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 1937 by mts...@gmail.com: Patch: Uses Stem::beam_end_corrective
to get tremolo heights right
http://code.google.com/p/lilypond/issues/detail?id=1937
Uses Stem::beam_end_corrective to get tremolo heights right
http://coderev
47 matches
Mail list logo
