From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: storm@cua.dk (Kim F. Storm) Newsgroups: gmane.emacs.devel Subject: Re: finger-pointer curser as default for mouse-face text Date: Mon, 25 Oct 2004 10:31:52 +0200 Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1098693173 29374 80.91.229.6 (25 Oct 2004 08:32:53 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 25 Oct 2004 08:32:53 +0000 (UTC) Cc: rms@gnu.org, drew.adams@oracle.com, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 25 10:32:40 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1CM0HQ-00006t-00 for ; Mon, 25 Oct 2004 10:32:40 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CM0P3-0000sq-MW for ged-emacs-devel@m.gmane.org; Mon, 25 Oct 2004 04:40:33 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CM0OV-0000sf-Te for emacs-devel@gnu.org; Mon, 25 Oct 2004 04:40:00 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CM0OU-0000sT-Ck for emacs-devel@gnu.org; Mon, 25 Oct 2004 04:39:58 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CM0OU-0000sQ-4r for emacs-devel@gnu.org; Mon, 25 Oct 2004 04:39:58 -0400 Original-Received: from [212.88.64.25] (helo=mail-relay.sonofon.dk) by monty-python.gnu.org with smtp (Exim 4.34) id 1CM0GZ-0002R5-4q for emacs-devel@gnu.org; Mon, 25 Oct 2004 04:31:47 -0400 Original-Received: (qmail 68645 invoked from network); 25 Oct 2004 08:31:46 -0000 Original-Received: from unknown (HELO kfs-l.imdomain.dk.cua.dk) (213.83.150.2) by 0 with SMTP; 25 Oct 2004 08:31:46 -0000 Original-To: Stefan In-Reply-To: (Stefan's message of "Sun, 24 Oct 2004 18:31:33 -0400") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/21.3.50 (gnu/linux) 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: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:28885 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:28885 Stefan writes: >> I found a simpler solution which works really well, as it provides the >> fallback directly on mouse-1 itself: > >> Measure the time between the mouse-1 down event and the up event, and >> if it less than 300 ms (configurable), follow the link, else do what >> mouse-1 normally does. > > Sounds like a terrible idea to me. Working with X11-over-DSL means that > timing is rather unreliable. Same thing with heavy-swapping (as happens > when a I do `tla star-merge' :-( ). True, but the worst thing that can happen (if you use a positive value) is that the click sets the point rather than follows the link -- so if things are slow, just click again (and hope for the best) or use mouse-2. I don't think that's terrible at all. And you can always set the variable to t, meaning that you will need to drag to set point. And on a local system, it works really well!!! > > And even if the timing could be measured accurately, I don't find the "hold > the mouse button longer" to be intuitive at all for "move point". Press harder to make the glue stick :-) Personally I find "drag to set point" much less intuitive which is why I'm looking for a better solution. > I think we're trying to squeeze too much info in those events. I'm quite > happy with the distinction between click and drag but I don't think we > should go further than that. We are trying to find a simple(!) way to let mouse-1 do its normal thing in the rare situation (except for David :-) where the user wants to set point in the middle of a link. Providing the "long click" as a user option is trivial (it is 3 lines of code and it is already done), and personally, I find it quite intuitive. Whether we want to turn it on by default (with or without timeout) is another matter. -- Kim F. Storm http://www.cua.dk