Updates:
Status: Verified
Comment #17 on issue 935 by colinpkc...@gmail.com: Enhancement: optional
arguments in music functions
http://code.google.com/p/lilypond/issues/detail?id=935
(No comment was entered for this change.)
___
bug-lilypo
Updates:
Status: Fixed
Labels: -Patch-needs_work fixed_2_15_13
Comment #16 on issue 935 by d...@gnu.org: Enhancement: optional arguments
in music functions
http://code.google.com/p/lilypond/issues/detail?id=935
Pushed as b4ff85a2416e4b80deb9eef8329cd230ee4dc944 (and the two pr
Updates:
Labels: -Patch-new Patch-needs_work
Comment #15 on issue 935 by pkx1...@gmail.com: Enhancement: optional
arguments in music functions
http://code.google.com/p/lilypond/issues/detail?id=935
David,
1920 and it seems, from your last but one comment on
http://codereview.appspo
Updates:
Blockedon: -1920
Comment #14 on issue 935 by pkx1...@gmail.com: Enhancement: optional
arguments in music functions
http://code.google.com/p/lilypond/issues/detail?id=935
(No comment was entered for this change.)
___
bug-lilypond m
Updates:
Blockedon: 1920
Comment #13 on issue 935 by percival.music.ca: Enhancement: optional
arguments in music functions
http://code.google.com/p/lilypond/issues/detail?id=935
(No comment was entered for this change.)
___
bug-lilypond ma
Updates:
Status: Started
Comment #12 on issue 935 by d...@gnu.org: Enhancement: optional arguments
in music functions
http://code.google.com/p/lilypond/issues/detail?id=935
(No comment was entered for this change.)
___
bug-lilypond mailing
Updates:
Labels: Patch-new
Comment #11 on issue 935 by d...@gnu.org: Enhancement: optional arguments
in music functions
http://code.google.com/p/lilypond/issues/detail?id=935
Patch has been reverted. It exposes programming errors in the existing
code base, namely markup commands ca
Comment #10 on issue 935 by brownian.box: Enhancement: optional arguments
in music functions
http://code.google.com/p/lilypond/issues/detail?id=935
Fixed in which stable, please?
(and regtest would be great, I would know how to verify)
___
bug-lil
Comment #9 on issue 935 by reinhold...@gmail.com: Enhancement: optional
arguments in music functions
http://code.google.com/p/lilypond/issues/detail?id=935
When will you add a simple regtest? Normally, once someone pushes a patch
without a regtest, nobody will think about a regtest any more
Updates:
Status: Fixed
Labels: -Patch-countdown
Comment #8 on issue 935 by d...@gnu.org: Enhancement: optional arguments in
music functions
http://code.google.com/p/lilypond/issues/detail?id=935
Pushed as 83055a30e52c14b0fd49d6df3eb1c7af476ecb4b
Documentation and regtests are
Updates:
Labels: -Patch-review Patch-countdown
Comment #7 on issue 935 by colinpkc...@gmail.com: Enhancement: optional
arguments in music functions
http://code.google.com/p/lilypond/issues/detail?id=935
(No comment was entered for this change.)
__
Updates:
Labels: -Patch-needs_work Patch-review
Comment #6 on issue 935 by d...@gnu.org: Enhancement: optional arguments in
music functions
http://code.google.com/p/lilypond/issues/detail?id=935
Ok, I guess the current version is about as useful as it may become, so I
am changing th
Updates:
Labels: -Patch-review Patch-needs_work
Comment #5 on issue 935 by colinpkc...@gmail.com: Enhancement: optional
arguments in music functions
http://code.google.com/p/lilypond/issues/detail?id=935
Joe Neeman writes:
> On Mon, Sep 19, 2011 at 9:35 PM, David Kastrup wrote:
>
Comment #4 on issue 935 by colinpkc...@gmail.com: Enhancement: optional
arguments in music functions
http://code.google.com/p/lilypond/issues/detail?id=935
FWIW, I ran make and make check with no obvious problems. The regtests
showed some long lists of entries in logfiles (graphviz.log and
Updates:
Status: Started
Owner: d...@gnu.org
Cc: v.villen...@gmail.com
Labels: -Priority-Postponed Patch-review
Comment #3 on issue 935 by d...@gnu.org: Enhancement: optional arguments in
music functions
http://code.google.com/p/lilypond/issues/detail?id=935
An
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
Comment #1 on issue 935 by john.mandereau: Enhancement: optional arguments
in music functions
http://code.google.com/p/lilypond/issues/detail?id=935
Have you considered previous discussion like the subthread starting at
http://lists.gnu.org/archive/html/lilypond-devel/2009-08/msg00233.html
be
Status: Accepted
Owner: v.villenave
Labels: Type-Enhancement Priority-Postponed Bounty
New issue 935 by v.villenave: Enhancement: optional arguments in music
functions
http://code.google.com/p/lilypond/issues/detail?id=935
Currently, we can't have optargs in music-functions. It would be *ver
18 matches
Mail list logo
