emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: mode-line-inactive and toggle-input-method


From: Al Petrofsky
Subject: Re: mode-line-inactive and toggle-input-method
Date: Wed, 27 Feb 2002 09:13:47 -0800

> From: address@hidden (Kim F. Storm)
> Al Petrofsky <address@hidden> 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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]