all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 29400@debbugs.gnu.org
Subject: bug#29400: 26.0; Add Elisp manual index entry for `defvar' to node `Compiler Errors'
Date: Fri, 24 Nov 2017 19:10:28 +0200	[thread overview]
Message-ID: <83wp2f8uwr.fsf@gnu.org> (raw)
In-Reply-To: <f6b9ee9f-e49a-4d7d-9af8-12fb6f3af11d@default> (message from Drew Adams on Fri, 24 Nov 2017 08:54:39 -0800 (PST))

> Date: Fri, 24 Nov 2017 08:54:39 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 29400-done@debbugs.gnu.org
> 
> > 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.

> 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.





  reply	other threads:[~2017-11-24 17:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<f03d7e3c-b121-4aad-bc5c-1f4a8fba506f@default>
     [not found] ` <<83a7zbagbk.fsf@gnu.org>
2017-11-24 16:54   ` bug#29400: 26.0; Add Elisp manual index entry for `defvar' to node `Compiler Errors' Drew Adams
2017-11-24 17:10     ` Eli Zaretskii [this message]
     [not found] <<<f03d7e3c-b121-4aad-bc5c-1f4a8fba506f@default>
     [not found] ` <<<83a7zbagbk.fsf@gnu.org>
     [not found]   ` <<f6b9ee9f-e49a-4d7d-9af8-12fb6f3af11d@default>
     [not found]     ` <<83wp2f8uwr.fsf@gnu.org>
2017-11-24 17:39       ` Drew Adams
2017-11-22 16:50 Drew Adams
2017-11-24 14:42 ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83wp2f8uwr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=29400@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.