From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Difficulty with mouse-1-click-follows-link Date: Thu, 13 Oct 2005 10:39:57 -0400 Message-ID: References: <877jcmlgig.fsf@stupidchicken.com> <87vf06ttgd.fsf@pacem.orebokech.com> <87mzlh48wt.fsf@stupidchicken.com> <873bn8j7ok.fsf@pacem.orebokech.com> <87achf7ntw.fsf@stupidchicken.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1129215143 323 80.91.229.2 (13 Oct 2005 14:52:23 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 13 Oct 2005 14:52:23 +0000 (UTC) Cc: cyd@stupidchicken.com, romain@orebokech.com, emacs-devel@gnu.org, "Kim F. Storm" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Oct 13 16:52:21 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EQ4Iy-0007Tr-6G for ged-emacs-devel@m.gmane.org; Thu, 13 Oct 2005 16:43:36 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EQ4Ix-0004gb-GD for ged-emacs-devel@m.gmane.org; Thu, 13 Oct 2005 10:43:35 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EQ4Ft-0003hR-Ox for emacs-devel@gnu.org; Thu, 13 Oct 2005 10:40:25 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EQ4Fc-0003ck-Pr for emacs-devel@gnu.org; Thu, 13 Oct 2005 10:40:25 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EQ4Fc-0003cY-EL for emacs-devel@gnu.org; Thu, 13 Oct 2005 10:40:08 -0400 Original-Received: from [132.204.24.67] (helo=mercure.iro.umontreal.ca) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EQ4FY-0004E8-GL; Thu, 13 Oct 2005 10:40:04 -0400 Original-Received: from hidalgo.iro.umontreal.ca (hidalgo.iro.umontreal.ca [132.204.27.50]) by mercure.iro.umontreal.ca (Postfix) with ESMTP id C0A4B2CF61E; Thu, 13 Oct 2005 10:40:03 -0400 (EDT) Original-Received: from asado.iro.umontreal.ca (asado.iro.umontreal.ca [132.204.24.84]) by hidalgo.iro.umontreal.ca (Postfix) with ESMTP id 20CAD4AC00A; Thu, 13 Oct 2005 10:39:58 -0400 (EDT) Original-Received: by asado.iro.umontreal.ca (Postfix, from userid 20848) id 0D0CAE6C1A; Thu, 13 Oct 2005 10:39:58 -0400 (EDT) Original-To: rms@gnu.org In-Reply-To: (Richard M. Stallman's message of "Thu, 13 Oct 2005 00:52:48 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-DIRO-MailScanner-Information: Please contact the ISP for more information X-DIRO-MailScanner: Found to be clean X-DIRO-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=-4.849, requis 5, autolearn=not spam, AWL 0.05, BAYES_00 -4.90) X-MailScanner-From: monnier@iro.umontreal.ca X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:43987 Archived-At: >>>>> "Richard" == Richard M Stallman 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