[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: etags confused with uppercase filenames (on Windows)
From: |
Francesco Potorti` |
Subject: |
Re: etags confused with uppercase filenames (on Windows) |
Date: |
Tue, 02 Apr 2002 17:19:09 +0200 |
This particular problem can be solved by adding "EL" to the
Lisp_suffixes array in etags.c.
Indeed.
By the way, Stavros can circumvent his problem by prepending to the file
names the option --language=lisp.
However, I don't think etags can be made case-insensitive to file
names in general, since foo.C needs to be processed as C++ code,
while foo.c should be processed as C code.
That would not be a big problem, because etags can distinguish C and C++
by looking at the file contents. But in general, I agree that making
etags case insensitive on file names means losing information, and
is not the right thing to do.
> This happened to me because in some transfer from one filesystem to
>another, some piece of software decided to canonicalize filenames as
>all-caps....
I have an idea, and would like to hear if anyone has anything against
it.
To determine a file's language, currently etags does the following:
1) if the user specified a language, use that
2) else, guess it from the file name
3) else, look for #!
4) ... (other euristics)
I think that I could add:
2bis) else, if the file name is all upcase, upcase the builtin file name
suffixes and retry
- Re: etags confused with uppercase filenames (on Windows),
Francesco Potorti` <=
Re: etags confused with uppercase filenames (on Windows), Eli Zaretskii, 2002/04/03