From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: Locking files for CLASH_DETECTION now supported on MS-Windows Date: Mon, 25 Feb 2013 10:05:42 -0800 Message-ID: <512BA7F6.4010304@cs.ucla.edu> References: <83wqtwi90o.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1361815566 6200 80.91.229.3 (25 Feb 2013 18:06:06 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 25 Feb 2013 18:06:06 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 25 19:06:29 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UA2RV-0005Fc-Fb for ged-emacs-devel@m.gmane.org; Mon, 25 Feb 2013 19:06:25 +0100 Original-Received: from localhost ([::1]:47258 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UA2RA-0002LV-L9 for ged-emacs-devel@m.gmane.org; Mon, 25 Feb 2013 13:06:04 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:38336) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UA2R4-0002Kl-IL for emacs-devel@gnu.org; Mon, 25 Feb 2013 13:06:02 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UA2R0-0003Mr-CT for emacs-devel@gnu.org; Mon, 25 Feb 2013 13:05:58 -0500 Original-Received: from smtp.cs.ucla.edu ([131.179.128.62]:59634) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UA2Qu-0003Kg-TR; Mon, 25 Feb 2013 13:05:49 -0500 Original-Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.cs.ucla.edu (Postfix) with ESMTP id D870D39E8108; Mon, 25 Feb 2013 10:05:47 -0800 (PST) X-Virus-Scanned: amavisd-new at smtp.cs.ucla.edu Original-Received: from smtp.cs.ucla.edu ([127.0.0.1]) by localhost (smtp.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cirAtxNSwmGz; Mon, 25 Feb 2013 10:05:47 -0800 (PST) Original-Received: from penguin.cs.ucla.edu (Penguin.CS.UCLA.EDU [131.179.64.200]) by smtp.cs.ucla.edu (Postfix) with ESMTPSA id 6FBFE39E8106; Mon, 25 Feb 2013 10:05:47 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130219 Thunderbird/17.0.3 In-Reply-To: <83wqtwi90o.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 131.179.128.62 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:157331 Archived-At: On 02/25/13 09:43, Eli Zaretskii wrote: > Trunk revision 111877 implements file locking and clash detection for > MS-Windows (see the node "Interlocking" in the Emacs manual for the > details), The MS-Windows code uses regular files while the GNUish code uses symbolic links. Suppose one instance of Emacs is running on a GNUish host while the other one is running on MS-Windows, and they are both accessing the same file via NFS. Won't that cause problems? The MS-Windows code will use a regular file .#FOO while the GNUish code is programmed to ignore locking for FOO if a regular file .#FOO exists (for compatibility with non-Emacs programs that use .#FOO for other purposes). Also, suppose an MS-Windows Emacs uses .#FOO as a lock file while a non-Emacs program uses .#FOO as a regular file for something else. Won't there be problems of a different sort?