unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: dradetsky@gmail.com, luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: Disabling mouse input
Date: Sat, 02 Nov 2024 20:32:11 +0200	[thread overview]
Message-ID: <867c9lxz9w.fsf@gnu.org> (raw)
In-Reply-To: <jwvplndbjv0.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sat, 02 Nov 2024 14:11:58 -0400)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: dradetsky@gmail.com,  luangruo@yahoo.com,  emacs-devel@gnu.org
> Date: Sat, 02 Nov 2024 14:11:58 -0400
> 
> >> IIUC the problematic events tend to occur "in the middle of other
> >> events", because they are generated as a side effect of the hand
> >> movement that causes the other events, so I suspect the effect on
> >> `while-no-input` is not particularly important.
> > I'm not sure I would be happy relying on that, or in general that such
> > events will be seen in the queue,
> 
> Maybe.  AFAICT the fundamental problem is a hardware problem (where the
> touchpad sometimes registers events which were not intended) and
> disabling all mouse events in Emacs is just one of the workarounds the
> OP considered taking.
> 
> While I'm sure other people are faced with the same problem, I can't see
> any evidence that it's a very common wish, so I'd rather not make the
> C input code even more hairy than it already is by adding ad-hoc code
> for that if there's a way to get 99% of the result with
> a Lisp-only solution.

If the OP is happy with this kind of solution, I don't mind.

> > but there's AFAIU a larger problem with this method: it requires users
> > to add a lot of events to the list of events "disabled" via this
> > method.  It is also not very future-proof, I think.  E.g., what about
> > drag-N, drag-n-drop, etc.?  My understanding was that the OP wanted
> > a way of disabling mouse events without the need to go though all the
> > possible symbols Emacs uses for them.
> 
> Indeed, and this is a much wider problem.
> E.g. for many years I had exactly such a nasty list of bindings to remap
> all the variations of `mouse-4/5` events to `wheel-up/down`.

And then what to do with track-mouse?



  reply	other threads:[~2024-11-02 18:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-02  2:01 Disabling mouse input Daniel Radetsky
2024-11-02  2:44 ` Corwin Brust
2024-11-02  3:07   ` Daniel Radetsky
2024-11-02  7:38 ` Eli Zaretskii
2024-11-02 10:17   ` Daniel Radetsky
2024-11-02 12:04     ` Eli Zaretskii
2024-11-02 13:38     ` Stefan Monnier
2024-11-02 14:32       ` James Cherti
2024-11-02 16:30         ` Dov Grobgeld
2024-11-02 16:43           ` Stefan Monnier
2024-11-02 17:07             ` tomas
2024-11-03 12:34           ` James Cherti
2024-11-03 12:47             ` tomas
2024-11-02 16:50       ` Eli Zaretskii
2024-11-02 16:54         ` Stefan Monnier
2024-11-02 16:59           ` Eli Zaretskii
2024-11-02 17:04             ` Stefan Monnier
2024-11-02 17:40               ` Eli Zaretskii
2024-11-02 18:11                 ` Stefan Monnier
2024-11-02 18:32                   ` Eli Zaretskii [this message]
2024-11-02 23:09                   ` Daniel Radetsky
2024-11-03  1:56                     ` Stefan Monnier
2024-11-03  7:54                       ` Daniel Radetsky
2024-11-03 14:01       ` James Cherti
2024-11-04  9:48   ` Po Lu
2024-11-04 13:20     ` Eli Zaretskii
2024-11-02 13:17 ` James Cherti

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=867c9lxz9w.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dradetsky@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.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).