From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Intelligent stacking of messages in the echo area Date: Wed, 25 Dec 2019 02:15:59 +0200 Organization: LINKOV.NET Message-ID: <875zi5ntts.fsf@mail.linkov.net> References: <87sgldfi9j.fsf@mail.linkov.net> <878sn3g0o7.fsf@gmail.com> <87pngepti3.fsf@mail.linkov.net> <87mubidptp.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="182846"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (x86_64-pc-linux-gnu) Cc: ndame , "emacs-devel@gnu.org" To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 25 03:14:50 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1ijwCI-000lTY-4o for ged-emacs-devel@m.gmane.org; Wed, 25 Dec 2019 03:14:50 +0100 Original-Received: from localhost ([::1]:43180 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ijwCG-0000N1-29 for ged-emacs-devel@m.gmane.org; Tue, 24 Dec 2019 21:14:48 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37982) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ijwCA-0000Mv-Bf for emacs-devel@gnu.org; Tue, 24 Dec 2019 21:14:43 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ijwC8-0006uC-Pn for emacs-devel@gnu.org; Tue, 24 Dec 2019 21:14:42 -0500 Original-Received: from crocodile.birch.relay.mailchannels.net ([23.83.209.45]:1824) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ijwC8-0006t8-Gm for emacs-devel@gnu.org; Tue, 24 Dec 2019 21:14:40 -0500 X-Sender-Id: dreamhost|x-authsender|jurta@jurta.org Original-Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 158D26007C3; Wed, 25 Dec 2019 02:14:38 +0000 (UTC) Original-Received: from pdx1-sub0-mail-a50.g.dreamhost.com (100-96-206-11.trex.outbound.svc.cluster.local [100.96.206.11]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id A44716009F3; Wed, 25 Dec 2019 02:14:37 +0000 (UTC) X-Sender-Id: dreamhost|x-authsender|jurta@jurta.org Original-Received: from pdx1-sub0-mail-a50.g.dreamhost.com ([TEMPUNAVAIL]. [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.5); Wed, 25 Dec 2019 02:14:38 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: dreamhost|x-authsender|jurta@jurta.org X-MailChannels-Auth-Id: dreamhost X-Bitter-Macabre: 3a6b04a1719fb237_1577240077901_883165523 X-MC-Loop-Signature: 1577240077901:621916978 X-MC-Ingress-Time: 1577240077901 Original-Received: from pdx1-sub0-mail-a50.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a50.g.dreamhost.com (Postfix) with ESMTP id BB8ED7F07C; Tue, 24 Dec 2019 18:14:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=linkov.net; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=linkov.net; bh=6HL8VcDzR1pCqvib2lq+49PgBmA=; b= XLHJiUOaNlWEzrjVq9j2YAjMCNJ1Dy2f0auFUSlfKuHQ31W5wN4dBpgeDzJJEabb XwRChNGlYCTpv4KXoopU8S1jd+uBbquQkuq1mgRYTQs2yvzQs0zNmo3saX2Tane7 eOCAZYonPKrY7j+ExT/sCWMgdUs56hVp4vfbwWOxdBo= Original-Received: from mail.jurta.org (m91-129-107-186.cust.tele2.ee [91.129.107.186]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: jurta@jurta.org) by pdx1-sub0-mail-a50.g.dreamhost.com (Postfix) with ESMTPSA id 5C6157F078; Tue, 24 Dec 2019 18:14:30 -0800 (PST) X-DH-BACKEND: pdx1-sub0-mail-a50 In-Reply-To: <87mubidptp.fsf@localhost> (Ihor Radchenko's message of "Tue, 24 Dec 2019 17:40:18 +0800") X-VR-OUT-STATUS: OK X-VR-OUT-SCORE: 0 X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedufedrvddvvddgudeglecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucggtfgfnhhsuhgsshgtrhhisggvpdfftffgtefojffquffvnecuuegrihhlohhuthemuceftddtnecunecujfgurhephffvufhofhffjgfkfgggtgesthdtredttdertdenucfhrhhomheplfhurhhiucfnihhnkhhovhcuoehjuhhriheslhhinhhkohhvrdhnvghtqeenucfkphepledurdduvdelrddutdejrddukeeinecurfgrrhgrmhepmhhouggvpehsmhhtphdphhgvlhhopehmrghilhdrjhhurhhtrgdrohhrghdpihhnvghtpeeluddruddvledruddtjedrudekiedprhgvthhurhhnqdhprghthheplfhurhhiucfnihhnkhhovhcuoehjuhhriheslhhinhhkohhvrdhnvghtqedpmhgrihhlfhhrohhmpehjuhhriheslhhinhhkohhvrdhnvghtpdhnrhgtphhtthhopeihrghnthgrrhelvdesghhmrghilhdrtghomhenucevlhhushhtvghrufhiiigvpedv X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 23.83.209.45 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:243621 Archived-At: > I was testing the code for a while. > There seem to be one irritating (for me) problem with the way > set-message-function is implemented. > When I run a command changing current buffer and emitting multiple > messages, emacs frame is redrawn every time a new message comes out. > Specifically, I was running org-capture, which changes windows > configuration, switches to different buffer, and emits multiple messages > while running. Normally, it runs very fast (the capture template I used > does not require any user input), but with multi-message, I can see the > frame being redrawn on every new message popping up. Since window > configuration is different, full redraw is forced and the whole > org-capture runs a lot slower. Maybe this is because multi-line messages resize the echo-area window every time a new message line is added (when resize-mini-windows is non-nil), so height changes of the echo-area window invoke window-configuration-change-hook. It seems the same problem existed for a long time, but had no noticeable effect because multi-line messages were rare. Now for the multi-message feature where multi-line messages are not an exception but a rule, one way to mitigate it is to use a message separator other than a newline, e.g. (setq multi-message-separator (propertize ";" 'face 'minibuffer-prompt)) In a wide frame, one echo-area line can accommodate several short messages without resizing the echo-area window.