[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug Report (Feature request?) etags (GNU Emacs 21.1)

From: Sven Utcke
Subject: Re: Bug Report (Feature request?) etags (GNU Emacs 21.1)
Date: Tue, 5 Mar 2002 14:11:54 +0100 (CET)

Hello Francesco,

> I made etags aware of the #line directives that can be found in
> automatically generated sources, for example .y-->.c, or .web-->.[hc].

Great, thanks!

Hmm.  One problem though, although I'm not sure how to handle this:  

I create the tag-file using something like:

find . -name "*.c" -exec etags -a -I -o /home/utcke/src/StreetSigns/TAGS {} \;

probably not the most elegant way to do this (something featuring
xargs would probably be preferred), but it works.  Only: the TAGS file
now contains entries like the following (I'm replacing the non-ascii
characters with a look-alike ascii representation...) 

#define MIN(^?MIN^A1,0
static char rcsid[^?597,
boolean kread_edgels(^?54,

This is because the #line directives in Canny/Khoros/kedgelio.c read:

#line 590 "kedgelio.web"

But of course in the TAGS file it should read
Canny/Khoros/kedgelio.web instead of kedgelio.web.  Possible

a) Get fweb to output absolute paths.
b) Have etags prefix the filename from the #Line-directive with the
   current path.
c) Something else?

I'm not sure what would be the best thing to do here, as both a) and
b) would prevent me from seperating the *.c from the *.web...

 _  __                     The Cognitive Systems Group
| |/ /___  __ _ ___                                       University of Hamburg
| ' </ _ \/ _` (_-<  phone:    +49 (0)40 42883-2576      Vogt-Koelln-Strasse 30
|_|\_\___/\__, /__/  fax  :    +49 (0)40 42883-2572             D-22527 Hamburg
          |___/ http://kogs-www.informatik.uni-hamburg.de/~utcke/home.html

reply via email to

[Prev in Thread] Current Thread [Next in Thread]