From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: monnier+gnu/emacs@rum.cs.yale.edu
Subject: Re: loaddefs.el filenames as seen by `update-file-autoloads'
Date: Tue, 13 May 2003 10:00:54 -0400 [thread overview]
Message-ID: <200305131400.h4DE0sd6012045@rum.cs.yale.edu> (raw)
In-Reply-To: E19FR3t-0004v6-00@colo.agora-net.com
> From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
> Date: Mon, 12 May 2003 21:14:13 -0400
>
> Under W32, the file-system preserves the capitalization, even though
> it ignores it when searching for files. I.e. you can't have both "Foo"
> and "FOO", but after creating "Foo", an application can know whether
> the file was created as "Foo" or "foo" or "FOO".
>
> If `directory-files' *can* properly return ("ChangeLog" "README"
> "configure"), rather than ("changelog" "readme" "configure") or
> ("CHANGELOG" "README" "CONFIGURE"), without having to read the user's
> mind (and without performance cost) then I think it should.
>
> ok, i see what you mean. i see that `readdir' for vms (in sysdep.c)
> does no case translation, and stepping through that function a few times
> in the debugger shows the filename to be upcased from the beginning. it
> looks like vms that i am using follows the last of the three models
> above.
In that case, it probably makes sense to keep all file names
upcased, indeed.
But that means that there is no way we can reliably use on Unix
a loaddefs.el generated on VMS. So I think the thing we should
do is use something like `file-name-equal' rather than string=.
Stefan
next prev parent reply other threads:[~2003-05-13 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 22:30 loaddefs.el filenames as seen by `update-file-autoloads' Thien-Thi Nguyen
2003-05-12 23:05 ` Stefan Monnier
2003-05-13 0:41 ` Thien-Thi Nguyen
2003-05-13 1:14 ` Stefan Monnier
2003-05-13 2:05 ` Miles Bader
2003-05-13 4:06 ` Thien-Thi Nguyen
2003-05-13 14:00 ` Stefan Monnier [this message]
2003-05-13 16:08 ` Thien-Thi Nguyen
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=200305131400.h4DE0sd6012045@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.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).