unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@glug.org>
Cc: emacs-devel@gnu.org
Subject: Re: loaddefs.el filenames as seen by `update-file-autoloads'
Date: Tue, 13 May 2003 00:06:45 -0400	[thread overview]
Message-ID: <E19FR3t-0004v6-00@colo.agora-net.com> (raw)
In-Reply-To: <200305130114.h4D1EDBZ010190@rum.cs.yale.edu> (monnier+gnu/emacs@rum.cs.yale.edu)

   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.

   Why do you need to upcase in expand-file-name ?
   Isn't VMS happy either way ?

i don't know if it's necessary; perhaps for consistency?  after a while,
the "vms mindset" of upcase filenames is not as disturbing as initially.
what is more disturbing is the case folding for dcl command procedure
arguments, necessitating quoting, which has its own share of freaky and
baroque idiosyncrasies, but i digress...

   update-file-autoloads is not used exclusievly for lisp/loaddefs.el:
   it is also used by some outside elisp packages.  Admittedly, they
   probably also use lowercase filenames.

yeah, i have some familiarity from use in ttn-pers-elisp, although this
is the first time i've looked at the case issue.

   >   (expand-file-name "foo.el") => "AXPA:[TTN.EMACS.EMACS212_3]FOO.EL"

   Since VMS is case-insensitive, it would work just as well if
   expand-file-name returned "AXPA:[TTN.EMACS.EMACS212_3]FOO.EL".

i presume you mean "axpa:[ttn.emacs.emacs212_3]foo.el", as currently
`expand-file-name' does indeed upcase.

thi

  parent reply	other threads:[~2003-05-13  4:06 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 [this message]
2003-05-13 14:00         ` Stefan Monnier
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=E19FR3t-0004v6-00@colo.agora-net.com \
    --to=ttn@glug.org \
    --cc=emacs-devel@gnu.org \
    /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).