bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: info --index not finding all indexed entries


From: Karl Berry
Subject: Re: info --index not finding all indexed entries
Date: Fri, 30 Jul 2010 23:39:30 GMT

    Neither the 'Index Entries' nor the 'Indexing Commands' node of the
    Texinfo manual mention that duplicates should be avoided.

I recall seeing Bob's words about writing index entries and avoiding
duplicates somewhere.  I will hunt.  (And see about fixing some of
Texinfo's duplicates.)  BTW, it's certainly a matter of style, not
technically erroneous input.

    I'm wondering why the 'Command List' node
    doesn't use @ftable instead of @table

The Command List node isn't indexed because those are just one-sentence
summaries.  Not worth indexing.  The real descriptions are elsewhere,
and are indexed there.

Beyond that, Bob indexed the Texinfo commands without the leading @
because with the prefix there would be hundreds of entries under @.
This would not be very friendly (admittedly a matter of opinion, but
obviously it was his opinion), especially in the printed manual -- it's
nicer to have refill under r in the function index, ie, have the
commands grouped by letter instead of in one huge list under @.

Therefore, @ftable couldn't be used even if we wanted to index the
Command List node, since obviously the @item's in that table do start
with @address@hidden

As I wrote Ralf separately ... this
omitting-common-prefix-for-better-sorting thing is pretty much the valid
reason I've ever been able to see for having separate indexes.
Otherwise, it's just a pain for users to have a bunch of different
places to look, assuming knowledge may not have.  Again, especially for
the printed manual.  (I looked just now, and the Autoconf manual is even
worse than Emacs in this regard -- nine indexes!  Yikes!)

I could imagine fancy/obscure new features to specify the common prefix,
and then info --index could apply the prefix, but ... anyway ...

    Meanwhile, I found this little typo, see patch below.

Thanks.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]