unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: daniel@mendler.net, emacs-devel@gnu.org,
	monnier@iro.umontreal.ca, kevin.legouguec@gmail.com,
	arstoffel@gmail.com, drew.adams@oracle.com
Subject: Re: [External] : Re: Indicate better the current use of the echo area / minibuffer [was: Controlling Isearch from minibuffer]
Date: Thu, 13 May 2021 19:44:00 +0300	[thread overview]
Message-ID: <838s4i1t4f.fsf@gnu.org> (raw)
In-Reply-To: <YJ1Ep1JIP0gA/635@ACM> (message from Alan Mackenzie on Thu, 13 May 2021 15:24:23 +0000)

> Date: Thu, 13 May 2021 15:24:23 +0000
> From: Alan Mackenzie <acm@muc.de>
> Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>,
>  "monnier@iro.umontreal.ca" <monnier@iro.umontreal.ca>,
>  "kevin.legouguec@gmail.com" <kevin.legouguec@gmail.com>,
>  Eli Zaretskii <eliz@gnu.org>, "arstoffel@gmail.com" <arstoffel@gmail.com>,
>  Drew Adams <drew.adams@oracle.com>
> 
> > 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.
> 
> That's a rather misleading way of portraying it.  Users used to other
> programs tend not to be familiar with incremental search, where point is
> not in "a separate input form" but in the buffer they're searching
> through.  There is no "separate input form".

That was true some years ago, but no longer is.  Many other editors
and browsers support incremental search nowadays, and at least some of
them, mostly browsers, indeed expect you to type into a special input
widget.

> I am worried that these suggestions for using the minibuffer will get
> implemented, and searching in Emacs will move from the delightfully
> lightweight feature we have at the moment to something awkward and
> sluggish, like most other programs' searching is.

This alternative UI might indeed be added some day, but only as one
option, and most probably not the default.  So don't you worry.



  parent reply	other threads:[~2021-05-13 16:44 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 [this message]
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
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=838s4i1t4f.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=acm@muc.de \
    --cc=arstoffel@gmail.com \
    --cc=daniel@mendler.net \
    --cc=drew.adams@oracle.com \
    --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).