[Emacs-diffs] /srv/bzr/emacs/trunk r108180: Document new create-lockfiles option

[Glenn Morris]

------------------------------------------------------------
revno: 108180
committer: Glenn Morris <address@hidden>
branch nick: trunk
timestamp: Wed 2012-05-09 20:58:16 -0400
message:
  Document new create-lockfiles option
modified:
  doc/emacs/ChangeLog
  doc/emacs/files.texi
  doc/lispref/ChangeLog
  doc/lispref/files.texi
  etc/NEWS

=== modified file 'doc/emacs/ChangeLog'
--- a/doc/emacs/ChangeLog       2012-05-09 03:30:51 +0000
+++ b/doc/emacs/ChangeLog       2012-05-10 00:58:16 +0000
@@ -1,3 +1,7 @@
+2012-05-10  Glenn Morris  <address@hidden>
+
+       * files.texi (Interlocking): Mention create-lockfiles option.
+
 2012-05-09  Chong Yidong  <address@hidden>
 
        * frames.texi (Mouse References, Mouse Commands): Fix index

=== modified file 'doc/emacs/files.texi'
--- a/doc/emacs/files.texi      2012-04-26 00:31:47 +0000
+++ b/doc/emacs/files.texi      2012-05-10 00:58:16 +0000
@@ -739,6 +739,11 @@
 idea is that the file is locked whenever an Emacs buffer visiting it
 has unsaved changes.
 
address@hidden create-lockfiles
+  You can prevent the creation of lock files by setting the variable
address@hidden 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

=== modified file 'doc/lispref/ChangeLog'
--- a/doc/lispref/ChangeLog     2012-05-09 03:30:51 +0000
+++ b/doc/lispref/ChangeLog     2012-05-10 00:58:16 +0000
@@ -1,3 +1,7 @@
+2012-05-10  Glenn Morris  <address@hidden>
+
+       * files.texi (File Locks): Mention create-lockfiles option.
+
 2012-05-09  Glenn Morris  <address@hidden>
 
        * vol1.texi, vol2.texi: Remove files.

=== modified file 'doc/lispref/files.texi'
--- a/doc/lispref/files.texi    2012-05-02 07:20:29 +0000
+++ b/doc/lispref/files.texi    2012-05-10 00:58:16 +0000
@@ -726,7 +726,12 @@
 
   File locking is not supported on some systems.  On systems that do not
 support it, the functions @code{lock-buffer}, @code{unlock-buffer} and
address@hidden do nothing and return @code{nil}.
address@hidden do nothing and return @code{nil}.  It is also
+possible to disable locking, by setting the variable @code{create-lockfiles}.
+
address@hidden create-lockfiles
+If this variable is @code{nil}, Emacs does not lock files.
address@hidden defopt
 
 @defun ask-user-about-lock file other-user
 This function is called when the user tries to modify @var{file}, but it

=== modified file 'etc/NEWS'
--- a/etc/NEWS  2012-05-09 08:33:48 +0000
+++ b/etc/NEWS  2012-05-10 00:58:16 +0000
@@ -65,6 +65,10 @@
 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.