From: David Engster <deng@randomsample.de>
To: Glenn Morris <rgm@gnu.org>
Cc: 8518-done@debbugs.gnu.org
Subject: bug#8518: 24.0.50; 'byte-compile-error-on-warn' no effect on 'defvar ignored because X is let-bound' warning
Date: Tue, 19 Apr 2011 07:39:50 +0200 [thread overview]
Message-ID: <87ipuahk9l.fsf@engster.org> (raw)
In-Reply-To: <84o5vh34m.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 18 Apr 2011 13:37:45 -0400")
Glenn Morris writes:
> The warning does not come from the compiler, it comes from when the
> code is evaluated. You get the same result with:
>
> emacs -batch -L . -l ./test.el
Oh, you're right, of course. Sorry for the noise.
-David
prev parent reply other threads:[~2011-04-19 5:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-18 9:22 bug#8518: 24.0.50; 'byte-compile-error-on-warn' no effect on 'defvar ignored because X is let-bound' warning David Engster
2011-04-18 17:37 ` Glenn Morris
2011-04-19 5:39 ` David Engster [this message]
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=87ipuahk9l.fsf@engster.org \
--to=deng@randomsample.de \
--cc=8518-done@debbugs.gnu.org \
--cc=rgm@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).