From: Eli Zaretskii <eliz@gnu.org>
To: "Daniel Martín" <mardani29@yahoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: Handling of [mouse-movement] and exiting isearch
Date: Fri, 13 Nov 2020 10:01:39 +0200 [thread overview]
Message-ID: <83eekxy9b0.fsf@gnu.org> (raw)
In-Reply-To: <m17dqqb2wr.fsf@yahoo.es> (message from Daniel Martín on Thu, 12 Nov 2020 23:56:04 +0100)
> From: Daniel Martín <mardani29@yahoo.es>
> Cc: emacs-devel@gnu.org
> Date: Thu, 12 Nov 2020 23:56:04 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
> >
> > Stab in the dark: the isearch-scroll property of commands, perhaps?
>
> Yes, that works for commands. I was looking for some option that could
> work for events like mouse-movement.
Maybe I'm missing something: an event is meaningless unless it's bound
to some command. And we exit Isearch when certain commands are
invoked, not because some event arrived (this level in Emacs is
completely oblivious to events, anyway).
> I'm not sure if that would be a good idea in general because a minor
> mode may bind the mouse-movement event to a command that is
> incompatible with isearch, right? (for example, because the command
> moves the point).
Indeed, which is why we perform this filtering on the level of
commands.
> So I think the safest way is that users/developers manually mark those
> commands that are compatible with isearch with the isearch-scroll
> property.
That's what we support now. We could, of course, provide some minor
mode that marks many commands with that property, if that's
convenient.
next prev parent reply other threads:[~2020-11-13 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m14klzl7ap.fsf.ref@yahoo.es>
2020-11-09 0:09 ` Handling of [mouse-movement] and exiting isearch Daniel Martín
2020-11-09 3:37 ` Stefan Monnier
2020-11-09 15:40 ` Eli Zaretskii
2020-11-12 22:56 ` Daniel Martín
2020-11-13 8:01 ` Eli Zaretskii [this message]
2020-11-13 10:50 ` Daniel Martín
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=83eekxy9b0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mardani29@yahoo.es \
/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.