From mboxrd@z Thu Jan 1 00:00:00 1970 Path: quimby.gnus.org!not-for-mail From: Sven Utcke Newsgroups: gmane.emacs.devel Subject: Re: Bug Report (Feature request?) etags (GNU Emacs 21.1) Date: Fri, 22 Feb 2002 12:37:35 +0100 (CET) Message-ID: <200202221137.g1MBbZk02551@kogs46.informatik.uni-hamburg.de> NNTP-Posting-Host: quimby2.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: quimby2.netfonds.no 1014378063 25662 195.204.10.66 (22 Feb 2002 11:41:03 GMT) X-Complaints-To: usenet@quimby2.netfonds.no NNTP-Posting-Date: 22 Feb 2002 11:41:03 GMT Cc: storm@cua.dk, pot@gnu.org, emacs-devel@gnu.org Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby2.netfonds.no with esmtp (Exim 3.12 #1 (Debian)) id 16eE4U-0006fo-00 for ; Fri, 22 Feb 2002 12:41:03 +0100 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.33 #1 (Debian)) id 16eE2j-0005Gw-00; Fri, 22 Feb 2002 06:39:13 -0500 Original-Received: from rzdspc1.informatik.uni-hamburg.de ([134.100.9.61]) by fencepost.gnu.org with esmtp (Exim 3.33 #1 (Debian)) id 16eE1H-0005BE-00; Fri, 22 Feb 2002 06:37:43 -0500 Original-Received: from kogs1.informatik.uni-hamburg.de (kogs1.informatik.uni-hamburg.de [134.100.12.111]) by rzdspc1.informatik.uni-hamburg.de (8.12.2/8.12.2) with ESMTP id g1MBbat5009059; Fri, 22 Feb 2002 12:37:36 +0100 (CET) Original-Received: from kogs46.informatik.uni-hamburg.de (kogs46.informatik.uni-hamburg.de [134.100.12.146]) by kogs1.informatik.uni-hamburg.de (8.12.2/8.12.2) with ESMTP id g1MBbZWd025959; Fri, 22 Feb 2002 12:37:35 +0100 (CET) Original-Received: (from utcke@localhost) by kogs46.informatik.uni-hamburg.de (8.10.1/8.10.1) id g1MBbZk02551; Fri, 22 Feb 2002 12:37:35 +0100 (CET) Original-To: rms@gnu.org In-Reply-To: <200202220433.g1M4XCj14050@aztec.santafe.edu> from "Richard Stallman" at Feb 21, 2002 09:33:12 PM X-Mailer: ELM [version 2.5 PL2] X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.5 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: quimby.gnus.org gmane.emacs.devel:1410 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:1410 Hello Richard, hello all, > It has been mentioned before to put dual references into TAGS: > one for the actual file, and one for the file from the #line > directive. This is simple. > > Having both files in the TAGS table is what we want to AVOID. > It is wasteful. Not in the case to which the sentence above was alluding. There you would have a line FUNC f::x(a,b) { a /?/ b } in the .ylag file, but a line _YLfunc_x__f_(_YLp *a, _YLp *b) in the generated .c file. I believe the only way to reasonably handle this would be _four_ references altogether: One for each file, and one for each functionname. So looking up f::a would get you to the *.ylag file first, and to the *.c file next (Ok, this would probably be hard to implement :-), while looking up _YLfunc_x__f_ (why would anybody want to do that?) would get you to the *.c file first and to the *.ylag next. I guess. But then, I have no clue about ylag, only web. And for the latter _one_ reference (to the *.web) would certainly be enough... Sven -- _ __ The Cognitive Systems Group | |/ /___ __ _ ___ University of Hamburg | '