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: RE: hyperlinks in variable's value - links to libraries Date: Sat, 7 Jan 2006 07:38:55 -0800 Message-ID: References: <17343.9228.226503.690284@kahikatea.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 1136648931 24480 80.91.229.2 (7 Jan 2006 15:48:51 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 7 Jan 2006 15:48:51 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 07 16:48:48 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EvGJ0-00041f-2l for ged-emacs-devel@m.gmane.org; Sat, 07 Jan 2006 16:48:34 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EvGKo-0006We-6M for ged-emacs-devel@m.gmane.org; Sat, 07 Jan 2006 10:50:26 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EvGBn-0001zt-EQ for emacs-devel@gnu.org; Sat, 07 Jan 2006 10:41:07 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EvGBj-0001wn-5h for emacs-devel@gnu.org; Sat, 07 Jan 2006 10:41:05 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EvGBh-0001vd-9I for emacs-devel@gnu.org; Sat, 07 Jan 2006 10:41:01 -0500 Original-Received: from [141.146.126.228] (helo=agminet01.oracle.com) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1EvGDd-0005iJ-Tu for emacs-devel@gnu.org; Sat, 07 Jan 2006 10:43:02 -0500 Original-Received: from rgmsgw300.us.oracle.com (rgmsgw300.us.oracle.com [138.1.186.49]) by agminet01.oracle.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k07Fd0M7020123 for ; Sat, 7 Jan 2006 09:39:01 -0600 Original-Received: from rgmsgw300.us.oracle.com (localhost [127.0.0.1]) by rgmsgw300.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id k07Fd0Dr012863 for ; Sat, 7 Jan 2006 08:39:00 -0700 Original-Received: from dradamslap (dhcp-amer-rmdc-csvpn-gw6-141-144-112-252.vpn.oracle.com [141.144.112.252]) by rgmsgw300.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with SMTP id k07Fcxrd012855 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Sat, 7 Jan 2006 08:39:00 -0700 Original-To: "Emacs-Devel" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <17343.9228.226503.690284@kahikatea.snap.net.nz> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE 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:48820 Archived-At: > Yes, of course. However, in practice, it works quite well... I don't think it does. > The problem of multiple names of different types is pretty > well handled by ordering (priority) - see the code I sent. When I tried it it linked to a function if there was one, and only to a library if there was no function with the same name. Yes. I found that works well, in practice. The priority could be changed, of course, but a function foo in a library foo is generally a tighter focus, so a better bet on average. This is the way the code already worked, for dealing with function and variable names. I just added library names. As I said, mixes of either function or variable names and library names are uncommon in *Help* buffers. You might get the occasional foo function or variable being linked to, instead of foo library, in the `features' list, but that is not a big problem, because you still end up in the library code (via one more link, "defined in foo").