From: martin rudalics <rudalics@gmx.at>
To: John Yates <john@yates-sheets.org>, Drew Adams <drew.adams@oracle.com>
Cc: Daniel Mendler <daniel@mendler.net>,
Daniel Mendler <mail@daniel-mendler.de>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>,
"monnier@iro.umontreal.ca" <monnier@iro.umontreal.ca>,
"kevin.legouguec@gmail.com" <kevin.legouguec@gmail.com>,
"acm@muc.de" <acm@muc.de>, Eli Zaretskii <eliz@gnu.org>,
"arstoffel@gmail.com" <arstoffel@gmail.com>
Subject: Re: [External] : Re: Indicate better the current use of the echo area / minibuffer [was: Controlling Isearch from minibuffer]
Date: Sat, 15 May 2021 09:57:15 +0200 [thread overview]
Message-ID: <32c5e3dc-31dd-2540-de1f-f5e4670d2510@gmx.at> (raw)
In-Reply-To: <CAJnXXoh5+pZ1L9yKXOrjJv+kEZO+8Gv3CWOay8eD7SqiKSnGMw@mail.gmail.com>
> I use a separate minibuffer frame. The idea is to
> have a one pixel frame inner border. The border
> changes from matching the background to some
> contrasting color when the minibuffer is active.
>
> I am not sure what the analog to the inner border
> should be for the non-separate minibuffer frame
> scenario.
There is none. The best solution I can think of is to tune the
minibuffer window's background.
martin
next prev parent reply other threads:[~2021-05-15 7:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 23:47 Indicate better the current use of the echo area / minibuffer [was: Controlling Isearch from minibuffer] Drew Adams
2021-05-13 6:28 ` Eli Zaretskii
2021-05-13 14:11 ` [External] : " Drew Adams
2021-05-13 14:41 ` Daniel Mendler
2021-05-13 15:24 ` Alan Mackenzie
2021-05-13 16:12 ` Daniel Mendler
2021-05-13 16:21 ` Augusto Stoffel
2021-05-13 16:44 ` Eli Zaretskii
2021-05-13 16:16 ` Daniel Martín
2021-05-13 16:33 ` Daniel Mendler
2021-05-13 17:41 ` Drew Adams
2021-05-13 18:07 ` Daniel Mendler
2021-05-13 19:36 ` Drew Adams
2021-05-14 21:02 ` John Yates
2021-05-14 21:55 ` Drew Adams
2021-05-15 7:57 ` martin rudalics [this message]
2021-05-15 19:46 ` Drew Adams
2021-05-14 18:16 ` Juri Linkov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=32c5e3dc-31dd-2540-de1f-f5e4670d2510@gmx.at \
--to=rudalics@gmx.at \
--cc=acm@muc.de \
--cc=arstoffel@gmail.com \
--cc=daniel@mendler.net \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=john@yates-sheets.org \
--cc=kevin.legouguec@gmail.com \
--cc=mail@daniel-mendler.de \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).