emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] trunk r116133: * doc/lispref/files.texi (File Locks): Ever


From: Glenn Morris
Subject: [Emacs-diffs] trunk r116133: * doc/lispref/files.texi (File Locks): Every platform supports locking now.
Date: Fri, 24 Jan 2014 03:52:05 +0000
User-agent: Bazaar (2.6b2)

------------------------------------------------------------
revno: 116133
revision-id: address@hidden
parent: address@hidden
committer: Glenn Morris <address@hidden>
branch nick: trunk
timestamp: Thu 2014-01-23 19:51:52 -0800
message:
  * doc/lispref/files.texi (File Locks): Every platform supports locking now.
modified:
  doc/lispref/ChangeLog          changelog-20091113204419-o5vbwnq5f7feedwu-6155
  doc/lispref/files.texi         files.texi-20091113204419-o5vbwnq5f7feedwu-6179
=== modified file 'doc/lispref/ChangeLog'
--- a/doc/lispref/ChangeLog     2014-01-22 08:30:00 +0000
+++ b/doc/lispref/ChangeLog     2014-01-24 03:51:52 +0000
@@ -1,3 +1,7 @@
+2014-01-24  Glenn Morris  <address@hidden>
+
+       * files.texi (File Locks): Every platform supports locking now.
+
 2014-01-22  Glenn Morris  <address@hidden>
 
        * display.texi (ImageMagick Images): Expand on image-format-suffixes.

=== modified file 'doc/lispref/files.texi'
--- a/doc/lispref/files.texi    2014-01-07 18:50:49 +0000
+++ b/doc/lispref/files.texi    2014-01-24 03:51:52 +0000
@@ -676,11 +676,12 @@
   When two users edit the same file at the same time, they are likely
 to interfere with each other.  Emacs tries to prevent this situation
 from arising by recording a @dfn{file lock} when a file is being
-modified.  (File locks are not implemented on Microsoft systems.)
+modified.
 Emacs can then detect the first attempt to modify a buffer visiting a
 file that is locked by another Emacs job, and ask the user what to do.
 The file lock is really a file, a symbolic link with a special name,
-stored in the same directory as the file you are editing.
+stored in the same directory as the file you are editing.  (On file
+systems that do not support symbolic links, a regular file is used.)
 
   When you access files using NFS, there may be a small probability that
 you and another user will both lock the same file ``simultaneously''.
@@ -719,11 +720,6 @@
 system does not support locking.
 @end defun
 
-  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}.  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
@@ -760,8 +756,7 @@
 @end itemize
 
 If you wish, you can replace the @code{ask-user-about-lock} function
-with your own version that makes the decision in another way.  The code
-for its usual definition is in @file{userlock.el}.
+with your own version that makes the decision in another way.
 @end defun
 
 @node Information about Files


reply via email to

[Prev in Thread] Current Thread [Next in Thread]