From: Daniel Mendler <mail@daniel-mendler.de>
To: Drew Adams <drew.adams@oracle.com>,
Daniel Mendler <daniel@mendler.net>, Eli Zaretskii <eliz@gnu.org>
Cc: "acm@muc.de" <acm@muc.de>,
"kevin.legouguec@gmail.com" <kevin.legouguec@gmail.com>,
"arstoffel@gmail.com" <arstoffel@gmail.com>,
"monnier@iro.umontreal.ca" <monnier@iro.umontreal.ca>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: [External] : Re: Indicate better the current use of the echo area / minibuffer [was: Controlling Isearch from minibuffer]
Date: Thu, 13 May 2021 20:07:30 +0200 [thread overview]
Message-ID: <79b1d1e6-e530-d4b4-cdde-a98b2dda3f60@daniel-mendler.de> (raw)
In-Reply-To: <SA2PR10MB447433527D5E40837374978FF3519@SA2PR10MB4474.namprd10.prod.outlook.com>
On 5/13/21 7:41 PM, Drew Adams wrote:
> It seems that this thread has been knee-jerk
> hijacked by those intent on pushing a proposal to
> base Isearch on the minibuffer.
>
> That's NOT the intention of this thread.
> There's another thread for that - please go there
> for that.
>
> This thread is about the current (longstanding)
> design of Isearch, which is NOT minibuffer-based.
>
> And it's also about the echo area and minibuffer
> (independently of any concern with Isearch).
Of course, my intention was to hijack "your" thread.
Just to make it clear - my mail is related to your colorful
echo/minibuffer proposal as follows: If Isearch would not use the echo
area as it currently does, there would not even exist a need for an
indicator to make anything more clear.
But please tell me about the different indication modes you have
implemented in your packages. You have a color for the minibuffer and a
color if Isearch is active? Then you change color based on the recursion
level. Are there indicators for other states?
I have written a tiny package, which displays a "recursion indicator" in
the mode line: https://github.com/minad/recursion-indicator. Currently
it displays an arrow per recursion level and a special symbol if a
recursive minibuffer session is active. It makes sense to extend this
with more states, like Isearch. For Isearch I am using a separate
indicator in the mode line:
~~~
(defvar isearch-indicator
(concat (propertize "Isearch" 'face 'isearch)))
(add-hook 'isearch-mode-hook
(lambda ()
(push isearch-indicator mode-line-misc-info)))
(add-hook 'isearch-mode-end-hook
(lambda ()
(setq mode-line-misc-info
(delq isearch-indicator mode-line-misc-info))))
~~~
Daniel
next prev parent reply other threads:[~2021-05-13 18:07 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 [this message]
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
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=79b1d1e6-e530-d4b4-cdde-a98b2dda3f60@daniel-mendler.de \
--to=mail@daniel-mendler.de \
--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=kevin.legouguec@gmail.com \
--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).