unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Augusto Stoffel <arstoffel@gmail.com>
To: Drew Adams <drew.adams@oracle.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 13:16:04 +0100	[thread overview]
Message-ID: <87zg99x33v.fsf@gmail.com> (raw)
In-Reply-To: <SJ0PR10MB54881636D1CBE79D1AC9A403F3A69@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Sat, 18 Feb 2023 22:43:14 +0000")

On Sat, 18 Feb 2023 at 22:43, Drew Adams wrote:

>> The flickering happens because the cursor briefly moves from the
>> minibuffer to the minibuffer selected window when the lazy highlighting
>> is done (e.g. after typing a character in the C-M-% regexp query).
>
> FWIW -
> 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.

Also, in isearch I still see cursor flickering when I type fast enough.
But since I normally use isearch-mb, which is not affected by this, I
can't describe the problem in more detail.





  reply	other threads:[~2023-02-19 12:16 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 [this message]
2023-02-19 15:53           ` Drew Adams
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

  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=87zg99x33v.fsf@gmail.com \
    --to=arstoffel@gmail.com \
    --cc=61601@debbugs.gnu.org \
    --cc=drew.adams@oracle.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 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).