From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Marcin Borkowski Newsgroups: gmane.emacs.devel Subject: Re: Intelligent stacking of messages in the echo area Date: Sat, 31 Aug 2019 11:46:46 +0200 Message-ID: <87r251u0op.fsf@mbork.pl> References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="261564"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: mu4e 1.1.0; emacs 27.0.50 Cc: "emacs-devel@gnu.org" To: ndame Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Aug 31 11:47:12 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 1i3zyS-0015vF-D5 for ged-emacs-devel@m.gmane.org; Sat, 31 Aug 2019 11:47:12 +0200 Original-Received: from localhost ([::1]:43766 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i3zyQ-0001av-NK for ged-emacs-devel@m.gmane.org; Sat, 31 Aug 2019 05:47:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58422) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i3zyK-0001ao-4J for emacs-devel@gnu.org; Sat, 31 Aug 2019 05:47:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i3zyI-0007HM-T5 for emacs-devel@gnu.org; Sat, 31 Aug 2019 05:47:03 -0400 Original-Received: from mail.mojserwer.eu ([195.110.48.8]:57928) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1i3zyI-00073k-MC for emacs-devel@gnu.org; Sat, 31 Aug 2019 05:47:02 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by mail.mojserwer.eu (Postfix) with ESMTP id 31F65E6700; Sat, 31 Aug 2019 11:46:54 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mail.mojserwer.eu Original-Received: from mail.mojserwer.eu ([127.0.0.1]) by localhost (mail.mojserwer.eu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KwmV2_nCeuEW; Sat, 31 Aug 2019 11:46:50 +0200 (CEST) Original-Received: from localhost (jeden09-dwa27.echostar.pl [213.156.109.227]) by mail.mojserwer.eu (Postfix) with ESMTPSA id 1781AE6322; Sat, 31 Aug 2019 11:46:50 +0200 (CEST) In-reply-to: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.110.48.8 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:239720 Archived-At: Before Emacs learns to do what you want, how about a workaround? See http://mbork.pl/2017-05-01_show-some-last-messages (and the comment, which apperently I forgot to answer - sorry for that). Hth, mb On 2019-08-31, at 07:35, ndame wrote: > If two or more packages use the echo area for informational messages > then often they fight each other, overwriting each other's messages. > > For example, in lisp mode eldoc is automatically enabled in my emacs > 26.2 If I also turn on a paren mode which shows in the message area > the matching part of a paren outside of the screen then eldoc often > overwrites this message with its own documentation message. > > Other systems solve this by stacking messages on top of each other: > > https://www.howtogeek.com/wp-content/uploads/2014/11/ximg_54669cfe004ae.jpg.pagespeed.gp+jp+jw+pj+js+rj+rp+rw+ri+cp+md.ic.iDwLFdLQh5.jpg > > Maybe the echo area could be smarter and stack messages on top of each > other if they come from diferent sources and they are close to each > other in time. > > So in case of the above example, if a message comes from eldoc and > parens at the same time in quick succession then the echo area could > show both of them in two lines. > > And if the same source is sending multiple messsages or there is > enough delay between two messages from different sources (e.g. 1-2 > seconds) then it would work as today using only a single line. -- Marcin Borkowski http://mbork.pl