From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: find-library-name fails if file (with no extension) exists. Date: Wed, 22 Nov 2006 01:59:15 +0100 Message-ID: <4563A0E3.9050103@student.lu.se> References: <8764d8u085.fsf@pacem.orebokech.com> <85lkm4zbfa.fsf@lola.goethe.zz> <854pssz8u7.fsf@lola.goethe.zz> <45638B07.2090201@student.lu.se> <85wt5oxtly.fsf@lola.goethe.zz> <456396EA.9030207@student.lu.se> <857ixoxq6e.fsf@lola.goethe.zz> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1164157184 3153 80.91.229.2 (22 Nov 2006 00:59:44 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 22 Nov 2006 00:59:44 +0000 (UTC) Cc: Juanma Barranquero , Emacs Devel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Nov 22 01:59:41 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1GmgSd-00009b-EA for ged-emacs-devel@m.gmane.org; Wed, 22 Nov 2006 01:59:35 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GmgSc-0002Cu-Rn for ged-emacs-devel@m.gmane.org; Tue, 21 Nov 2006 19:59:34 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GmgSP-00028m-D6 for emacs-devel@gnu.org; Tue, 21 Nov 2006 19:59:21 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GmgSO-000269-6t for emacs-devel@gnu.org; Tue, 21 Nov 2006 19:59:20 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GmgSN-00025z-Vc for emacs-devel@gnu.org; Tue, 21 Nov 2006 19:59:20 -0500 Original-Received: from [80.76.149.212] (helo=ch-smtp01.sth.basefarm.net) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1GmgSM-0000IZ-Cz; Tue, 21 Nov 2006 19:59:18 -0500 Original-Received: from c83-254-145-24.bredband.comhem.se ([83.254.145.24]:62025 helo=[192.168.123.121]) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.63) (envelope-from ) id 1GmgSK-0002H0-3H; Wed, 22 Nov 2006 01:59:16 +0100 User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) Original-To: David Kastrup In-Reply-To: <857ixoxq6e.fsf@lola.goethe.zz> X-Scan-Result: No virus found in message 1GmgSK-0002H0-3H. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1GmgSK-0002H0-3H 25ee8f8a6de6f55cf13a1745e1e23250 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:62632 Archived-At: David Kastrup wrote: > Lennart Borgman writes: > >> David Kastrup wrote: >> >>> It is not even possible to write code with a reasonable chance of >>> working reliably since one can have Windows and Unix file systems on >>> the same system and export either with Samba or NFS or a number of >>> other ways. >> If (a very big IF perhaps) Samba, NFS etc preserves the case of file >> names in each export and the software is written with the possibility >> of both case sensitive and case insensitive file systems in mind it >> seems possible to me. >> >> Or am I missing something there? > > You can't decide that two file names might indicate the same file > without doing an actual file operation. You can't decide whether > writing a file would conflict with an existing file without actually > doing the write (and asking the operating system to fail in case the > file exists). You can't really base any decision on existing file > names. As a rule of thumb, if there is a possibility for a race > condition, there is a possibility for filename aliasing trouble. And > not every potential race condition is a problem. > > Things like file name completion are simply something which is > impossible to get right. But does not that depend on the use of file names? If file names are choosen so that they work on both case insensitive and case sensitive system are there then any problems? At least that has been the problem in the cases I have seen. Most often the problem has actually been that someone writing on a case sensitive file system forgot to take care of this. (That is of course an easy mistake to make.) I am aware of the cases you mentioned to Juanma where there really are no way to do lowercase/uppercase certain letters. Could not they be handled (and are they not already handled) as different letters even though they outside the computer world may look at uppercase/lowercase variants of the same letter?