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

[Sven Utcke]

pot@gnu.org (Francesco Potorti`) writes:

>    David> words, would etags wind up generating the same reference twice
>    David> (once from the generated file and once from the original)?
>    
>    etags will already do this if you run it on parse.y and parse.c.
>    I've always found this a bit annoying.  Usually I use some Makefile
>    rule I didn't write to generate TAGS.  So parse.c is included, but I
>    don't want it, since I never want to edit it.  In this scenario it
>    would be convenient if etags ignored the generated file.

Wouldn't it even better if etags referred you to parse.y, as the
#line-directives asks it to do?

Of course you would still get the double referrence, unless etags does
some internal sorting and uniquifying...

> if etags finds a #line directive in file X pointing to file Y, and if
> file Y is given on the command line, then ignore file X.
> 
> Maybe this would better be handled by not giving file X to etags to
> parse.  

But of course this only works if etags knows how to parse file Y.

> Going back to the original question, what happens if you give to etags
> the original .web file, instead of the .c produced from it?

It works on about 50% of the definitions.  For about 25% you get a
reference pointing you to some completely unrelated piece of text
(comments mostly), possibly not even in the correct file.  For the
rest, it simply fails...

And what language are you going to tell etags to use on the .web file,
as it might be used to create files in a dozen different languages...?

Sven
-- 
 _  __                     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