From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Nick Roberts Newsgroups: gmane.emacs.devel Subject: RE: mouse-1-click-follows-link Date: Tue, 14 Jun 2005 10:19:09 +1200 Message-ID: <17070.1629.248799.723986@farnswood.snap.net.nz> References: <17067.59794.984974.659746@farnswood.snap.net.nz> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1118702723 23809 80.91.229.2 (13 Jun 2005 22:45:23 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 13 Jun 2005 22:45:23 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 14 00:45:22 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DhxgD-0003OB-5v for ged-emacs-devel@m.gmane.org; Tue, 14 Jun 2005 00:45:17 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dhxl5-0007Ak-Qq for ged-emacs-devel@m.gmane.org; Mon, 13 Jun 2005 18:50:19 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Dhxe0-0005ho-Vn for emacs-devel@gnu.org; Mon, 13 Jun 2005 18:43:01 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Dhxdo-0005dO-97 for emacs-devel@gnu.org; Mon, 13 Jun 2005 18:42:48 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dhxdn-0005Wm-UL for emacs-devel@gnu.org; Mon, 13 Jun 2005 18:42:47 -0400 Original-Received: from [202.37.101.8] (helo=viper.snap.net.nz) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DhxJf-000228-Le for emacs-devel@gnu.org; Mon, 13 Jun 2005 18:22:00 -0400 Original-Received: from farnswood.snap.net.nz (p79-tnt1.snap.net.nz [202.124.110.79]) by viper.snap.net.nz (Postfix) with ESMTP id A01EC546D19; Tue, 14 Jun 2005 10:20:39 +1200 (NZST) Original-Received: by farnswood.snap.net.nz (Postfix, from userid 501) id EFD2962A99; Mon, 13 Jun 2005 23:19:09 +0100 (BST) Original-To: "Drew Adams" In-Reply-To: X-Mailer: VM 7.19 under Emacs 22.0.50.68 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:38757 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:38757 Drew Adams writes: > In the compilation buffer mouse-face (and therefore mouse-1) only works > on the file and line number while mouse-2 and RET work for the > whole line. > > It would help if grep also worked this way. > > I disagree. My opinion: > > 1) mouse-1, RET, and mouse-2 should all behave similarly. What's good for > mouse-2 is good for mouse-1 too. The challenge is to find the right default > behavior (trade-off/compromise). > > 2) The entire line should be the hot zone (no "button"). Makes it very easy > to scan lines and align text anywhere on the line with the proper hot zone. > No need for your eye to move between the text (anywhere on the line) and the > hot zone. Thats not much of a compromise! Jason's point about the touchpad makes it even more important that the entire line should be *not* be the hot zone. > 3) The grep behavior (full-line hot zone) should hold also for the > compilation buffer (compilation and grep should behave similarly). I think it should be the other way round i.e grep should behave like the compilation buffer. > 4) mouse-1 should follow links by default, for the reasons others have given > (even though I, myself, might choose to turn this off). I think the default has been agreed. What we are discussing now is the extent of coverage. > 5) The delay for mouse-1 to set point should be short, by default, so it is > not inconvenient to set point with mouse-1. The current default delay is too > long. Users will naturally click very quickly to follow a link, and if they > click too slowly, they will quickly learn to click quicker (or consult the > doc to change the delay value). Clicking a little too slowly unintentionally > (i.e. when intending to follow a link) will just set point, which is benign. Whatever the period, its hard to estimate in your head while clicking. How long should a piece of string be? Nick