Updates:
Status: Verified
Comment #5 on issue 1920 by brownian.box: arguments in docs don't alway
agree
http://code.google.com/p/lilypond/issues/detail?id=1920
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lil
Issue 1920: arguments in docs don't alway agree
http://code.google.com/p/lilypond/issues/detail?id=1920
This issue is no longer blocking issue 935.
See http://code.google.com/p/lilypond/issues/detail?id=935
--
You received this message because you are listed in the owner
or CC fields of this issu
Updates:
Status: Fixed
Labels: fixed_2_15_13
Comment #3 on issue 1920 by d...@gnu.org: arguments in docs don't alway
agree
http://code.google.com/p/lilypond/issues/detail?id=1920
Apparently fixed with commit 47657f55288626b9b18d14c31961c0a68502bc1c. It
would not seem that m
Comment #2 on issue 1920 by d...@gnu.org: arguments in docs don't alway
agree
http://code.google.com/p/lilypond/issues/detail?id=1920
Concerned are just markup and markup list commands (music functions have
always been typechecked). One known test is cherry-picking
83055a30e52c14b0fd49d6
Issue 1920: arguments in docs don't alway agree
http://code.google.com/p/lilypond/issues/detail?id=1920
This issue is now blocking issue 935.
See http://code.google.com/p/lilypond/issues/detail?id=935
--
You received this message because you are listed in the owner
or CC fields of this issue, or
Status: Accepted
Owner:
Labels: Type-Defect
New issue 1920 by percival.music.ca: arguments in docs don't alway agree
http://code.google.com/p/lilypond/issues/detail?id=1920
namely markup commands called with arguments not matching their
declaration. This is exposed by stricter type-check
