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 19:40:50 +0200	[thread overview]
Message-ID: <86bjyxy1nh.fsf@gnu.org> (raw)
In-Reply-To: <jwvv7x5bmdq.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sat, 02 Nov 2024 13:04:25 -0400)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: dradetsky@gmail.com,  luangruo@yahoo.com,  emacs-devel@gnu.org
> Date: Sat, 02 Nov 2024 13:04:25 -0400
> 
> >> I think the answer is yes, tho I'm not sure what you mean by "think
> >> input events arrived" nor why you seem to think that would be a problem.
> >
> > I mentioned that in my original comments: stuff like while-no-input
> > will think some input arrived, which is not what the users would want,
> > when this knob is used.
> 
> 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, 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.



  reply	other threads:[~2024-11-02 17:40 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 [this message]
2024-11-02 18:11                 ` Stefan Monnier
2024-11-02 18:32                   ` Eli Zaretskii
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=86bjyxy1nh.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).