From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Ivan Kanis <ivan.kanis@googlemail.com>
Cc: Thierry Volpiatto <thierry.volpiatto@gmail.com>, 12124@debbugs.gnu.org
Subject: bug#12124: 24.1.50; warning pollution
Date: Mon, 06 Aug 2012 06:35:34 -0400 [thread overview]
Message-ID: <jwv4nog48fg.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87lihtn3rf.fsf@kanis.fr> (Ivan Kanis's message of "Sun, 05 Aug 2012 10:26:28 +0200")
>>> Why instead of keeping old definitions of labels and flet don't we use
>>> aliases for cl-flet/labels (among others)?
>> Because they do not do the same (almost, but not quite).
> I think that the buffer *Compile Log* shouldn't pop up. It should behave
> like *Message*.
I think you're right that in such a use-case it shouldn't pop up,
although in the usual byte-compilation case it should.
> The problem is in emacs-w3m. It annoys me for mundane
> task such as reading mail or catching up news in newsticker.
But it's also the case that emacs-w3m probably shouldn't byte-compile
code at run-time. Can you try and figure out which it does that?
Stefan
next prev parent reply other threads:[~2012-08-06 10:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 17:26 bug#12124: 24.1.50; warning pollution Ivan Kanis
2012-08-02 17:50 ` Thierry Volpiatto
2012-08-03 9:52 ` Stefan Monnier
2012-08-03 10:37 ` Thierry Volpiatto
2012-08-03 23:20 ` Stefan Monnier
2012-08-04 4:15 ` Thierry Volpiatto
2012-08-05 8:26 ` Ivan Kanis
2012-08-06 10:35 ` Stefan Monnier [this message]
2012-08-11 14:31 ` Ivan Kanis
2012-08-11 15:29 ` Stefan Monnier
2012-08-11 14:32 ` Ivan Kanis
2012-08-11 15:30 ` Stefan Monnier
2012-08-12 8:26 ` Ivan Kanis
2012-08-12 16:44 ` Stefan Monnier
2012-08-13 18:17 ` Ivan Kanis
2021-12-06 23:36 ` bug#12124: *Compile Log* pops up for compile warnings from programatic calls to byte-compile Stefan Kangas
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=jwv4nog48fg.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=12124@debbugs.gnu.org \
--cc=ivan.kanis@googlemail.com \
--cc=thierry.volpiatto@gmail.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 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).