From: Eli Zaretskii <eliz@gnu.org>
To: David Kastrup <dak@gnu.org>
Cc: cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: [gmane.emacs.bugs] Emacs fails to start properly if the current working directory is on a vfat or ntfs filesystem
Date: Sun, 24 Feb 2008 06:16:37 +0200 [thread overview]
Message-ID: <ulk5bm1ju.fsf@gnu.org> (raw)
In-Reply-To: <85oda71exn.fsf@lola.goethe.zz> (message from David Kastrup on Sat, 23 Feb 2008 23:33:08 +0100)
> From: David Kastrup <dak@gnu.org>
> Cc: Chong Yidong <cyd@stupidchicken.com>, emacs-devel@gnu.org
> Date: Sat, 23 Feb 2008 23:33:08 +0100
>
> A similar problem would be filename completion. We have separate code
> paths for that in Windows/Unix I believe, even though on MacOSX, the
> file system tends to be case insensitive, too (and normalizing utf-8
> composed characters in some manner).
>
> If we could design some sort of system call sequence that worked out
> insensitivity/normalizing agnostic, this would mean that on a typical
> GNU/Linux system which can mount various foreign file system types,
> everything would work out according to expectations.
>
> That would seem to be preferable to #ifdef and its ilk. I think,
> however, that stuff like the "\\" directory separator can be system
> rather than file system dependent.
I believe you are talking about expand-file-name, because
file_name_completion is almost devoid of OS-dependent #ifdef's.
As for expand-file-name, the #ifdef's there are mostly due to the
different semantics of file names: backslashes and drive letters, and
also to the fact that ~user is not supported. Most of these will have
to stay OS-dependent, I think.
next prev parent reply other threads:[~2008-02-24 4:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 22:00 [gmane.emacs.bugs] Emacs fails to start properly if the current working directory is on a vfat or ntfs filesystem Chong Yidong
2008-02-23 22:22 ` Eli Zaretskii
2008-02-23 22:30 ` Chong Yidong
2008-02-23 22:33 ` David Kastrup
2008-02-24 4:16 ` Eli Zaretskii [this message]
2008-02-24 14:36 ` Jason Rumney
2008-02-24 15:39 ` Stefan Monnier
2008-02-24 15:44 ` Miles Bader
2008-02-24 16:01 ` Jason Rumney
2008-02-24 19:44 ` Eli Zaretskii
2008-02-24 20:41 ` Stefan Monnier
2008-02-25 10:57 ` Richard Stallman
2008-02-25 15:57 ` Stefan Monnier
2008-02-26 12:36 ` Richard Stallman
2008-02-24 19:43 ` Eli Zaretskii
2008-02-24 23:04 ` Richard Stallman
2008-02-24 23:44 ` Jason Rumney
2008-02-25 19:01 ` Richard Stallman
2008-02-25 23:58 ` Jason Rumney
2008-02-26 1:57 ` Stefan Monnier
2008-02-26 3:41 ` Chong Yidong
2008-02-26 4:53 ` Stefan Monnier
2008-02-26 9:07 ` Jason Rumney
2008-02-26 9:39 ` Jason Rumney
2008-02-26 15:18 ` Stefan Monnier
2008-02-24 22:30 ` Richard Stallman
2008-02-24 15:23 ` Richard Stallman
2008-02-24 20:01 ` Eli Zaretskii
2008-02-25 10:57 ` Richard Stallman
2008-02-25 20:04 ` Eli Zaretskii
2008-02-25 20:52 ` Andreas Schwab
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=ulk5bm1ju.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=dak@gnu.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 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.