[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#11178: 24.0.94; Elisp manual: add index entries for :link LINK-DATA
bug#11178: 24.0.94; Elisp manual: add index entries for :link LINK-DATA alternatives
Wed, 11 Apr 2012 22:35:51 +0300
> From: "Drew Adams" <address@hidden>
> Cc: <address@hidden>, <address@hidden>
> 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 address@hidden, 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
> 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.