From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: Where to show message output while inputting [was: New multi-command facility displays in the wrong echo area] Date: Tue, 13 Oct 2020 19:42:28 +0000 Message-ID: References: <5f7af512-7951-4e10-a8a1-4f5d07ee6cda@default> Reply-To: Gregory Heytings Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32258"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Alpine 2.22 (NEB 394 2020-01-19) Cc: Eli Zaretskii , acm@muc.de, juri@linkov.net, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Oct 13 21:44:19 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kSQDa-0008Iv-Hr for ged-emacs-devel@m.gmane-mx.org; Tue, 13 Oct 2020 21:44:18 +0200 Original-Received: from localhost ([::1]:59352 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kSQDZ-0001Ru-JM for ged-emacs-devel@m.gmane-mx.org; Tue, 13 Oct 2020 15:44:17 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43878) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kSQBx-00009y-F5 for emacs-devel@gnu.org; Tue, 13 Oct 2020 15:42:37 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:60293) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kSQBv-0002da-5u; Tue, 13 Oct 2020 15:42:37 -0400 Original-Received: from sdf.org (IDENT:ghe@faeroes.freeshell.org [205.166.94.9]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 09DJgUmx006300 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Tue, 13 Oct 2020 19:42:31 GMT Original-Received: (from ghe@localhost) by sdf.org (8.15.2/8.12.8/Submit) id 09DJgr0Y008234; Tue, 13 Oct 2020 19:42:53 GMT In-Reply-To: <5f7af512-7951-4e10-a8a1-4f5d07ee6cda@default> Received-SPF: pass client-ip=205.166.94.24; envelope-from=ghe@sdf.org; helo=mx.sdf.org X-detected-operating-system: by eggs.gnu.org: First seen = 2020/10/13 15:22:16 X-ACL-Warn: Detected OS = ??? X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:257571 Archived-At: > > The same problem will exist if you move output (`message' echoes) to the > mode-line: you won't be able to see the mode-line info and the message > at the same time. > That's obviously a problem that will exist in any possible solution to that problem: the message will hide something. The question is then: what is the "something" that can be hidden with the least possible risk? IMO the mode-line is, in this context, the least important element, and it can be temporarily right-shifted. Eldoc does this, too. > > Or we could choose to echo in a separate area only when needed. E.g., > we might use the same area for echo and minibuffer whenever there's no > conflict (no overlap in time), and show echoes in some other place (e.g. > pop-up) in the rarer cases when needed. > That's exactly what my proposed solution does. The same area is used when there's no conflict, and the "pop-up" uses the space on the left of the mode-line, which is temporarily right-shifted. > > "Pop up" here could mean temporarily overwriting the mode-line, as > Gregory suggested. > No, the mode-line is not temporarily overwritten, it is temporarily right-shifted. Usually (when the message is not too long) the leftmost part of the mode-line remains visible.