From: Eli Zaretskii <eliz@fencepost.gnu.org>
Cc: pot@gnu.org, emacs-devel@gnu.org, stavros.macrakis@verizon.net
Subject: Re: etags confused with uppercase filenames (on Windows)
Date: Wed, 03 Apr 2002 02:57:57 -0500 [thread overview]
Message-ID: <E16sfeX-0007YX-00@fencepost.gnu.org> (raw)
In-Reply-To: <200204021602.g32G2oS02957@rum.cs.yale.edu> (monnier+gnu/emacs@RUM.cs.yale.edu)
> From: "Stefan Monnier" <monnier+gnu/emacs@RUM.cs.yale.edu>
> Date: Tue, 02 Apr 2002 11:02:49 -0500
>
> But I do think that #! should take precedence since I'd rather
> not change the existing behavior on POSIX systems.
Does it really make sense to have etags behavior be different on
different platforms? Especially given the fact that some file you are
working on can well come from a Windows system that exports its
filesystem?
More specifically, what bad effects could be caused by treating
FOO.EL on Unix and GNU systems as an Emacs Lisp file for the purposes
of etags?
next prev parent reply other threads:[~2002-04-03 7:57 UTC|newest]
Thread overview: 14+ 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
2002-04-02 16:02 ` Stefan Monnier
2002-04-03 7:57 ` Eli Zaretskii [this message]
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=E16sfeX-0007YX-00@fencepost.gnu.org \
--to=eliz@fencepost.gnu.org \
--cc=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=pot@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.