From: Paul Eggert <eggert@cs.ucla.edu>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: 19514@debbugs.gnu.org
Subject: bug#19514: 25.0.50; byte-compile-file too tight-lipped
Date: Tue, 06 Jan 2015 23:04:04 -0800 [thread overview]
Message-ID: <54ACDA64.9090106@cs.ucla.edu> (raw)
In-Reply-To: <b4mh9w3tfut.fsf@jpl.org>
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).
next prev parent reply other threads:[~2015-01-07 7:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 11:10 bug#19514: 25.0.50; byte-compile-file too tight-lipped Katsumi Yamaoka
2015-01-06 23:30 ` Paul Eggert
2015-01-07 3:43 ` Katsumi Yamaoka
2015-01-07 7:04 ` Paul Eggert [this message]
2015-01-20 0:02 ` Katsumi Yamaoka
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54ACDA64.9090106@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=19514@debbugs.gnu.org \
--cc=yamaoka@jpl.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).