unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Daniel Martín" <mardani29@yahoo.es>
To: Daniel Mendler <daniel@mendler.net>
Cc: Drew Adams <drew.adams@oracle.com>,  Eli Zaretskii <eliz@gnu.org>,
	"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 18:16:23 +0200	[thread overview]
Message-ID: <m1o8dey5go.fsf@yahoo.es> (raw)
In-Reply-To: <61c85b87-98f2-1fa2-4e0a-aba40b080049@mendler.net> (Daniel Mendler's message of "Thu, 13 May 2021 16:41:10 +0200")

Daniel Mendler <daniel@mendler.net> writes:

>
> The echo area/minibuffer distinction comes up from time to time in
> discussions with new users. I know that I had been confused for a while
> with the Isearch behavior. The Isearch use of the echo area is
> unexpected. Users expect to enter a search string into a separate input
> form as is common in many other programs. In Emacs this input form is
> the minibuffer.

It's unexpected if you come from other applications, but I don't think
it's a bad UX.  Once you get used to how Isearch works, in my opinion
it's much more efficient than using the minibuffer.  For example, it's
very common to use incremental search to navigate to a particular place
in a buffer, and, once you are in the desired position, do something
like C-n, C-v, or C-p to move the point further and end the search at
the same time.  This use case wouldn't be as convenient if incremental
search used the minibuffer.  Try it in the CtrlF package, for example.

>
> I would welcome the changes by Augusto. The minibuffer-controlled
> Isearch makes entering the search string more robust with regards to
> various editing commands as mentioned before by Kévin Le Gouguec.
>

I wouldn't like them.  If you want to edit the search string, you can
just 'M-e' or click on the echo area.  You can also type 'C-M-d' to
delete individual characters, instead of using 'backspace'.

> There exists the ctrlf package on MELPA which also uses the minibuffer,
> but it feels hardly justified to install an extra package only to get a
> minibuffer-controlled search mode. I also don't want to replace such a
> tightly integrated component like Isearch with an external package. If a
> minibuffer mode can be added to Isearch with small effort and in a
> reasonably clean way, why not do that?
>

That's the problem.  Given the amount of subtle use cases currently
supported by Isearch, I think that even adding a separate option to use
the minibuffer would not be a simple implementation (for example, you
can perform an incremental search in the minibuffer itself, etc.).

To be fair, I see some good things about using the minibuffer (for
example, it'd be simpler to perform certain actions, like scrolling the
window, without exiting the search), but all the things that we'll lose
or will change don't quite justify the new feature, IMHO.



  parent reply	other threads:[~2021-05-13 16:16 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 [this message]
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
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=m1o8dey5go.fsf@yahoo.es \
    --to=mardani29@yahoo.es \
    --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).