From: Francesco Potorti` <pot@gnu.org>
Cc: Emacs developers <emacs-devel@gnu.org>,
Stavros Macrakis <stavros.macrakis@verizon.net>
Subject: Re: etags confused with uppercase filenames (on Windows)
Date: Tue, 02 Apr 2002 17:19:09 +0200 [thread overview]
Message-ID: <E16sQ3x-0003Nx-00@potorti.it> (raw)
In-Reply-To: "eliz@is.elta.co.il"'s message of Sat, 30 Mar 2002 11:37:38 +0300
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
next reply other threads:[~2002-04-02 15:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-02 15:19 Francesco Potorti` [this message]
2002-04-02 15:46 ` etags confused with uppercase filenames (on Windows) Stavros Macrakis
2002-04-02 16:02 ` Stefan Monnier
2002-04-03 7:57 ` Eli Zaretskii
2002-04-03 8:43 ` Francesco Potorti`
2002-04-03 15:42 ` Stefan Monnier
2002-04-03 21:23 ` Francesco Potorti`
2002-04-03 15:22 ` Stefan Monnier
2002-04-04 17:36 ` Richard Stallman
2002-04-03 7:54 ` Eli Zaretskii
2002-04-03 21:40 ` Stavros Macrakis
-- strict thread matches above, loose matches on Subject: below --
2002-04-03 22:01 Stavros Macrakis
2002-03-30 1:56 Stavros Macrakis
2002-03-30 8:37 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E16sQ3x-0003Nx-00@potorti.it \
--to=pot@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stavros.macrakis@verizon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.