all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: "61601@debbugs.gnu.org" <61601@debbugs.gnu.org>,
	Eli Zaretskii <eliz@gnu.org>, Juri Linkov <juri@linkov.net>
Subject: bug#61601: [PATCH] * lisp/isearch.el (minibuffer-lazy-highlight-setup): Use cursor-in-echo-area
Date: Sun, 19 Feb 2023 15:53:42 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488A58052F663F2FE25C3A5F3A79@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87zg99x33v.fsf@gmail.com>

> > No such problems existed before Isearch started
> > using the minibuffer instead of the echo area.
> 
> AFAICT C-M-% always used the minibuffer to read a regular expression.
> This has nothing to do with Isearch per se.

If this is only about C-M-% reading a regexp
then OK, and I apologize for not having read
more of the thread.

C-M-%'s reading of a regexp is an all-at-once,
one time reading that uses the minibuffer.

That reading has nothing to do with Isearch's
reading of keys you type, for incremental
input and editing of the search pattern.  

_If_ this is about Isearch's incremental
handling of a search pattern, then maybe my
comment is relevant.  Apart from `M-e', since
Day One Isearch always read input directly,
not using the minibuffer.  It displayed what
you typed in the echo area, giving somewhat
the (mistaken) impression that input was in
the minibuffer.





  reply	other threads:[~2023-02-19 15:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-18 11:30 bug#61601: [PATCH] * lisp/isearch.el (minibuffer-lazy-highlight-setup): Use cursor-in-echo-area Augusto Stoffel
2023-02-18 18:44 ` Juri Linkov
2023-02-18 19:05   ` Augusto Stoffel
2023-02-18 19:18   ` Eli Zaretskii
2023-02-18 21:40     ` Augusto Stoffel
2023-02-18 22:43       ` Drew Adams
2023-02-19 12:16         ` Augusto Stoffel
2023-02-19 15:53           ` Drew Adams [this message]
2023-02-19  6:16       ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=SJ0PR10MB5488A58052F663F2FE25C3A5F3A79@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=61601@debbugs.gnu.org \
    --cc=arstoffel@gmail.com \
    --cc=eliz@gnu.org \
    --cc=juri@linkov.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.