GNU bug report logs -
#19514
25.0.50; byte-compile-file too tight-lipped
Previous Next
Reported by: Katsumi Yamaoka <yamaoka <at> jpl.org>
Date: Mon, 5 Jan 2015 11:11:02 UTC
Severity: normal
Found in version 25.0.50
Done: Katsumi Yamaoka <yamaoka <at> jpl.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
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).
This bug report was last modified 10 years and 182 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.