From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Mouse click vs drag
Date: Tue, 22 Sep 2020 20:12:36 +0300 [thread overview]
Message-ID: <837dslwxa3.fsf@gnu.org> (raw)
In-Reply-To: <87ft79sprs.fsf@iki.fi> (message from Petteri Hintsanen on Tue, 22 Sep 2020 20:08:23 +0300)
> From: Petteri Hintsanen <petterih@iki.fi>
> Cc: help-gnu-emacs@gnu.org
> Date: Tue, 22 Sep 2020 20:08:23 +0300
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Did you try to enlarge double-click-fuzz?
>
> Tried now, doesn’t help.
It does here.
What did you try? For a mouse-movement NOT to be interpreted as a
mouse-drag, the movement must be smaller than double-click-fuzz AND
the mouse pointer should stay on the same buffer position.
next prev parent reply other threads:[~2020-09-22 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 15:57 Mouse click vs drag Petteri Hintsanen
2020-09-22 16:24 ` Stefan Monnier
2020-09-22 17:07 ` Eli Zaretskii
2020-09-22 16:38 ` Eli Zaretskii
2020-09-22 17:08 ` Petteri Hintsanen
2020-09-22 17:12 ` Eli Zaretskii [this message]
2020-09-22 17:50 ` Petteri Hintsanen
-- strict thread matches above, loose matches on Subject: below --
2020-09-23 8:09 Anders Munch
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=837dslwxa3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).