Comment #4 on issue 855 by markpolesky: fix the command index
http://code.google.com/p/lilypond/issues/detail?id=855
I agree with Graham's comment #5 in issue 788 - modifying
lilypond-texi2html.init is not the right solution since it
doesn't address the info/PDF docs.
Regarding this:
@funindex \foo
@funindex foo
We can take a formal vote if necessary, but does it looks
like most of us already favor keeping only the "\foo"
version?
Also, is anybody even remotely interested in tackling the
possibility of ignoring "\" during the sorting of the index?
annotate-spacing
\autochange
auto-first-page-number
\accepts
I haven't heard a peep from anyone, and this has been around
for long enough.
********************
"Graham Percival" wrote:
Questions:
1) Everything marked with a @funindex in the docs ends
up in *both* NR indices. How and why do these items
end up in appendix F?
Because @funindex calls both @findex and @kindex, and we
merge a copy of @findex with @kindex.
2) Why do we need @funindex? Why don't we just use
these:
@findex
@printindex fn
Because then anything in appendix E won't appear in
appendix F, and (at some point in our past) there was a
feeling that commands should be printed in both indices.
Ugh. Who here wants commands printed in both indices?
It's so overstuffed already. A simple note with a
@ref{LilyPond command index} at the top of the general
index would be so much better, IMO. For me, the presence
of the commands in the general index is nothing but a
nuisance. The general index in PDF is 20 pages long, and
almost half of the entries are duplicated from the command
index.
In fact, I'd prefer to see three indices:
"Command index", syntactic items not starting with a letter:
@findex !
@findex \abs-fontsize
...
@printindex fn
"Variable index", syntactic items starting with a letter:
@vindex alignAboveContext
@vindex beamExceptions
...
@printindex vr
"General index", concepts *only*:
@cindex beaming in cadenzas
@cindex page breaks
...
@printindex cp
Does anyone else think this would be nice? As it stands
it's too easy to miss something like "beamExceptions" in
the command index since it's not betweem "\beam" and
"\bendAfter". And two @ref's at the top of each index (to
the other indices) would be easy to spot. And a decent
sed script could do most of the work.
Is now a bad time to resurrect this?
- Mark
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
