unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: emacs-devel@gnu.org
Subject: Re: loaddefs.el filenames as seen by `update-file-autoloads'
Date: Mon, 12 May 2003 19:05:14 -0400	[thread overview]
Message-ID: <200305122305.h4CN5EGw009946@rum.cs.yale.edu> (raw)
In-Reply-To: E19FLo0-00086H-00@colo.agora-net.com

> under vms, filenames are case-insensitive and are upcased w/in emacs.

Any reason why it's upcased ?
Is it just the tradition under VMS ?  At least under Emacs, the tradition
is rather to use lowercase for most file names, so it would make more
sense to downcase (and most places where we want to ignore case, we
downcase rather than upcase, your code below being a prime example).

Also it would be better to do what W32 does: preserve capitalization.
Is that possible ?

>   (let ((load-name ...))
>     (when (memq system-type '(vax-vms vms
>                               ;; Add other systems whose filenames
>                               ;; are case insensitive and for which
>                               ;; `expand-file-name' DTRT, here.
> 			      ))
>       (setq load-name (downcase load-name)))
>     ...
>     (when (string= load-name ...) ...))

I'd rather use file-name-equal.

Admittedly, since loaddefs.el is still under CVS control and is hence
shared between all kinds of systems, it might be better to just systematically
downcase, independently from the system in use.

Hold it.  What about the file name in the (autoload ...) form ?
Since the `autoload' might be used on case-sensitive systems, it needs
to have the right capitalization (now there's an example where
preserving capitalization in filenames (even if you ignore it)
is beneficial).

> changing `load-name' instead of making the comparison case-insensitive
> means loaddefs.el will have lowercased frags (under vms), a change that
> is transparent to `expand-file-name'.  is this ok?  other ideas?

I don't understand your references to expand-file-name.
Could you lay out what you mean ?


	Stefan

  reply	other threads:[~2003-05-12 23:05 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 [this message]
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
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=200305122305.h4CN5EGw009946@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@rum.cs.yale.edu \
    --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).