From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 20445@debbugs.gnu.org
Subject: bug#20445: excessive redisplay / echo area resizing during byte-compilation
Date: Tue, 28 Apr 2015 19:43:03 +0200 [thread overview]
Message-ID: <553FC6A7.5070600@gmx.at> (raw)
In-Reply-To: <83mw1suvkw.fsf@gnu.org>
> This effectively disables the log control executed via
> byte-compile--interactive. So the question is: how can we solve it
> without that adverse effect?
To solve the case at hand we could probably get away with something like
--- a/lisp/progmodes/elisp-mode.el
+++ b/lisp/progmodes/elisp-mode.el
@@ -181,7 +181,8 @@ All commands in `lisp-mode-shared-map' are inherited by this map.")
"Byte compile the file containing the current buffer."
(interactive)
(if buffer-file-name
- (byte-compile-file buffer-file-name)
+ (let ((byte-compile--interactive t))
+ (byte-compile-file buffer-file-name))
(error "The buffer must be saved in a file first")))
(defun emacs-lisp-byte-compile-and-load ()
But there might be lots of cases where `byte-compile-file' and friends
are called by a command.
martin
next prev parent reply other threads:[~2015-04-28 17:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 21:31 bug#20445: excessive redisplay / echo area resizing during byte-compilation Glenn Morris
2015-04-27 21:44 ` Glenn Morris
2015-04-28 9:33 ` martin rudalics
2015-04-28 14:26 ` martin rudalics
2015-04-28 15:22 ` Eli Zaretskii
2015-04-28 17:43 ` martin rudalics [this message]
2015-04-28 18:00 ` Eli Zaretskii
2015-04-29 7:11 ` martin rudalics
2015-04-28 15:13 ` Eli Zaretskii
2015-04-29 3:21 ` Stefan Monnier
2015-04-29 7:11 ` martin rudalics
2015-04-29 8:56 ` Artur Malabarba
2015-04-29 8:58 ` Artur Malabarba
2015-04-29 7:37 ` Artur Malabarba
2015-04-29 15:53 ` Eli Zaretskii
2015-04-29 18:35 ` Artur Malabarba
2015-04-29 18:52 ` Artur Malabarba
2015-05-01 10:41 ` martin rudalics
2015-05-01 12:20 ` Artur Malabarba
2015-05-01 13:45 ` martin rudalics
2015-05-01 14:19 ` Artur Malabarba
2015-05-01 16:28 ` Artur Malabarba
2015-05-02 8:58 ` martin rudalics
2015-05-01 10:41 ` martin rudalics
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=553FC6A7.5070600@gmx.at \
--to=rudalics@gmx.at \
--cc=20445@debbugs.gnu.org \
--cc=eliz@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.