unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 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 17:41:51 +0000	[thread overview]
Message-ID: <SA2PR10MB447433527D5E40837374978FF3519@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <61c85b87-98f2-1fa2-4e0a-aba40b080049@mendler.net>

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).

Minibuffer, echo area, and Isearch pattern share
the same screen area.  This thread is about
helping users more easily distinguish the current
state of that area.

[Those insistent on a minibuffer-based Isearch
have been the first to clamor about how confusing
it can be, especially for newbies, that Isearch
doesn't use the minibuffer but it uses the same
screen area.  Where are your voices on this other,
very different question about trying to prevent
or reduce such confusion?]

And of course this feature would be _optional_.
So comments like this one are irrelevant in this
context:

 > Personally, I would not like to use such a
 > colorful "subtle" indication in the echo area. 

That user Jane or Jim might not want any help with
this problem isn't a problem for anyone - they just
wouldn't turn it on.

This isn't about what _you_ might like as a user.
It's about how we might help other users - users in
general.

So far, alas, that comment is the only contribution
to this thread that's been (somewhat) on-topic.  The
rest has all been noise about why we should base
Isearch on the minibuffer.  And Eli has already said
that if _that_ were to be offered it would anyway be
optional for users.  So this problem remains for
Isearch as we've come to know and love it.

How about some ideas for making the state of this
shared screen area more clear to users?

All I've suggested in that regard is that I think a
visual, continuing indication, right there, _in that
area_ is what's called for.  (As opposed to some
ephemeral message, ding, or flash.)

That's my suggestion on the blue-sky whiteboard.
Anyone else have a suggestion?

  parent reply	other threads:[~2021-05-13 17:41 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 [this message]
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
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=SA2PR10MB447433527D5E40837374978FF3519@SA2PR10MB4474.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=acm@muc.de \
    --cc=arstoffel@gmail.com \
    --cc=daniel@mendler.net \
    --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).