From mboxrd@z Thu Jan 1 00:00:00 1970 Path: quimby.gnus.org!not-for-mail From: Al Petrofsky Newsgroups: gmane.emacs.devel Subject: Re: mode-line-inactive and toggle-input-method Date: Wed, 27 Feb 2002 09:13:47 -0800 Message-ID: <200202271713.JAA12395@radish.petrofsky.org> References: <1438-Sat16Feb2002104635+0200-eliz@is.elta.co.il> <200202171648.g1HGmup10311@aztec.santafe.edu> <5x7koz96o6.fsf@kfs2.cua.dk> <200202270013.QAA10950@radish.petrofsky.org> <5xit8jutxn.fsf@kfs2.cua.dk> NNTP-Posting-Host: quimby2.netfonds.no X-Trace: quimby2.netfonds.no 1014830368 10705 195.204.10.66 (27 Feb 2002 17:19:28 GMT) X-Complaints-To: usenet@quimby2.netfonds.no NNTP-Posting-Date: 27 Feb 2002 17:19:28 GMT Cc: emacs-devel@gnu.org Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby2.netfonds.no with esmtp (Exim 3.12 #1 (Debian)) id 16g7jj-0002mZ-00 for ; Wed, 27 Feb 2002 18:19:28 +0100 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.33 #1 (Debian)) id 16g7fn-000591-00; Wed, 27 Feb 2002 12:15:23 -0500 Original-Received: from radish.petrofsky.org ([216.240.48.33]) by fencepost.gnu.org with esmtp (Exim 3.33 #1 (Debian)) id 16g7eI-000534-00 for ; Wed, 27 Feb 2002 12:13:50 -0500 Original-Received: (from al@localhost) by radish.petrofsky.org (8.9.3/8.9.3/Debian 8.9.3-21) id JAA12395; Wed, 27 Feb 2002 09:13:47 -0800 Original-To: storm@cua.dk In-reply-to: <5xit8jutxn.fsf@kfs2.cua.dk> (storm@cua.dk) Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: quimby.gnus.org gmane.emacs.devel:1603 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:1603 > From: storm@cua.dk (Kim F. Storm) > Al Petrofsky writes: > > Why the inconsistency for minibuffer entry from the miniwindow? I > > would find it more informative for all mode-lines to go inactive to > > indicate that this has happened. I sometimes accidentally hit M-x > > twice in a row. It would be useful to have immediate feedback that > > this has happened. > > The problem that was reported was related to doing "trivial" commands > like C-u C-\ in the minibuffer would turn off the mode line indication > of the selected window. That is confusing. Confusion is in the eye of the beholder, but personally, I really don't see it that way. If you do C-u C-\ from an ordinary window, then you are setting the input method for the buffer in that window, and there's sense in keeping the window highlighted as if it were selected. But if you do C-u C-\ from the minibuffer, you are setting the minibuffer's input method. This is much less related to the original window. > As you say, it may be equally confusing that this doesn't happen > if you accidentally hit M-x twice in a row. > > I don't know how to solve this. Any ideas? > > We could handle M-x specially, i.e. if this-command is > execute-extended-command and we enter from the minibuffer, then > Vminibuf_selected_window should be set to nil. But that's a hack! Ordinarily, minibuffer activation from the minibuffer only occurs if the user has set enable-recursive-minibuffers, which is proof of his enlightenment, so clearly the more useful and consistent behavior is what's appropriate. The hack here is that read-input-method-name overrides enable-recursive-minibuffers. If you really think that it should override consistent mode-line highlighting as well, then that is the place to do it (but please, only do so if the user-set value of enable-recursive-minibuffers is nil). -al _______________________________________________ Emacs-devel mailing list Emacs-devel@gnu.org http://mail.gnu.org/mailman/listinfo/emacs-devel