bug#19514: 25.0.50; byte-compile-file too tight-lipped

[Katsumi Yamaoka]

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.