From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: follow-link in grep buffer Date: Sat, 26 Feb 2005 01:44:32 +0100 Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1109379977 28497 80.91.229.2 (26 Feb 2005 01:06:17 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 26 Feb 2005 01:06:17 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Feb 26 02:06:17 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D4qPL-0001Um-He for ged-emacs-devel@m.gmane.org; Sat, 26 Feb 2005 02:06:11 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D4qhC-0007ga-JH for ged-emacs-devel@m.gmane.org; Fri, 25 Feb 2005 20:24:38 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D4qgw-0007ba-3n for emacs-devel@gnu.org; Fri, 25 Feb 2005 20:24:22 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D4qg6-0007HA-0H for emacs-devel@gnu.org; Fri, 25 Feb 2005 20:23:36 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D4qg4-00079b-4K for emacs-devel@gnu.org; Fri, 25 Feb 2005 20:23:28 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D4q4Q-0002vh-8r for emacs-devel@gnu.org; Fri, 25 Feb 2005 19:44:34 -0500 Original-Received: from localhost ([127.0.0.1] helo=lola.goethe.zz) by fencepost.gnu.org with esmtp (Exim 4.34) id 1D4q4P-0006Za-PX; Fri, 25 Feb 2005 19:44:34 -0500 Original-To: "Drew Adams" In-Reply-To: (Drew Adams's message of "Fri, 25 Feb 2005 15:34:38 -0800") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.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: , 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 X-MailScanner-To: ged-emacs-devel@m.gmane.org Xref: main.gmane.org gmane.emacs.devel:33822 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:33822 "Drew Adams" writes: > > I use mouse-1 to set point currently, as usual (no > > double-clicking). If we changed mouse-1 to follow links, then I > > would double-click to set point - or I would forego > > mouse-1-follows-links. "Simple editing" would not be affected > > detrimentally by what I or Kim described, and such buffers are not > > for non-simple editing. > > Look, you are arguing for an interface you are not even using > yourself. > > I argued for full-line mouseover highlighting in buffers like > grep. I've been using it for decades. Try it; you'll like it. I don't. I don't need to particularly try it since it is the current default. To make this visually acceptable, we will need two different highlighting faces: a decent one on the whole line (such as underlining), and possibly a more striking one on selected "hot spots", like just the filename in a grep or dired buffer. The whole actionable area can always be invoked by mouse-2, and I think we have agreement that having selected hot spots (like Customize buttons) react to mouse-1 is a good idea. We have not much talked about larger actionable areas not specifically marked as buttons by the application programmer: the initial plans were more or less based on making them behave equal to hot spots or buttons, which has the disadvantage that they often cover areas where one would want to set point with mouse-1. There is some agreement that offering more than mouse-2 on them for triggering the action would be a good idea. My proposal was to use a double mouse-1 click here, so that a single click can still set point. Opinions here vary wildly, with quite a few proposals trying to make a single mouse-1 click also work for triggering an action, but with a mixture of special rules like "how long the click?" "click into non-selected window?" "click into non-focused frame" to pick stuff apart. Rules that partly violate some policies for click event set forth in the Elisp manuals, and rules that partly can't be cast into event types described by our hypertext help system. It is clear that tastes for one's own personal use vary wildly, and it certainly would be nice if many tastes could be accommodated with customization possibilities. > Bad generalization. A better generalization is "Whenever David > discusses something, he screams like Howard Dean in Iowa." But > neither generalization is very good. Whatever. Enough people have pointed out by now that they see little merit or sense or consistency or logic in my proposals. So I'll just stop screaming and let others decide. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum