From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Proposed patch: allow user to disable lockfile creation Date: Fri, 29 Jul 2011 19:40:30 -0400 Message-ID: References: <87ei1bqi8p.fsf@uwakimon.sk.tsukuba.ac.jp> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: dough.gmane.org 1311982841 20775 80.91.229.12 (29 Jul 2011 23:40:41 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 29 Jul 2011 23:40:41 +0000 (UTC) Cc: johnw@newartisans.com, theophilusx@gmail.com, lennart.borgman@gmail.com, emacs-devel@gnu.org, schwab@linux-m68k.org, stephen@xemacs.org To: Dave Abrahams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jul 30 01:40:36 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1QmwfT-0005Fs-Rv for ged-emacs-devel@m.gmane.org; Sat, 30 Jul 2011 01:40:35 +0200 Original-Received: from localhost ([::1]:37573 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QmwfT-00081x-DO for ged-emacs-devel@m.gmane.org; Fri, 29 Jul 2011 19:40:35 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:37214) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QmwfQ-00081q-Ly for emacs-devel@gnu.org; Fri, 29 Jul 2011 19:40:33 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QmwfP-00025K-EL for emacs-devel@gnu.org; Fri, 29 Jul 2011 19:40:32 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]:46025) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QmwfP-00025F-BM for emacs-devel@gnu.org; Fri, 29 Jul 2011 19:40:31 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1QmwfO-0003wZ-Fv; Fri, 29 Jul 2011 19:40:30 -0400 In-reply-to: (message from Dave Abrahams on Thu, 28 Jul 2011 20:51:41 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 140.186.70.10 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:142500 Archived-At: It's actually more than that. The scheme is simultaneously over-cautious and yet full of holes. So what? It still does a very useful job, providing advance warning about simultaneous editing in many cases. It's predicated on the idea that everybody who might touch the file simultaneously is using Emacs, No such assumption is made, because Emacs does not depend on this feature to function every time. The advance warning feature functions if the other person uses Emacs. That's better than nothing. Furthermore, Emacs is perfectly capable of telling me when that has happened before I save... at least it seems to work pretty darned reliably. That is why the advance warning feature does not need to be 100% dependable. It is an added convenience. It is convenient to get the warning before you start editing, rather than only when you try to save the file. -- Dr Richard Stallman President, Free Software Foundation 51 Franklin St Boston MA 02110 USA www.fsf.org www.gnu.org Skype: No way! That's nonfree (freedom-denying) software. Use free telephony http://directory.fsf.org/category/tel/