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: tags for functions Date: Fri, 30 Jan 2009 08:06:42 -0800 Message-ID: <003f01c982f4$be64d4c0$0200a8c0@us.oracle.com> References: <867i4pemv5.fsf@lifelogs.com><86y6x49un4.fsf@lifelogs.com> <86ljt39ysz.fsf@lifelogs.com> <87tz7oxodr.fsf@jurta.org><86mydd3kzv.fsf@lifelogs.com> <87pri9k64b.fsf@jurta.org><86ljsw252p.fsf@lifelogs.com> <87hc3kfgb8.fsf@jurta.org><86r62ne3aq.fsf@lifelogs.com> <86bptrdv4f.fsf@lifelogs.com> <861vuldgmu.fsf@lifelogs.com> <864ozgajtx.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1233331688 12192 80.91.229.12 (30 Jan 2009 16:08:08 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 30 Jan 2009 16:08:08 +0000 (UTC) To: "'Ted Zlatanov'" , Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 30 17:09:22 2009 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 1LSvvb-0004h4-54 for ged-emacs-devel@m.gmane.org; Fri, 30 Jan 2009 17:09:11 +0100 Original-Received: from localhost ([127.0.0.1]:39160 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LSvuI-00012A-VP for ged-emacs-devel@m.gmane.org; Fri, 30 Jan 2009 11:07:51 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LSvtU-0000f7-0u for emacs-devel@gnu.org; Fri, 30 Jan 2009 11:07:00 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LSvtS-0000dD-49 for emacs-devel@gnu.org; Fri, 30 Jan 2009 11:06:59 -0500 Original-Received: from [199.232.76.173] (port=47643 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LSvtR-0000cm-QR for emacs-devel@gnu.org; Fri, 30 Jan 2009 11:06:57 -0500 Original-Received: from rcsinet12.oracle.com ([148.87.113.124]:20005 helo=rgminet12.oracle.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1LSvtQ-0002jx-9t for emacs-devel@gnu.org; Fri, 30 Jan 2009 11:06:56 -0500 Original-Received: from acsinet13.oracle.com (acsinet13.oracle.com [141.146.126.235]) by rgminet12.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n0UG6NNt018902 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 30 Jan 2009 16:06:24 GMT Original-Received: from acsmt700.oracle.com (acsmt700.oracle.com [141.146.40.70]) by acsinet13.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n0UG6kdC005484; Fri, 30 Jan 2009 16:06:48 GMT Original-Received: from dradamslap1 (/141.144.161.83) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 30 Jan 2009 16:06:43 +0000 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <864ozgajtx.fsf@lifelogs.com> Thread-Index: AcmC8C51gPKS3wjrThCvypO0ZOR3qQAA0l8Q X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Source-IP: acsmt700.oracle.com [141.146.40.70] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A09020A.49832596.0021:SCFSTAT928724,ss=1,fgs=0 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 1) 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:108413 Archived-At: 1. When the thing documented in *Help* is also in the manual, then we have a link to the manual from the *Help* buffer. 2. The manual should have such a `See also' cross reference, if any place should. 3. When both the thing doc'd in *Help* and the thing xref'd are in the manual, #1 and #2 would take care of such cross-referencing. Admittedly, passing through the manual represents an indirection, but typically a fruitful one. Dunno if it's worth adding this for cases that are not covered by the manual. It sounds like a helpful feature. I can't speak to the implementation cost. (There is also a doc-maintenance cost to consider.)