unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stavros Macrakis" <stavros.macrakis@verizon.net>
Cc: "Emacs developers" <emacs-devel@gnu.org>
Subject: RE: etags confused with uppercase filenames (on Windows)
Date: Tue, 2 Apr 2002 10:46:55 -0500	[thread overview]
Message-ID: <000801c1da5d$9da31950$34f3fea9@gazi> (raw)
In-Reply-To: <E16sQ3x-0003Nx-00@potorti.it>

Thanks, Francesco and Eli, for your thoughts on etags *.el.

I wouldn't want you to spend too much time thinking about this, though!
Mainly, it was a surprise to me.  I had transferred some files a long time
ago, and they happened to have been upcased somewhere, and I never noticed
that they weren't being indexed by etags.

One of the confusing things in all this is that the wildcard "*.el" in
Windows matches "xxx.EL", too.  Not much we can do about that.

One simple solution might be to give a warning message in etags for
unrecognized extensions, and perhaps files with zero tag entries.  If etags
had told me that .EL was unrecognized, I would have just renamed the files.

By the way, what's the purpose of generating a tag entry for every line of
an unrecognized file type?

        -s

  reply	other threads:[~2002-04-02 15:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-02 15:19 etags confused with uppercase filenames (on Windows) Francesco Potorti`
2002-04-02 15:46 ` Stavros Macrakis [this message]
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

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000801c1da5d$9da31950$34f3fea9@gazi' \
    --to=stavros.macrakis@verizon.net \
    --cc=emacs-devel@gnu.org \
    --cc=macrakis@alum.mit.edu \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).