Re: Issue 1920 in lilypond: arguments in docs don't alway agree

[lilypond]

Comment #2 on issue 1920 by address@hidden: 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  
83055a30e52c14b0fd49d6df3eb1c7af476ecb4b, the merge commit for optional  
music function arguments which has the side-effect of checking those  
arguments.

The regtests all pass, but documentation builds don't currently complete.   
As a consequence, the optional music function argument patch has been  
reverted and is pending a fix of this issue.

If desired, I can try to prepare a separate patch only adding the  
type-checking.  However, this is likely non-trivial since the optional  
music function patch uses a completely different approach to type-checking,  
so this patch would have to be prepared independently and would likely lead  
to a merge conflict later.