From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: cyd@stupidchicken.com, romain@orebokech.com, emacs-devel@gnu.org,
"Kim F. Storm" <storm@cua.dk>
Subject: Re: Difficulty with mouse-1-click-follows-link
Date: Thu, 13 Oct 2005 10:39:57 -0400 [thread overview]
Message-ID: <jwvll0xwkm5.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1EPv5E-0007yo-6k@fencepost.gnu.org> (Richard M. Stallman's message of "Thu, 13 Oct 2005 00:52:48 -0400")
>>>>> "Richard" == Richard M Stallman <rms@gnu.org> writes:
> IIRC, the code you removed was intended to make a double-click do the
> normal action at point rather than following the link
> (when mouse-1-click-follows-link != double-click).
> That is important. Double-click of mouse-1 has a standard meaning,
> and the link-following feature is not supposed to interfere with it.
> Whether the old code succeeded in keeping double-click working right,
> I don't know. But if it doesn't work correctly now, it needs to be
> fixed.
An alternative implementation which may fix the problem could look like:
After the first click, start a timer waiting for double-click-time and
add a pre-command-hook. The timer just runs the mouse-2 binding.
The pre-command-hook will cancel the timer and depending on whether the
triggering event is a double-click or not, it will run the mouse-2 binding.
This way you avoid the problematic sit-for. But it's pretty nasty code in
any case.
Stefan
next prev parent reply other threads:[~2005-10-13 14:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-09 17:57 Difficulty with mouse-1-click-follows-link Chong Yidong
2005-10-09 18:51 ` Romain Francoise
2005-10-10 16:46 ` Chong Yidong
2005-10-11 17:16 ` Romain Francoise
2005-10-11 21:04 ` Kim F. Storm
2005-10-11 21:20 ` Chong Yidong
2005-10-12 9:32 ` Kim F. Storm
2005-10-12 13:11 ` Chong Yidong
2005-10-12 13:37 ` Kim F. Storm
2005-10-13 4:52 ` Richard M. Stallman
2005-10-13 14:39 ` Stefan Monnier [this message]
2005-10-13 15:33 ` Chong Yidong
2005-10-14 5:10 ` Richard M. Stallman
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=jwvll0xwkm5.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=romain@orebokech.com \
--cc=storm@cua.dk \
/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).