Document new create-lockfiles option

diff --git a/doc/emacs/ChangeLog b/doc/emacs/ChangeLog
index 80d9381ec42e2ad732b0878e6ae1f0b2d9b46a5c..95db71940538e0fb0635fa4c86992e78927f5274 100644 (file)
--- a/doc/emacs/ChangeLog
+++ b/doc/emacs/ChangeLog
@@ -1,3 +1,7 @@
+2012-05-10  Glenn Morris  <rgm@gnu.org>
+
+       * files.texi (Interlocking): Mention create-lockfiles option.
+
 2012-05-09  Chong Yidong  <cyd@gnu.org>
 
        * frames.texi (Mouse References, Mouse Commands): Fix index

diff --git a/doc/emacs/files.texi b/doc/emacs/files.texi
index 31883a1f5ccd61ce80b784d9e4113a0f9c123d22..088c3ce29a74ce9e5d74fdc4e3d5283453355df0 100644 (file)
--- a/doc/emacs/files.texi
+++ b/doc/emacs/files.texi
@@ -739,6 +739,11 @@ directory.)  Emacs removes the lock when you save the changes.  The
 idea is that the file is locked whenever an Emacs buffer visiting it
 has unsaved changes.
 
+@vindex create-lockfiles
+  You can prevent the creation of lock files by setting the variable
+@code{create-lockfiles} to @code{nil}.  @strong{Caution:} by
+doing so you will lose the benefits that this feature provides.
+
 @cindex collision
   If you begin to modify the buffer while the visited file is locked by
 someone else, this constitutes a @dfn{collision}.  When Emacs detects a

diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog
index 1b9fa0991e424b23964d953c865c1c51a7e38bef..2967e644558d4194f60cd3c8829d72919f08c304 100644 (file)
--- a/doc/lispref/ChangeLog
+++ b/doc/lispref/ChangeLog
@@ -1,3 +1,7 @@
+2012-05-10  Glenn Morris  <rgm@gnu.org>
+
+       * files.texi (File Locks): Mention create-lockfiles option.
+
 2012-05-09  Glenn Morris  <rgm@gnu.org>
 
        * vol1.texi, vol2.texi: Remove files.

diff --git a/doc/lispref/files.texi b/doc/lispref/files.texi
index 1756e56bd2afedc03e6bb71879eacc3b9a834529..2ee80504b60ff397cf2c730a38b5f4381c901d02 100644 (file)
--- a/doc/lispref/files.texi
+++ b/doc/lispref/files.texi
@@ -726,7 +726,12 @@ system does not support locking.
 
   File locking is not supported on some systems.  On systems that do not
 support it, the functions @code{lock-buffer}, @code{unlock-buffer} and
-@code{file-locked-p} do nothing and return @code{nil}.
+@code{file-locked-p} do nothing and return @code{nil}.  It is also
+possible to disable locking, by setting the variable @code{create-lockfiles}.
+
+@defopt create-lockfiles
+If this variable is @code{nil}, Emacs does not lock files.
+@end defopt
 
 @defun ask-user-about-lock file other-user
 This function is called when the user tries to modify @var{file}, but it

diff --git a/etc/NEWS b/etc/NEWS
index 921f44bbcce424f0c65fdddf0f363548123519bc..0726b091989abc67c08328b5301a1c9ed4975b41 100644 (file)
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -65,6 +65,10 @@ ImageMagick to view images, set
 frames, if emacsclient is only told to open a new frame without
 specifying any file to visit or expression to evaluate.
 
++++
+** You can prevent the creation of lock files by setting `create-lockfiles'
+to nil.  Use with caution, and only if you really need to.
+
 ** Using "unibyte: t" in Lisp source files is obsolete.
 Use "coding: raw-text" instead.