GNU bug report logs - #19514
25.0.50; byte-compile-file too tight-lipped

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 19514 in the body.
You can then email your comments to 19514 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Katsumi Yamaoka <yamaoka <at> jpl.org>
To: bug-gnu-emacs <at> gnu.org
Subject: 25.0.50; byte-compile-file too tight-lipped
Date: Mon, 05 Jan 2015 20:10:33 +0900

Hi,

The byte compiler is now too quiet if it runs in the batch mode.
For instance, this is what I got when compiling Ma Gnus:

[...]
lispdir="/usr/local/share/emacs/25.0.50/site-lisp/gnus" srcdir=. emacs-25.0.50 -batch -q -no-site-file -l /usr/local/share/emacs/site-lisp/no-site-lisp.el -l ./dgnushack.el -f dgnushack-compile
No MH variant found on the system
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
Warning: Using brain-dead macro `mm-with-unibyte-current-buffer'!
[...]

I cannot see what Lisp modules are blamed.  This seems to be due
to the recent change <cd2d58c1c81d608d6e1aefe1eb8a3d1f1cd60540>.

Thanks.

In GNU Emacs 25.0.50.1 (i686-pc-cygwin, GTK+ Version 3.10.9)
 of 2015-01-05 on localhost
Windowing system distributor `The Cygwin/X Project', version 11.0.11501000
Configured using:
 `configure --verbose --with-x-toolkit=gtk3'

Message #8 received at 19514 <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Katsumi Yamaoka <yamaoka <at> jpl.org>
Cc: 19514 <at> debbugs.gnu.org
Subject: Re: 25.0.50; byte-compile-file too tight-lipped
Date: Tue, 06 Jan 2015 15:30:51 -0800

[Message part 1 (text/plain, inline)]

Hmm, well, dgnushack shouldn't rely on byte-compile-file outputting 
messages when not verbose.  One way to fix this is for dgnushack to set 
byte-compile-verbose, but that might make dgnushack *too* verbose.  So 
how about the attached patch to dgnushack instead?

[gnus.diff (text/x-patch, attachment)]

Message #11 received at 19514 <at> debbugs.gnu.org (full text, mbox):

From: Katsumi Yamaoka <yamaoka <at> jpl.org>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 19514 <at> debbugs.gnu.org
Subject: Re: 25.0.50; byte-compile-file too tight-lipped
Date: Wed, 07 Jan 2015 12:43:54 +0900

On Tue, 06 Jan 2015 15:30:51 -0800, Paul Eggert wrote:
> Hmm, well, dgnushack shouldn't rely on byte-compile-file outputting
> messages when not verbose.  One way to fix this is for dgnushack to
> set byte-compile-verbose, but that might make dgnushack *too* verbose.
> So how about the attached patch to dgnushack instead?

[...]
> +(defun dgnushack-compile-file (file)
> +  "Byte-compile FILE after reporting that it's being compiled."
> +  (message "Compiling %s..." file)
> +  (byte-compile-file file))
[...]

It will work.  Thanks.  But should every Lisp package, that uses
byte-compile-file, have such one in its install program?
Even if a Lisp package is perfect and issues no warning (the CVS
HEAD of emacs-w3m is it), the installer had better say at least
"Wrote xxx.elc" rather than no message is displayed for a couple
of ten seconds, I think.  How about this?

(defvar byte-compile-silent nil
  "*If non-nil, byte-compiler issues no verbose message in the batch mode.")

I hope it defaults to nil, i.e. the default behavior is unchanged.

Message #14 received at 19514 <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Katsumi Yamaoka <yamaoka <at> jpl.org>
Cc: 19514 <at> debbugs.gnu.org
Subject: Re: 25.0.50; byte-compile-file too tight-lipped
Date: Tue, 06 Jan 2015 23:04:04 -0800

Katsumi Yamaoka wrote:
> How about this?
>
> (defvar byte-compile-silent nil
>    "*If non-nil, byte-compiler issues no verbose message in the batch mode.")

That would be doable, but the value of doing it seems limited, as the caller of 
byte-compile-file can easily write the message itself.  This distinguishes it 
from byte-compile-verbose, which cannot be easily implemented by a wrapper.

Furthermore, the old behavior was not good.  First one saw the error messages 
from compiling FOO.  Then one saw the message saying that FOO was compiled. 
That's backwards and confusing.

So I'd prefer fixing dgnushack to generate better output.  Similarly for any 
other callers relying on the old "Wrote" message (my impression is that most 
callers won't care).

Message #19 received at 19514-done <at> debbugs.gnu.org (full text, mbox):

From: Katsumi Yamaoka <yamaoka <at> jpl.org>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 19514-done <at> debbugs.gnu.org
Subject: Re: 25.0.50; byte-compile-file too tight-lipped
Date: Tue, 20 Jan 2015 09:02:07 +0900

I've installed your `dgnushack-compile-file' for only GNU Emacs
after all.  Thanks.

<http://article.gmane.org/gmane.emacs.gnus.cvs/12738>

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.