bug#12965: 24.3.50; Suppress *Compile-log* buffer during init

bug#12965: 24.3.50; Suppress *Compile-log* buffer during init

[Jambunathan K]

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.

Anyways, I need a way to have this "*Compile-Log*" suppressed or buried.
AFAIK, this "split-window-with-compile-log-in-foreground" is a fairly
recent behaviour with the trunk.


Annexure:

--8<---------------cut here---------------start------------->8---
;; (require 'info)
(defadvice info-display-manual
  (after my-info-display-manual activate)
  (rename-buffer
   (format "*info* (%s)"
	   (capitalize (file-name-directory Info-current-file)))))

(global-set-key "\bi" (quote info-display-manual))
--8<---------------cut here---------------end--------------->8---

In GNU Emacs 24.3.50.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
 of 2012-11-21 on debian-6.05
Bzr revision: 110967 rgm@gnu.org-20121121044755-u0jd8639omz57us3
Windowing system distributor `The X.Org Foundation', version 11.0.10707000
Important settings:
  value of $LANG: en_IN
  locale-coding-system: iso-latin-1-unix
  default enable-multibyte-characters: t

bug#12965: 24.3.50; Suppress *Compile-log* buffer during init

[Stefan Monnier]

> 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

bug#12965: 24.3.50; Suppress *Compile-log* buffer during init

[Stefan Monnier]

Actually, while the general problem is old, its appearance in your case
is indeed due to a recent change in advice.el which I think was a bug.
I've installed a patch on trunk which should fix the problem.
Please confirm,


        Stefan

bug#12965: 24.3.50; Suppress *Compile-log* buffer during init

[Jambunathan K]

> Actually, while the general problem is old, its appearance in your case
> is indeed due to a recent change in advice.el which I think was a bug.
> I've installed a patch on trunk which should fix the problem.
> Please confirm,

Fixed.  The bug can be closed.

Some book-keeping info,

    1. *Compile-Log* no longer comes to the fore.
    2. It contains a sole warning 

        ,----
        | elisp/bbdb-2.35/lisp/bbdb-com.elc:Warning: Use `with-current-buffer' rather
        |     than save-excursion+set-buffer
        `----

    3. The warning pertaining to defadvice has disappeared.

>         Stefan

bug#12965: 24.3.50; Suppress *Compile-log* buffer during init

[Stefan Monnier]

> Fixed.  The bug can be closed.

Thanks, done.

>     2. It contains a sole warning 

>         ,----
>         | elisp/bbdb-2.35/lisp/bbdb-com.elc:Warning: Use `with-current-buffer' rather
>         |     than save-excursion+set-buffer
>         `----

Until someone changes bytecomp.el to use `message' when compiling
a single function, you'll either have to live it or fix it on
BBDB's side.
BTW, you might like to upgrade to bbdb-3.


        Stefan