all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Daniel Martín" <mardani29@yahoo.es>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Handling of [mouse-movement] and exiting isearch
Date: Fri, 13 Nov 2020 11:50:27 +0100	[thread overview]
Message-ID: <m1361dbkek.fsf@yahoo.es> (raw)
In-Reply-To: <83eekxy9b0.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 13 Nov 2020 10:01:39 +0200")

Eli Zaretskii <eliz@gnu.org> writes:
>
> 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.

Yes, that may be convenient.  If I understand correctly, the minor mode
would set isearch-allow-scroll to t on enter and leave it nil on exit.
And it could expose some functions like

(add-isearch-compatible-commands COMMAND1 COMMAND2 ...)
(remove-isearch-compatible-commands COMMAND1 COMMAND2 ...)
(isearch-compatible-command-p COMMAND)

that would transparently add/remove/query the isearch-scroll property of
their arguments.

A nice side effect of this new minor mode is that the naming will make
it more clear that not every command is about scrolling (for example,
enlarge-window), while keeping backwards compatibility.

I need to think about how this feature would play with the rest of the
configuration options in isearch.  What if the user wants
isearch-allow-scroll set to 'unlimited, for example.

Opinions?



      reply	other threads:[~2020-11-13 10:50 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
2020-11-13 10:50         ` Daniel Martín [this message]

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=m1361dbkek.fsf@yahoo.es \
    --to=mardani29@yahoo.es \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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.