bug#29400: 26.0; Add Elisp manual index entry for `defvar' to node `Compiler Errors'

[Drew Adams <drew.adams@oracle.com>]

> > > but I don't understand why you wanted an
> > > index entry with "defvar" in it.  A reader who will look for "defvar"
> > > when they want to find ways of suppressing compiler warnings already
> > > knows that defvar is used for that purpose, so why would they use
> > > such a topic at Info-index's prompt?
> >
> > To find exactly what the manual says about it.
> 
> But defvar is described elsewhere, and index entries about it should
> lead there.  And after my changes, the description there mentions its
> use for suppressing warnings, so I don't think an index entry leading
> elsewhere is needed.

That was the point of the bug report.  You have added
mention of supressing warnings to the node that is
indexed by `defvar', which responds to the report.
(And hopefully you will also have added there a link
to the more complete coverage of compiler warnings.)

> > Looking in the index for `warning' is not the only
> > reasonable way to use an index for this - see above.
> 
> Feel free to suggest other topics, but "defvar" is
> definitely not one of them.

You just got through admitting that it is one of them.
You corrected, you say, the node that index-entry
`defvar' points to, by adding info there about
suppressing warnings (and presumably linking to the
node that deals more generally with such warnings and
their suppression).