From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: links in *Apropos* buffer Date: Sat, 22 Sep 2007 16:02:40 -0700 Message-ID: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1190502205 29609 80.91.229.12 (22 Sep 2007 23:03:25 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 22 Sep 2007 23:03:25 +0000 (UTC) To: "Emacs-Devel" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Sep 23 01:03:19 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1IZE0M-0008TP-4G for ged-emacs-devel@m.gmane.org; Sun, 23 Sep 2007 01:03:18 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IZE0J-0003UH-On for ged-emacs-devel@m.gmane.org; Sat, 22 Sep 2007 19:03:15 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IZE0G-0003SX-AC for emacs-devel@gnu.org; Sat, 22 Sep 2007 19:03:12 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IZE0E-0003Pp-0o for emacs-devel@gnu.org; Sat, 22 Sep 2007 19:03:11 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IZE0D-0003Pd-MT for emacs-devel@gnu.org; Sat, 22 Sep 2007 19:03:09 -0400 Original-Received: from agminet01.oracle.com ([141.146.126.228]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1IZE0D-00077N-5k for emacs-devel@gnu.org; Sat, 22 Sep 2007 19:03:09 -0400 Original-Received: from agmgw1.us.oracle.com (agmgw1.us.oracle.com [152.68.180.212]) by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id l8MN377i015336 for ; Sat, 22 Sep 2007 18:03:07 -0500 Original-Received: from acsmt351.oracle.com (acsmt351.oracle.com [141.146.40.151]) by agmgw1.us.oracle.com (Switch-3.2.0/Switch-3.2.0) with ESMTP id l8MM39t4008299 for ; Sat, 22 Sep 2007 17:03:06 -0600 Original-Received: from dhcp-amer-whq-csvpn-gw3-141-144-80-168.vpn.oracle.com by acsmt350.oracle.com with ESMTP id 3237854641190502140; Sat, 22 Sep 2007 16:02:20 -0700 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 X-Brightmail-Tracker: AAAAAQAAAAI= X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-Whitelist: TRUE X-Detected-Kernel: Linux 2.4-2.6 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:79541 Archived-At: There is duplication in the links of an *Apropos* buffer: the command/function/macro/variable/plist/face name has a link that is identical to one of the links below it (Command, Function, etc.). Apparently, it is the first such link that is duplicated. And most apropos entries have only one link below them (they are only a command or only a variable etc.), so this is nearly 100% duplication. A user will click both the command name and the word "Command" to see what they point to, and will discover that they are the same thing. I propose that we do away with this duplication. Here are some possibilities (alternatives): 1. Just remove the link on the command etc. name. 2. Have the link on the command etc. name take you to its treatment in an appropriate manual (for a command, it would do `Info-goto-emacs-command-node', for instance). Since there might be several such entries, this might actually access the relevant index entries or it could do as `Info-goto-emacs-command-node' does (put other entries in `Info-history'). 3. Have the link on the command etc. name take you to the source code that defines it. As now, whenever there are multiple entries for the same name (e.g. function, variable, face), the definition of the first of these would be used. It could be argued that a link on the entry name is too prominent to send you to source code, especially C code. I vote for #2. If that's not feasible, then #1.