bug-gnu-emacs
[Top][All Lists]
Advanced

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

RE: tags-search does not work on compressed tags file


From: WAROQUIERS Philippe
Subject: RE: tags-search does not work on compressed tags file
Date: Fri, 11 Jan 2002 21:09:39 +0100

As I did the support for the compressed files in etags.el
(on behalf of Francesco), at that time, I understood that
the idea was to be able to etags either compressed or
uncompressed files, potentially compressing the non-compressed
files *after* etags.

etags.el was then upgraded to have the intelligence to search
for files with "compression extension" in case it was not finding
the file with only the original name.

The problem in this area is that only find-tag was extended
with this intelligence.
next-file has not been made more intelligent.

I am quite sure I would be able to correct the problem in
etags.el but ...
  * I am *terribly* overloaded by my normal job currently.
  * second, maybe this intelligence to search files with compression
    names added automatically should not be handled in etags but
    maybe in another place (where some other emacs packages could
    use this intelligence). Maybe find-file, get-buffer-file and
    all these should get a list of extensions to try in case they
    do not find the original file.

Sorry for not having the time to work on this problem :(

-----Original Message-----
From: Eli Zaretskii [mailto:address@hidden
Sent: 11-Jan-2002 18:37
To: address@hidden
Cc: address@hidden; Francesco Potorti`
Subject: Re: tags-search does not work on compressed tags file


> From: Philippe Waroquiers <address@hidden>
> Date: Thu, 10 Jan 2002 20:41:39 +0100 (MET)
> 
> next-file: Opening input file: no such file or directory, /tmp/tagged.c
> (same behaviour for tags-query-replace)

Ah, I see the problem: the file TAGS names tagged.c, not tagged.c.gz.
If I edit TAGS to mention tagged.c.gz instead, everything works as you
expect.

Francesco, is that done on purpose?  It's not clear to me whether
this should be fixed in etags or in etags.el.



reply via email to

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