unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Schmidt <christopher@ch.ristopher.com>
To: 12371@debbugs.gnu.org
Subject: bug#12371: 24.2.50; macroexpand-all reporting warnings to *Compile-Log*
Date: Thu,  6 Sep 2012 14:58:22 +0100 (BST)	[thread overview]
Message-ID: <87y5knb6dg@ch.ristopher.com> (raw)

emacs -q
M-: (macroexpand-all '(mapc '(lambda ()) nil)) RET

Debugger entered--Lisp error: (void-function byte-compile-log-warning)

emacs -q
M-x load-library RET bytecomp RET
M-: (macroexpand-all '(mapc '(lambda ()) nil)) RET

A *Compile-Log* buffer appears, with the following content

    Warning: (lambda nil ...) quoted with ' rather than with #'

This is utterly confusing.  There is no compilation going on.  (Another
user experience regarding this issue can be found in bug report 12362 -
<87392vtj24.fsf@jidanni.org>.)

macroexp--expand-all, which is the originator of the warning, calls
byte-compile-log-warning without consulting byte-compile-warnings.

I think the warning message should include a hint that it was generated
by macroexpanding code and byte-compile-warnings should be consulted as
well.

GNU Emacs 24.2.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.10) of
2012-09-06.

        Christopher





             reply	other threads:[~2012-09-06 13:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-06 13:58 Christopher Schmidt [this message]
2012-09-06 16:46 ` bug#12371: 24.2.50; macroexpand-all reporting warnings to *Compile-Log* Christopher Schmidt
2012-09-19 20:01 ` Stefan Monnier
2012-09-20  1:00 ` bug#12371: macroexp--funcall-if-compiled broke bootstrap for me Paul Eggert
2012-09-20  3:30   ` Stefan Monnier
2012-09-20  4:56     ` Paul Eggert
2012-09-20  5:11       ` Paul Eggert
2012-09-20  8:21         ` Troels Nielsen
2012-09-20 12:43           ` Stefan Monnier
2012-09-20 14:16             ` Stefan Monnier

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=87y5knb6dg@ch.ristopher.com \
    --to=christopher@ch.ristopher.com \
    --cc=12371@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).