Subject: Re: bug#11178: 24.0.94; Elisp manual: add index entries for :link LINK-DATA alternatives

From: Eli Zaretskii <[email-masked]>
Date: Wed, 11 Apr 2012 22:35:51 +0300

> From: "Drew Adams" <[email-masked]>
> Cc: <[email-masked]>, <[email-masked]>
> Date: Wed, 11 Apr 2012 10:37:39 -0700
> 
> > > These are reference entries.  No different from indexing 
> > > individual function names or individual button properties.
> > 
> > Perhaps adding two more index entries, something like
> > 
> >   @cindex links to documentation for customization items
> >   @cindex customization items, links to documentation
> > 
> > would do the job.  Currently, I see only one index entry there:
> > 
> >   @kindex link@r{, customization keyword}
> > 
> > which IMO is not enough for when the reader wants to find information
> > about adding links to the docs.  The existing index entry only covers
> > efficiently the case when the reader is specifically looking for the
> > 'link' keyword and already knows what that's used for.
> 
> What Eli says is also pertinent.  But independent.
> 
> Again, you are talking about indexing _topics_.  I am talking about _reference_
> index entries.

We've been through this before, Drew, and we already established that
your views about indexing are not shared.  Bringing that up again
won't change that.

> If a user wants to look up the particular button property `follow-link', she
> does `i follow-link' and Bob's an uncle.

She can also do 'i link TAB', see "link, customization keyword" and
Bob's her uncle.  IOW, if she already knows she's after follow-link,
she'll have no trouble finding it.