On Thu, 24 Apr 2008 11:40:58 +0200 David Kastrup <[EMAIL PROTECTED]> wrote:
> Having to specify a particular snippet makes sure that this snippet > (and thus the construct) indeed appears in the docs, and that its > absence will be noticed when compiling the documentation. You misunderstand. @lilypondfile will still be used for that. *sigh* OK, example time. Look at GDP output, NR 1.x Key signature. There's two snippets under "Selected Snippets". Those are produced by @lilyondfile. Those will remain. Scroll down to the "See also". Currently it says Snippets: Pitches. How much do you want to see Snippets: Pitches, dodecaponic-style..., makam, non-traditional..., preventing-extra..., preventing-natural... . (bear in mind that two of these items -- the most relevant onces -- are already directly included in this doc section) Also bear in mind that the whole point of LSR is that it lets us easily add and remove items from our docs. I forgot about this earlier; I was only thinking about renamed snippets. Updating these lists for the docs would be at least an hour per month. Cheers, - Graham _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
