Issue 1034 in lilypond: Documentation: categorizing music-function docstrings

[lilypond]

Status: Accepted
Owner: ----
Labels: Type-Documentation Priority-Low Maintainability

New issue 1034 by v.villenave: Documentation: categorizing music-function  
docstrings
http://code.google.com/p/lilypond/issues/detail?id=1034

In NR Appendix 1.15 (Available music functions), currently you have, in
bulk, user-oriented functions like \breathe, and more developer-oriented
functions like \assertBeamQuant.  Some come from music-functions-init.ly,
others come from property-init.ly.

There's some inconsistency in these files, by the way: some predefined
overrides like \harmonicsOn are defined in a pure-LilyPond way (i.e.
without any docstring), while others are defined as music-functions.  Do we
want to keep it that way?

By categorizing these functions we could subdivide this appendix and make
it a lot more usable, even add @cindex and @lilypond examples in the
doc-strings, etc. (much like Nicolas did with the "overview of markup
commands" appendix).

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings