From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Highlight non-selected minibuffer prompt Date: Sat, 31 Jul 2021 23:58:53 +0300 Organization: LINKOV.NET Message-ID: <87wnp6jk0y.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="12412"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (x86_64-pc-linux-gnu) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Aug 01 00:10:53 2021 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 1m9xC1-00035Q-6c for ged-emacs-devel@m.gmane-mx.org; Sun, 01 Aug 2021 00:10:53 +0200 Original-Received: from localhost ([::1]:43204 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m9xBz-0006zI-6B for ged-emacs-devel@m.gmane-mx.org; Sat, 31 Jul 2021 18:10:51 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42416) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m9xBF-0006Ja-MW for emacs-devel@gnu.org; Sat, 31 Jul 2021 18:10:05 -0400 Original-Received: from relay8-d.mail.gandi.net ([217.70.183.201]:35881) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m9xBD-00083j-KA for emacs-devel@gnu.org; Sat, 31 Jul 2021 18:10:05 -0400 Original-Received: (Authenticated sender: juri@linkov.net) by relay8-d.mail.gandi.net (Postfix) with ESMTPSA id 96B1F1BF208 for ; Sat, 31 Jul 2021 22:09:58 +0000 (UTC) Received-SPF: pass client-ip=217.70.183.201; envelope-from=juri@linkov.net; helo=relay8-d.mail.gandi.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=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:271906 Archived-At: Only today I realized how to address the long-standing complaint that sometimes accidentally switching from the minibuffer (that e.g. asks a yes/no question) remains unnoticed that leaves the minibuffer active for a long time. The solution was already invented long ago by minibuffer-depth-indicate-mode that highlights the recursive minibuffer with the minibuffer-depth-indicator face. The same solution could be used to add a highlighting to the minibuffer prompt after switching from the minibuffer that still remains active, thus turning the attention to a possible problem. I still have no idea where to implement this feature. Maybe in the same package mb-depth.el? Then should it be a separate mode or better to handle by a new option in the same minibuffer-depth-indicate-mode? Should it reuse the same minibuffer-depth-indicator face or add a new one?