From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: 12965@debbugs.gnu.org
Subject: bug#12965: 24.3.50; Suppress *Compile-log* buffer during init
Date: Fri, 23 Nov 2012 10:46:47 -0500 [thread overview]
Message-ID: <jwvwqxc1g6z.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87obiog43h.fsf@gmail.com> (Jambunathan K.'s message of "Fri, 23 Nov 2012 13:09:46 +0530")
> When I am starting up my Emacs, I am getting a split window with top
> half containing `initial-buffer-choice' and bottom half showing
> "*Compile-Log*" contents.
> ,----
> | elisp/bbdb-2.35/lisp/bbdb-com.elc:Warning: Use `with-current-buffer' rather
> | than save-excursion+set-buffer
> | .emacs.elc:Warning: reference to free variable `Info-current-file'
> `----
> Should snippet below /really/ produce a "*Compile-Log*" when /loading/
> my .emacs.elc.
This is not a new problem, actually. Even if it didn't happen earlier,
it's not because byte-compiler's warnings have changed, but because
some change either causes a code to be byte-compiled which wasn't before.
My guess is that the changes in advice.el have as a side consequence
that your advice now gets compiled even before info.el is loaded.
> Anyways, I need a way to have this "*Compile-Log*" suppressed or buried.
Yes, I think we should change bytecomp.el so that those warnings get
output via `message' when we're not byte-compiling a whole file.
> AFAIK, this "split-window-with-compile-log-in-foreground" is a fairly
> recent behaviour with the trunk.
Actually, no, it's been there for quite a while.
Stefan
next prev parent reply other threads:[~2012-11-23 15:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 7:39 bug#12965: 24.3.50; Suppress *Compile-log* buffer during init Jambunathan K
2012-11-23 15:46 ` Stefan Monnier [this message]
2012-11-26 20:01 ` Stefan Monnier
2012-11-27 4:11 ` Jambunathan K
2012-11-27 5:15 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvwqxc1g6z.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=12965@debbugs.gnu.org \
--cc=kjambunathan@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 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.