From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#20445: excessive redisplay / echo area resizing during byte-compilation Date: Wed, 29 Apr 2015 09:11:33 +0200 Message-ID: <55408425.5020409@gmx.at> References: <7cfv7lxnpr.fsf@fencepost.gnu.org> <83sibkuvze.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1430291544 1468 80.91.229.3 (29 Apr 2015 07:12:24 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 29 Apr 2015 07:12:24 +0000 (UTC) Cc: 20445@debbugs.gnu.org To: Stefan Monnier , Artur Malabarba Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Apr 29 09:12:13 2015 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YnMAF-00073z-OW for geb-bug-gnu-emacs@m.gmane.org; Wed, 29 Apr 2015 09:12:11 +0200 Original-Received: from localhost ([::1]:37332 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnMAE-000546-Tb for geb-bug-gnu-emacs@m.gmane.org; Wed, 29 Apr 2015 03:12:10 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34747) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnMAA-000517-GV for bug-gnu-emacs@gnu.org; Wed, 29 Apr 2015 03:12:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YnMA7-000239-AC for bug-gnu-emacs@gnu.org; Wed, 29 Apr 2015 03:12:06 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:45528) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YnMA7-000235-7m for bug-gnu-emacs@gnu.org; Wed, 29 Apr 2015 03:12:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1YnMA6-00084Q-WD for bug-gnu-emacs@gnu.org; Wed, 29 Apr 2015 03:12:03 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 29 Apr 2015 07:12:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 20445 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 20445-submit@debbugs.gnu.org id=B20445.143029150830994 (code B ref 20445); Wed, 29 Apr 2015 07:12:02 +0000 Original-Received: (at 20445) by debbugs.gnu.org; 29 Apr 2015 07:11:48 +0000 Original-Received: from localhost ([127.0.0.1]:55502 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1YnM9r-00083p-Lp for submit@debbugs.gnu.org; Wed, 29 Apr 2015 03:11:47 -0400 Original-Received: from mout.gmx.net ([212.227.15.18]:63073) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1YnM9q-00083a-8O for 20445@debbugs.gnu.org; Wed, 29 Apr 2015 03:11:46 -0400 Original-Received: from [93.82.73.211] ([93.82.73.211]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MKHtm-1Yp0Jg01bC-001mQl; Wed, 29 Apr 2015 09:11:38 +0200 In-Reply-To: X-Provags-ID: V03:K0:KBGj6BVQYY8UGiljW9rJNoWUWl8EvoxpknYOBZTy61lco9UU+IB Ga1KRWty7M9MJnPwXQllg150UDWiOO5O6liCD+neO+f7kJ70sDLj12bGOqxuWgdsQ2ty8Jz u39GKpbzI4HHvtB3aunVjL5Ly1wvGBRlOT5a1a+52q8xskPNls2Lk82ClFoJlOZn/bRTHaO STZdYrPRcQVUvmWI2N6Og== X-UI-Out-Filterresults: notjunk:1; X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:102207 Archived-At: > This is the problem: in order to "not emit a message" this code emits > the message and then immediately hides it by emitting "the empty > message" on top of it. > > Since `message' redisplays right away (rather than waiting for the next > "idle" moment to perform redisplay, as is the case for normal buffer > changes), this result in a lot of wasted work, and it won't truly do > what was intended: > - If your machine/display is slow enough, you will see it > - If your system "prints" messages by speaking them out loud (e.g. with > emacspeak) you will hear them. > > Why not just do: > > (when byte-compile--interactive > (apply #'message format args)) > > ? But if there are no errors this would not display a message at all with Glenn's scenario. IMHO `byte-compile--interactive' puts the cart before the horse. Rather, displaying messages should be the default and the caller should be able to suppress them via a `byte-compile--no-message' variable or something the like. So I'd instead use (unless byte-compile--no-message (apply #'message format args))) martin