From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Locking files for CLASH_DETECTION now supported on MS-Windows Date: Mon, 25 Feb 2013 15:35:24 -0500 Message-ID: References: <83wqtwi90o.fsf@gnu.org> <512BA7F6.4010304@cs.ucla.edu> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1361824541 913 80.91.229.3 (25 Feb 2013 20:35:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 25 Feb 2013 20:35:41 +0000 (UTC) Cc: Eli Zaretskii , emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 25 21:36:03 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 1UA4mC-0007g7-IM for ged-emacs-devel@m.gmane.org; Mon, 25 Feb 2013 21:35:56 +0100 Original-Received: from localhost ([::1]:60899 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UA4lr-0007hz-IR for ged-emacs-devel@m.gmane.org; Mon, 25 Feb 2013 15:35:35 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:55815) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UA4lo-0007eC-TH for emacs-devel@gnu.org; Mon, 25 Feb 2013 15:35:34 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UA4ln-0001Vy-4J for emacs-devel@gnu.org; Mon, 25 Feb 2013 15:35:32 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.182]:61198) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UA4ll-0001UL-CA; Mon, 25 Feb 2013 15:35:29 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av8EABK/CFHO+KLv/2dsb2JhbABEDr8AF3OCHgEBBAFWIwULCzQSFBgNEAETiB4GwS2NBYQFA4hhlnuFHoFegjlcgVE X-IPAS-Result: Av8EABK/CFHO+KLv/2dsb2JhbABEDr8AF3OCHgEBBAFWIwULCzQSFBgNEAETiB4GwS2NBYQFA4hhlnuFHoFegjlcgVE X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="2430540" Original-Received: from 206-248-162-239.dsl.teksavvy.com (HELO pastel.home) ([206.248.162.239]) by ironport2-out.teksavvy.com with ESMTP/TLS/ADH-AES256-SHA; 25 Feb 2013 15:35:24 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id EA5506C0A9; Mon, 25 Feb 2013 15:35:24 -0500 (EST) In-Reply-To: <512BA7F6.4010304@cs.ucla.edu> (Paul Eggert's message of "Mon, 25 Feb 2013 10:05:42 -0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.182 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:157339 Archived-At: > 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? I wouldn't worry about it, no. The example would be less hypothetical if you used SMB rather than NFS, but even so, in the worst case one of the machines will disable the file-lock-checks, which is no worse than what we had before (where the Windows machine had the file-lock-checks disabled). A much more likely scenario is to see users complain/worry on gnu.emacs.help about weird files appearing on their systems, then discovering that come from their new Emacs, and finally asking how to get rid of "this stupid new feature". Stefan