Re: Why does etags ask me if I want to keep the old TAGS - I do not want to load a new

[Eli Zaretskii]

> Date: Tue, 10 Apr 2007 08:07:02 +0200
> From: "Matzi Kratzi" <address@hidden>
> 
> I work on a software project with the source files in quite some
> directories. I create my TAGS table in
> k:/ERADIUM_kalle/LD_swmodules_005 and work in another. The first time
> I use "M-.", I am asked for the tags table to use. After responding to
> this I am taken to the definition.
> 
> If I then use "M-." to get to another definition, I am asked "Keep
> current list of tags tables also?".

Thank you for your report.

> If I have the *Message*-buffer in another window, I can now see this:
> k:/ERADIUM_kalle/LD_swmodules_005/TAGS and
> k:/ERADIUM_kalle/LD_SwModules_005/TAGS are the same file [2 times]

Note that these two file names are identical, but for the letter-case.
Since Windows filesystems are case-insensitive, these two names indeed
specify the same file.  The question is: where did Emacs get these two
names?

> Confessions:
> Since I haven't been able to find a way to produce TAGS-tables on
> windows 2000 recursively, I use "ctags -e" with ctags from
> "http://ctags.sourceforge.net/";.

This is not the Emacs etags program, so we probably have no idea what
it can do.  Why not use etags.exe that comes with Emacs? it works
flawlessly for me on Windows as well as on GNU/Linux, and I have yet
to see such problems.

> k: is where my clearcase mounts are located.

Does that mean that drive k: is the so-called ClearCase ``dynamic
view''?  If so, it could be that the virtual filesystem created by
ClearCase to mount its dynamic view somehow works differently than
native Windows filesystems, and dupes Emacs into thinking that TAGS
table was modified or moved/renamed.

Do you see such problems with etags and in local filesystems
(i.e. your hard disk)?  If not, there's probably little we can do for
you, since the problem seems to involve 2 pieces of non-trivial
software that are not related to Emacs: ctags and ClearCase.  Unless,
of course, you debug this problem yourself and report here your
findings that will indicate some bug in Emacs.