From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: [NEW PATCH] mouse-1 click follows link Date: Fri, 17 Dec 2004 19:20:00 -0500 Message-ID: References: <200410292354.i9TNsCq01994@raven.dms.auburn.edu> <200410310034.i9V0YX903876@raven.dms.auburn.edu> Reply-To: rms@gnu.org NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1103329564 20372 80.91.229.6 (18 Dec 2004 00:26:04 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 18 Dec 2004 00:26:04 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 18 01:25:57 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 1CfSQ1-0005S2-00 for ; Sat, 18 Dec 2004 01:25:57 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CfSaL-0005gg-3c for ged-emacs-devel@m.gmane.org; Fri, 17 Dec 2004 19:36:37 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CfSZI-0005GU-Ks for emacs-devel@gnu.org; Fri, 17 Dec 2004 19:35:32 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CfSZG-0005FA-D3 for emacs-devel@gnu.org; Fri, 17 Dec 2004 19:35:30 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CfSZG-0005Ev-4I for emacs-devel@gnu.org; Fri, 17 Dec 2004 19:35:30 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CfSOh-0000FK-Iq for emacs-devel@gnu.org; Fri, 17 Dec 2004 19:24:35 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1CfSKG-00082m-O7; Fri, 17 Dec 2004 19:20:00 -0500 Original-To: storm@cua.dk (Kim F. Storm) In-reply-to: (storm@cua.dk) 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: main.gmane.org gmane.emacs.devel:31250 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:31250 > It is not just historical reasons. Mouse-2 fits in better with the > usual Emacs mouse bindings than Mouse-1. We've decided to give higher > priority to compatibility with other programs, at the cost of fitting > in not quite as well. Should I mention that in the manual? There's no need for the manual to concern itself with previous versions of Emacs except in the Antinews section. However, explaining briefly the motivation for what the current version does is useful when it is interesting to the reader. So if you see a reason/occasion to do that, please try it. > I suggest you grep for Mouse-2 and for Mouse-1, and change the places > that need changing. What should I change them to? That question has no general answer. How to change the text depends, in each case, on the details of the situation. Should I mention both Mouse-1 and Mouse-2? Probably in most cases only Mouse-1. But it partly depends on what reads well and what would be interesting to the reader. Should I mention mouse-1-click-follows-link (every time)? It would be boring and wasteful to repeat it in each of these places where Mouse-1 gets a brief mention. Rather, find one central place to talk about this option. Perhaps the section that explains the basic general mouse commands could also talk about the convention for mouse link following and the options that affect it. Should I mention that a long mouse-1 click still sets point (depending on the setting of mouse-1-click-follows-link)? Try to put that in the one general explanation and see if it works.