From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 49844@debbugs.gnu.org
Subject: bug#49844: Highlight non-selected minibuffer prompt
Date: Sun, 07 Nov 2021 19:31:25 +0200 [thread overview]
Message-ID: <868ry0jf16.fsf@mail.linkov.net> (raw)
In-Reply-To: <8735o9t29l.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 06 Nov 2021 22:14:46 +0100")
>> ISTR, in bug#50141 we decided to add more generalized code to windmove.el
>> that will provide 4 customizable types of window backgrounds colors
>> with different faces:
>>
>> 1. selected window
>> 2. non-selected window
>> 3. selected minibuffer window
>> 4. non-selected minibuffer window
>
> But... isn't think pretty much unrelated to windmove, too? I'd just
> like to have the minibuffer light up when I've moved point somewhere
> else (because it can be confusing sometimes).
This was intended to address different requests. So far the requests
were: to highlight the background of the selected window, to highlight
the selected minibuffer window, and to highlight the non-selected
active minibuffer. The last case actually is more complex:
the non-selected minibuffer should not be highlighted
when the Completions window is selected. Only after moving point
out of both the minibuffer and the Completions window, the minibuffer
window should be highlighted.
next prev parent reply other threads:[~2021-11-07 17:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 7:47 bug#49844: Highlight non-selected minibuffer prompt Juri Linkov
2021-08-04 7:42 ` Lars Ingebrigtsen
2021-08-04 8:41 ` Juri Linkov
2021-08-04 8:53 ` Lars Ingebrigtsen
2021-08-04 21:32 ` Juri Linkov
2021-08-05 5:53 ` Eli Zaretskii
2021-08-05 11:00 ` Lars Ingebrigtsen
2021-11-06 2:41 ` Lars Ingebrigtsen
2021-11-06 2:42 ` Lars Ingebrigtsen
2021-11-06 18:43 ` Juri Linkov
2021-11-06 21:14 ` Lars Ingebrigtsen
2021-11-07 17:31 ` Juri Linkov [this message]
2022-08-22 11:04 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=868ry0jf16.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=49844@debbugs.gnu.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.