From: storm@cua.dk (Kim F. Storm)
Cc: Romain Francoise <romain@orebokech.com>, emacs-devel@gnu.org
Subject: Re: Difficulty with mouse-1-click-follows-link
Date: Wed, 12 Oct 2005 11:32:47 +0200 [thread overview]
Message-ID: <m3r7arcc74.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <87achf7ntw.fsf@stupidchicken.com> (Chong Yidong's message of "Tue, 11 Oct 2005 17:20:27 -0400")
Chong Yidong <cyd@stupidchicken.com> writes:
>> As the author of the feature, I just want to point out that originally
>> I did not include double-click support, but I added it on request from RMS.
>>
>> If it turns out to be a major obstackle for using the feature (I haven't
>> had that experience myself), I don't mind removing it.
>
> Just to avoid a misunderstanding: the change I made (removing the
> sit-for call in mouse-drag-region-1) doesn't affect the double-click
> support. Setting mouse-1-click-follows-link to 'double still has the
> same results: it makes a double-click rather than a single click
> follow the link. As far as I can see, there are no bad side-effects
> to the change.
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).
I'm not sure how useful that feature was, but it was added on request
from RMS.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2005-10-12 9:32 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 [this message]
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
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=m3r7arcc74.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=romain@orebokech.com \
/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).