From: Drew Adams <drew.adams@oracle.com>
To: 29400@debbugs.gnu.org
Subject: bug#29400: 26.0; Add Elisp manual index entry for `defvar' to node `Compiler Errors'
Date: Wed, 22 Nov 2017 08:50:33 -0800 (PST) [thread overview]
Message-ID: <f03d7e3c-b121-4aad-bc5c-1f4a8fba506f@default> (raw)
Node `Compiler Errors' seems to be the only place in the Elisp manual
where we tell users that you can use a vacuous `defvar' (no value) to
suppress a byte-compiler warning about it not being defined.
But this node has no index entry - at least none that has the word
`defvar' in it. Please add such an entry.
And please either add the same info (about this use of a vacuous
`defvar') to node `Defining Variables' or add a cross-reference from
that node to node `Compiler Errors'.
As it is now, it is not so easy to find this info.
In GNU Emacs 26.0.90 (build 3, x86_64-w64-mingw32)
of 2017-10-13
Repository revision: 906224eba147bdfc0514090064e8e8f53160f1d4
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --without-dbus --host=x86_64-w64-mingw32
--without-compress-install 'CFLAGS=-O2 -static -g3''
next reply other threads:[~2017-11-22 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 16:50 Drew Adams [this message]
2017-11-24 14:42 ` bug#29400: 26.0; Add Elisp manual index entry for `defvar' to node `Compiler Errors' Eli Zaretskii
[not found] <<f03d7e3c-b121-4aad-bc5c-1f4a8fba506f@default>
[not found] ` <<83a7zbagbk.fsf@gnu.org>
2017-11-24 16:54 ` Drew Adams
2017-11-24 17:10 ` Eli Zaretskii
[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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f03d7e3c-b121-4aad-bc5c-1f4a8fba506f@default \
--to=drew.adams@oracle.com \
--cc=29400@debbugs.gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).