From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel 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 Message-ID: References: <877igvl4dn.fsf@stupidchicken.com> <85oda71exn.fsf@lola.goethe.zz> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1203826619 8725 80.91.229.12 (24 Feb 2008 04:16:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 24 Feb 2008 04:16:59 +0000 (UTC) Cc: cyd@stupidchicken.com, emacs-devel@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Feb 24 05:17:23 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JT8Ik-0005dP-FY for ged-emacs-devel@m.gmane.org; Sun, 24 Feb 2008 05:17:22 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JT8IE-0003g8-Vg for ged-emacs-devel@m.gmane.org; Sat, 23 Feb 2008 23:16:51 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JT8IA-0003e2-Mq for emacs-devel@gnu.org; Sat, 23 Feb 2008 23:16:46 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JT8I8-0003aP-5O for emacs-devel@gnu.org; Sat, 23 Feb 2008 23:16:45 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JT8I8-0003aH-1k for emacs-devel@gnu.org; Sat, 23 Feb 2008 23:16:44 -0500 Original-Received: from nitzan.inter.net.il ([213.8.233.22]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JT8I3-0002Pe-Vm; Sat, 23 Feb 2008 23:16:40 -0500 Original-Received: from HOME-C4E4A596F7 (IGLD-84-229-200-132.inter.net.il [84.229.200.132]) by nitzan.inter.net.il (MOS 3.7.3a-GA) with ESMTP id JGV27871 (AUTH halo1); Sun, 24 Feb 2008 06:14:11 +0200 (IST) In-reply-to: <85oda71exn.fsf@lola.goethe.zz> (message from David Kastrup on Sat, 23 Feb 2008 23:33:08 +0100) X-detected-kernel: by monty-python.gnu.org: FreeBSD 4.7-5.2 (or MacOS X 10.2-10.4) (2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:90204 Archived-At: > From: David Kastrup > Cc: Chong Yidong , 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.