Updates:
Labels: -Patch-review Patch-push
Comment #5 on issue 456 by colinpkc...@gmail.com: \laissezVibrer in chords
http://code.google.com/p/lilypond/issues/detail?id=456
Counted down to 20110914, but needs a few minor tweaks; see Rietveld
Updates:
Labels: -Patch-review Patch-push
Comment #2 on issue 1876 by colinpkc...@gmail.com: MusicXML: fix case when
some elements have a staff number, while others don't
http://code.google.com/p/lilypond/issues/detail?id=1876
Counted down to 201
Updates:
Labels: -Patch-review Patch-needs_work
Comment #17 on issue 1193 by colinpkc...@gmail.com: Enhancement: internal
ledger lines
http://code.google.com/p/lilypond/issues/detail?id=1193
Changes requested; see Rietveld.
___
bug-lilypon
Updates:
Labels: -Patch-review Patch-needs_work
Comment #5 on issue 1292 by colinpkc...@gmail.com: Enhancement:
twelve-notation support
http://code.google.com/p/lilypond/issues/detail?id=1292
Changes requested; see Rietveld.
___
bug-lilypo
Comment #5 on issue 1878 by colinpkc...@gmail.com: Add support for custom
ledger positions, using two new staff-symbol properties
http://code.google.com/p/lilypond/issues/detail?id=1878
Corrections requesated; see Rietveld.
___
bug-lilypond mailin
Updates:
Labels: -Patch-review Patch-needs_work
Comment #4 on issue 1878 by colinpkc...@gmail.com: Add support for custom
ledger positions, using two new staff-symbol properties
http://code.google.com/p/lilypond/issues/detail?id=1878
Corrections requesated; see Rietveld.
___
Updates:
Labels: -Patch-review Patch-push
Comment #8 on issue 1852 by colinpkc...@gmail.com: manuals needs more
explicit dependencies
http://code.google.com/p/lilypond/issues/detail?id=1852
Counted down to 20110914
___
bug-lilypond
Updates:
Labels: -Patch-review Patch-needs_work
Comment #6 on issue 1873 by colinpkc...@gmail.com: Added glyphs for Kievan
Notation
http://code.google.com/p/lilypond/issues/detail?id=1873
Changes requested; see Rietveld link.
___
bug-lilyp
Updates:
Labels: -Patch-review Patch-push
Comment #37 on issue 1776 by colinpkc...@gmail.com: Doc: NR - Polymetric
Notation \compoundMeter isn't documented
http://code.google.com/p/lilypond/issues/detail?id=1776
Counted down to 201
Comment #5 on issue 1128 by n.putt...@gmail.com: Text pedal mark not closed
at music end
http://code.google.com/p/lilypond/issues/detail?id=1128
So, apparently creating a grob for "*" in ::finalize does not work. Any
idea how to make this work?
Couldn't you create the grob earlier so it's
Updates:
Labels: Patch-needs_work
Comment #4 on issue 1128 by pkx1...@gmail.com: Text pedal mark not closed
at music end
http://code.google.com/p/lilypond/issues/detail?id=1128
Just adding patch-needs_work to tracker so that it shows up as at least
having a patch.
___
Comment #1 on issue 1883 by pkx1...@gmail.com: change longas similarly to
how breves were changed
http://code.google.com/p/lilypond/issues/detail?id=1883
Passes make and reg tests (but there are differences for the pedants out
there) screenshots attached.
Attachments:
Screenshot.p
Updates:
Labels: -Patch-new Patch-review
Comment #1 on issue 1887 by pkx1...@gmail.com: Doc: adding doc strings for
\...DashPattern and \harmonicBy...
http://code.google.com/p/lilypond/issues/detail?id=1887
Passes make and reg tests
___
bu
Comment #7 on issue 1881 by percival.music.ca: Multiple cyclic dependency
errors for Beam/Stem
http://code.google.com/p/lilypond/issues/detail?id=1881
I deleted a few comments which established that the binary must be built
with
../configure --disable-optimising
I can confirm the cyclic
Comment #14 on issue 1839 by benko@gmail.com: Improves some parmesan
noteheads.
http://code.google.com/p/lilypond/issues/detail?id=1839
the first ligature (to the syllable "Ie-") is \[ f1 g1 \].
___
bug-lilypond mailing list
bug-lilypond@gnu.o
Updates:
Labels: -Type-Critical Type-Defect
Comment #2 on issue 1884 by percival.music.ca: Warnings from simultaneous
slurs with parallel music
http://code.google.com/p/lilypond/issues/detail?id=1884
Printing a warning instead of silently dropping notation is not a
regression. :)
Looks like a valid bug report.
Fwd to bug- (it was originally sent to -user).
On 12 September 2011 22:08, Ed Gordijn wrote:
>
> Hi List,
>
> I am working on a piece with three movements. I organized my score in
> different files, for the tiny-example let's say two. The fist file is
> instrument.l
Neil Puttock writes:
> On 14 September 2011 20:38, Reinhold Kainhofer wrote:
>
>> Unfortunately, lilypond is called with --verbose in
>> Documentation/GNUmakefile,
>> so these warnings are hidden inside hundreds of useless lines :(
>
> Do we really need main_input_name_ to be called "" here?
>
On 14 September 2011 20:38, Reinhold Kainhofer wrote:
> Unfortunately, lilypond is called with --verbose in Documentation/GNUmakefile,
> so these warnings are hidden inside hundreds of useless lines :(
Do we really need main_input_name_ to be called "" here?
Can't we just change it to an empty
Am Wednesday, 14. September 2011, 20:42:04 schrieb lilyp...@googlecode.com:
> while working on issue 1135 (which is closed now!) I found out
> that some functions still lack a proper doc string.
> Attached is a patch which adds the missing (_i ...) to four of them.
Here's a patch that changes make
On Sep 13, 2011, at 11:57 PM, Colin Campbell wrote:
> On 11-09-13 10:29 AM, Stan Sanderson wrote:
>> Thanks. I will recheck the list setting.
>> Looks like Bugreports will see this twice!
>>
>> Stan
>>
>> On Sep 13, 2011, at 11:21 AM, Xavier Scheuer wrote:
>>
>>> On 13 September 2011 18:05, S
Status: Started
Owner: janek.li...@gmail.com
Labels: Type-Documentation Patch-new
New issue 1887 by janek.li...@gmail.com: Doc: adding doc strings for
\...DashPattern and \harmonicBy...
http://code.google.com/p/lilypond/issues/detail?id=1887
By Marc Hohl:
while working on issue 1135 (which i
Comment #3 on issue 1128 by reinhold...@gmail.com: Text pedal mark not
closed at music end
http://code.google.com/p/lilypond/issues/detail?id=1128
The problem is that the brackets use a spanner, which will properly end,
while the text style uses separate grobs for each of the texts
("Ped.
Comment #2 on issue 935 by d...@gnu.org: Enhancement: optional arguments in
music functions
http://code.google.com/p/lilypond/issues/detail?id=935
Before investing unnecessary work here: is the bounty offer still good or
should it be removed from the issue report?
There are some situation
Updates:
Summary: Try to auto-detect cyclic references in header fields
(was 'cycling markup reference segfaults')
Labels: -Patch-review Patch-needs_work
Comment #18 on issue 380 by pkx1...@gmail.com: Try to auto-detect cyclic
references in header fields (was 'cycling markup referen
Updates:
Status: Started
Owner: d...@gnu.org
Comment #5 on issue 824 by d...@gnu.org: Enhancement: anchors in the music
stream
http://code.google.com/p/lilypond/issues/detail?id=824
Looking at my rather cryptic mails in the bug report, it looks like I
should have been more e
On 11-09-14 06:21 AM, lilyp...@googlecode.com wrote:
Comment #4 on issue 1886 by brownian.box: Enhancement request: add a
parameter/variable to control the spacing of lines in a score
http://code.google.com/p/lilypond/issues/detail?id=1886
"Invalid" as being a duplicate for issue 1885.
I gue
Comment #4 on issue 1886 by brownian.box: Enhancement request: add a
parameter/variable to control the spacing of lines in a score
http://code.google.com/p/lilypond/issues/detail?id=1886
"Invalid" as being a duplicate for issue 1885.
I guess "duplicate" status still need to be verified and f
Comment #3 on issue 1886 by x.sche...@gmail.com: Enhancement request: add a
parameter/variable to control the spacing of lines in a score
http://code.google.com/p/lilypond/issues/detail?id=1886
Yes, that freaked me out too, I was about to ask the same question.
But then I saw issue #1885
http
Comment #2 on issue 1886 by reinhold...@gmail.com: Enhancement request: add
a parameter/variable to control the spacing of lines in a score
http://code.google.com/p/lilypond/issues/detail?id=1886
Why is this invalid? That's a reasonable request (and I was astonished that
my test file didn't
Updates:
Summary: Warnings from simultaneous slurs with parallel music
Comment #1 on issue 1884 by reinhold...@gmail.com: Warnings from
simultaneous slurs with parallel music
http://code.google.com/p/lilypond/issues/detail?id=1884
Actually, this has nothing to do with partcombine. Rat
Am Wednesday, 14. September 2011, 06:47:50 schrieb Colin Campbell:
> On 11-09-13 09:29 PM, Nick Payne wrote:
> > Ok, the following small example reproduces the error on my system with
> > 2.15.11:
The minimal example is (the normal fingering "-1" does not have any influence,
so it should be remov
Comment #3 on issue 1784 by janek.li...@gmail.com: Adds epsilon to Bezier
range calculations
http://code.google.com/p/lilypond/issues/detail?id=1784
This snippet throws a "programming error: no solution found for Bezier
intersection" error - i guess it's related to this patch?
\version "2
Comment #4 on issue 824 by d...@gnu.org: Enhancement: anchors in the music
stream
http://code.google.com/p/lilypond/issues/detail?id=824
This is actually basic enough to make a nice example in "Extending
Lilypond".
___
bug-lilypond mailing list
Comment #3 on issue 824 by d...@gnu.org: Enhancement: anchors in the music
stream
http://code.google.com/p/lilypond/issues/detail?id=824
As to the $300, my Email address is registered at Paypal, but I'll also
provide bank account data on request (should be without fee in the Euro
zone).
35 matches
Mail list logo
