| blob | 3439b354b24a838e6be53c6f52e3db0d2845c467 |
1 ;;; vc.el --- drive a version-control system from within Emacs
3 ;; Copyright (C) 1992, 1993 Free Software Foundation, Inc.
5 ;; Author: Eric S. Raymond <esr@snark.thyrsus.com>
6 ;; Version: 5.4
8 ;; This file is part of GNU Emacs.
10 ;; GNU Emacs is free software; you can redistribute it and/or modify
11 ;; it under the terms of the GNU General Public License as published by
12 ;; the Free Software Foundation; either version 2, or (at your option)
13 ;; any later version.
15 ;; GNU Emacs is distributed in the hope that it will be useful,
16 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
17 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
18 ;; GNU General Public License for more details.
20 ;; You should have received a copy of the GNU General Public License
21 ;; along with GNU Emacs; see the file COPYING. If not, write to
22 ;; the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA.
24 ;;; Commentary:
26 ;; This mode is fully documented in the Emacs user's manual.
27 ;;
28 ;; This was designed and implemented by Eric Raymond <esr@snark.thyrsus.com>.
29 ;; Paul Eggert <eggert@twinsun.com>, Sebastian Kremer <sk@thp.uni-koeln.de>,
30 ;; and Richard Stallman contributed valuable criticism, support, and testing.
31 ;;
32 ;; Supported version-control systems presently include SCCS and RCS;
33 ;; your RCS version should be 5.6.2 or later for proper operation of
34 ;; the lock-breaking code.
35 ;;
36 ;; The RCS code assumes strict locking. You can support the RCS -x option
37 ;; by adding pairs to the vc-master-templates list.
38 ;;
39 ;; Proper function of the SCCS diff commands requires the shellscript vcdiff
40 ;; to be installed somewhere on Emacs's path for executables.
41 ;;
42 ;; If your site uses the ChangeLog convention supported by Emacs, the
43 ;; function vc-comment-to-change-log should prove a useful checkin hook.
44 ;;
45 ;; This code depends on call-process passing back the subprocess exit
46 ;; status. Thus, you need Emacs 18.58 or later to run it. For the
47 ;; vc-directory command to work properly as documented, you need 19.
48 ;; You also need Emacs 19's ring.el.
49 ;;
50 ;; The vc code maintains some internal state in order to reduce expensive
51 ;; version-control operations to a minimum. Some names are only computed
52 ;; once. If you perform version control operations with RCS/SCCS/CVS while
53 ;; vc's back is turned, or move/rename master files while vc is running,
54 ;; vc may get seriously confused. Don't do these things!
55 ;;
56 ;; Developer's notes on some concurrency issues are included at the end of
57 ;; the file.
59 ;;; Code:
67 minor-mode-alist)))
69 ;; General customization
72 "*Back-end actually used by this interface; may be SCCS or RCS.
94 ;;; This is duplicated in diff.el.
98 ;;;###autoload
102 ;; Header-insertion hair
110 "*Associate static header string templates with file types. A \%s in the
111 template is replaced with the first string associated with the file's
116 "*Special comment delimiters to be used in generating vc headers only.
117 Add an entry in this list if you need to override the normal comment-start
118 and comment-end variables. This will only be necessary if the mode language
121 ;; Default is to be extra careful for super-user.
123 "*Non-nil means be extra-careful in checkout.
124 Verify that the file really is not locked
127 ;; Variables the user doesn't need to know about.
147 ;; File property caching
150 ;; clear all properties of a given file
154 "Clear all cached file properties and the comment ring."
157 ;; Note: there is potential for minor lossage here if there is an open
158 ;; log buffer with a nonzero local value of vc-comment-ring-index.
161 ;; Random helper functions
171 "Look for a command anywhere on the subprocess-command search path."
184 exec-path)
185 nil)))
188 "Execute a version-control command, notifying user and checking for errors.
189 The command is successful if its exit status does not exceed OKSTATUS.
190 Output from COMMAND goes to buffer *vc*. The last argument of the command is
191 the master name of FILE; this is appended to an optional list of FLAGS."
198 status)
206 ;; This is so that command arguments typed in the *vc* buffer will
207 ;; have reasonable defaults.
212 flags)
228 status))
229 )
232 )
234 status)
235 )
237 ;;; Save a bit of the text around POSN in the current buffer, to help
238 ;;; us find the corresponding position again later. This works even
239 ;;; if all markers are destroyed or corrupted.
246 ;;; Return the position of CONTEXT in the current buffer, or nil if we
247 ;;; couldn't find it.
257 ;; Can't use search-backward since the match may continue
258 ;; after point.
260 ;; goto-char doesn't signal an error at
261 ;; beginning of buffer like backward-char would
263 ;; to beginning of OSTRING
267 ;; Most of this was shamelessly lifted from Sebastian Kremer's rcs.el mode.
268 ;; Revert buffer, try to keep point and mark where user expects them in spite
269 ;; of changes because of expanded version-control key words.
270 ;; This is quite important since otherwise typeahead won't work as expected.
274 ;; Use mark-marker to avoid confusion in transient-mark-mode.
277 ;; Make the right thing happen in transient-mark-mode.
279 ;; We may want to reparse the compilation buffer after revert
282 ;; Construct a list; each elt is nil or a buffer
283 ;; iff that buffer is a compilation output buffer
284 ;; that contains markers into the current buffer.
290 compilation-old-error-list
291 compilation-error-list))
304 ;; the actual revisit
307 ;; Reparse affected compilation buffers.
313 ;; Record the position in the compilation buffer of
314 ;; the last error next-error went to.
317 ;; Reparse the error messages as far as they were parsed before.
319 ;; Move the pointer up to find the error we were at before
320 ;; reparsing. Now next-error should properly go to the next one.
326 ;; Restore point and mark
335 ;; Make sure the current buffer and its working file are in sync
336 ;; NOT-URGENT means it is ok to continue if the user says not to save.
342 nil
347 ;; Has the given workfile changed since last checkout?
354 ;; 0 stands for an unknown time; it can't match any mod time.
356 unchanged)))))
359 ;;; If comment is specified, it will be used as an admin or checkin comment.
363 ;; if there is no master file corresponding, create one
371 ;; if there is no lock on the file, assert one and get it
379 file))
390 )
393 ;; a checked-out version exists, but the user may not own the lock
398 file
400 owner))
402 ;; OK, user owns the lock on the file
406 ;; give luser a chance to save before checking in.
409 ;; Revert if file is unchanged and buffer is too.
410 ;; If buffer is modified, that means the user just said no
411 ;; to saving it; in that case, don't revert,
412 ;; because the user might intend to save
413 ;; after finishing the log entry.
418 ;; DO NOT revert the file without asking the user!
421 ;; user may want to set nonstandard parameters
425 ;; OK, let's do the checkin
427 )))))
430 ;; We've accepted a log comment, now do a vc-next-action using it on all
431 ;; marked files.
439 nil t)
440 )
442 ;; Here's the major entry point.
444 ;;;###autoload
446 "Do the next logical checkin or checkout operation on the current file.
447 If the file is not already registered, this registers it for version
448 control and then retrieves a writable, locked copy for editing.
449 If the file is registered and not locked by anyone, this checks out
450 a writable and locked file ready for editing.
451 If the file is checked out and locked by the calling user, this
452 first checks to see if the file has changed since checkout. If not,
453 it performs a revert.
454 If the file has been changed, this pops up a buffer for entry
455 of a log message; when the message has been entered, it checks in the
456 resulting changes along with the log message as change commentary. If
457 the variable `vc-keep-workfiles' is non-nil (which is its default), a
458 read-only copy of the changed file is left in place afterwards.
459 If the file is registered and locked by someone else, you are given
460 the option to steal the lock.
461 If you call this from within a VC dired buffer with no files marked,
462 it will operate on the file in the current line.
463 If you call this from within a VC dired buffer, and one or more
464 files are marked, it will accept a log message and then operate on
465 each one. The log message will be used as a comment for any register
466 or checkin operations, but ignored when doing checkouts. Attempted
467 lock steals will raise an error.
469 For checkin, a prefix argument lets you specify the version number to use."
477 "Enter a change comment for the marked files."
486 ;;; These functions help the vc-next-action entry point
489 "Retrieve a writable copy of the latest version of the current buffer's file."
491 )
493 ;;;###autoload
495 "Register the current file into your version-control system."
499 ;; Watch out for new buffers of size 0: the corresponding file
500 ;; does not exist yet, even though buffer-modified-p is nil.
507 buffer-file-name
511 )
514 ;; If the given file is in the current buffer,
515 ;; either revert on it so we see expanded keyworks,
516 ;; or unvisit it (depending on vc-keep-workfiles)
517 ;; NOQUERY if non-nil inhibits confirmation for reverting.
518 ;; NOQUERY should be t *only* if it is known the only difference
519 ;; between the buffer and the file is due to RCS rather than user editing!
530 ;; Accept a comment for an operation on FILE revision REV. If COMMENT
531 ;; is nil, pop up a VC-log buffer, emit MSG, and set the
532 ;; action on close to ACTION; otherwise, do action immediately.
533 ;; Remember the file's buffer in parent-buffer (current one if no file).
556 "Check a file into your version-control system.
557 FILE is the unmodified name of the file. REV should be the base version
558 level to check it in under. COMMENT, if specified, is the checkin comment."
564 "Retrieve a copy of the latest version of the given file."
565 ;; If ftp is on this system and the name matches the ange-ftp format
566 ;; for a remote file, the user is trying something that won't work.
572 )
575 "Steal the lock on the current workfile."
595 ;; This is called when the notification has been sent.
601 "Check in the file specified by FILE.
602 The optional argument REV may be a string specifying the new version level
603 \(if nil increment the current level). The file is either retained with write
604 permissions zeroed, or deleted (according to the value of `vc-keep-workfiles').
605 COMMENT is a comment string; if omitted, a buffer is
606 popped up to accept a comment."
610 ;;; Here is a checkin hook that may prove useful to sites using the
611 ;;; ChangeLog facility supported by Emacs.
613 "Enter last VC comment into change log file for current buffer's file.
614 Optional arg (interactive prefix) non-nil means prompt for user name and site.
615 Second arg is file name of change log. \
616 If nil, uses `change-log-default-name'."
622 ;; Don't let add-change-log-entry insert a defun name.
624 end)
625 ;; Call add-log to do half the work.
627 ;; Insert the VC comment, leaving point before it.
630 ;; It starts with an open-paren, as in "(foo): Frobbed."
631 ;; So remove the ": " add-log inserted.
633 ;; Canonicalize the white space between the file name and comment.
635 ;; Indent rest of the text the same way add-log indented the first line.
642 ;; Fill the inserted text, preserving open-parens at bol.
647 ;; Canonicalize the white space at the end of the entry so it is
648 ;; separated from the next entry by a single blank line.
656 "Complete the operation implied by the current log entry."
658 ;; Check and record the comment, if any.
664 ;; Comment too long?
666 ;; Record the comment in the comment ring
670 ))
671 ;; Sync parent buffer in case the user modified it while editing the comment.
675 ;; OK, do it to it
679 vc-log-file
680 vc-log-version
683 ;; Return to "parent" buffer of this checkin and remove checkin window
688 ;; Now make sure we see the expanded headers
693 ;; Code for access to the comment ring
696 "Cycle backwards through comment history."
704 ;; Initialize the index on the first use of this command
705 ;; so that the first M-p gets index 0, and the first M-n gets
706 ;; index -1.
717 "Cycle forwards through comment history."
722 "Searches backwards through comment history for substring match."
739 "Searches forwards through comment history for substring match."
755 ;; Additional entry points for examining version histories
757 ;;;###autoload
759 "Display diffs between file versions.
760 Normally this compares the current file and buffer with the most recent
761 checked in version of that file. This uses no arguments.
762 With a prefix argument, it reads the file name to use
763 and two version designators specifying which versions to compare."
775 unchanged)
783 ;; Ideally, we'd like at this point to parse the diff so that
784 ;; the buffer effectively goes into compilation mode and we
785 ;; can visit the old and new change locations via next-error.
786 ;; Unfortunately, this is just too painful to do. The basic
787 ;; problem is that the `old' file doesn't exist to be
788 ;; visited. This plays hell with numerous assumptions in
789 ;; the diff.el and compile.el machinery.
801 "For FILE, report diffs between two stored versions REL1 and REL2 of it.
802 If FILE is a directory, generate diffs between versions for all registered
803 files in or below it."
816 " and "
829 )))
834 )
839 ;;;###autoload
841 "Visit version REV of the current buffer in another window.
842 If the current buffer is named `F', the version is named `F.~REV~'.
843 If `F.~REV~' already exists, it is used instead of being re-created."
852 rev))
859 ;; Header-insertion code
861 ;;;###autoload
863 "Insert headers in a file for use with your version-control system.
864 Headers desired are inserted at the start of the buffer, and are pulled from
865 the variable `vc-header-alist'."
884 hdstrings)
889 vc-static-header-alist))
890 )
891 )))))
893 ;; The VC directory submode. Coopt Dired for this.
894 ;; All VC commands get mapped into logical equivalents.
903 minor-mode-map-alist)))
906 "The augmented Dired minor mode used in VC directory buffers.
907 All Dired commands operate normally. Users currently locking listed files
908 are listed in place of the file's owner and group.
909 Keystrokes bound to VC commands will execute as though they had been called
910 on a buffer attached to the file named in the current Dired buffer line."
915 ;; Hack a directory-listing line, plugging in locking-user info in
916 ;; place of the user and group info. Should have the beneficial
917 ;; side-effect of shortening the listing line. Each call starts with
918 ;; point immediately following the dired mark area on the line to be
919 ;; hacked.
920 ;;
921 ;; Simplest possible one:
922 ;; (insert (concat x "\t")))
923 ;;
924 ;; This code, like dired, assumes UNIX -l format.
930 )
932 ;;; Note in Emacs 18 the following defun gets overridden
933 ;;; with the symbol 'vc-directory-18. See below.
934 ;;;###autoload
936 "Show version-control status of all files under the current directory."
941 dired-buf
942 dired-buf-mod-count)
951 ;; This uses a semi-documented feature of dired; giving a switch
952 ;; argument forces the buffer to refresh each time.
955 dired-listing-switches)
974 )
977 ))
979 ;; Emacs 18 version
981 "Show version-control status of all files under the current directory."
1004 )
1009 ; Emacs 18 also lacks these.
1013 ;; Named-configuration support for SCCS
1022 ))
1028 ;; (replace-regexp (concat ":" (regexp-quote file) "$") (concat ":" newname))
1033 ))
1036 ;; Return the numeric version corresponding to a named snapshot of file
1037 ;; If name is nil or a version number string it's just passed through
1041 name)
1046 )))
1048 ;; Named-configuration entry points
1051 ;; Return an example of why the current directory is not ready to be snapshot
1052 ;; or nil if no such example exists.
1058 nil))
1060 ;;;###autoload
1062 "Make a snapshot called NAME.
1063 The snapshot is made from all registered files at or below the current
1064 directory. For each file, the version level of its latest
1065 version becomes part of the named configuration."
1074 )))
1076 ;;;###autoload
1078 "Retrieve the snapshot called NAME.
1079 This function fails if any files are locked at or below the current directory
1080 Otherwise, all registered files are checked out (unlocked) at their version
1081 levels in the snapshot."
1091 )))
1093 ;; Miscellaneous other entry points
1095 ;;;###autoload
1097 "List the change log of the current buffer in a window."
1114 )
1116 )
1117 )
1119 ;;;###autoload
1121 "Revert the current buffer's file back to the latest checked-in version.
1122 This asks for confirmation if the buffer contents are not identical
1123 to that version."
1141 )
1142 )
1144 ;;;###autoload
1146 "Get rid of most recently checked in version of this file.
1147 A prefix argument means do not revert the buffer afterwards."
1156 "Remove your version %s from master? "
1159 nil
1165 ))
1168 "Rename file OLD to NEW, and rename its master file likewise."
1183 ;; This had FILE, I changed it to OLD. -- rms.
1187 oldmaster
1201 vc-master-templates)
1205 ; ?? Renaming a file might change its contents due to keyword expansion.
1206 ; We should really check out a new copy if the old copy was precisely equal
1207 ; to some checked in version. However, testing for this is tricky....
1213 ;; This had FILE, I changed it to OLD. -- rms.
1216 nil)
1217 )
1219 ;;;###autoload
1221 "Find change log file and add entries from recent RCS logs.
1222 The mark is left at the end of the text prepended to the change log.
1223 With prefix arg of C-u, only find log entries for the current buffer's file.
1224 With any numeric prefix arg, find log entries for all files currently visited.
1225 Otherwise, find log entries for all registered files in the default directory.
1226 From a program, any arguments are passed to the `rcs2log' script."
1233 file)
1239 files))
1247 f)))
1264 f
1266 args))))
1269 ;; Functions for querying the master and lock files.
1275 ;; Use PATTERNS to parse information out of the current buffer
1276 ;; by matching each regular expression in the list and returning \\1.
1277 ;; If a regexp has two tag brackets, assume the second is a date
1278 ;; field and we want the most recent entry matching the template.
1279 ;; If FILE and PROPERTIES are given, the latter must be a list of
1280 ;; properties of the same length as PATTERNS; each property is assigned
1281 ;; the corresponding value.
1293 latest-val))
1299 value))
1301 patterns)
1302 )
1305 ;; Search for information in a master file.
1318 )
1322 properties))
1323 )
1324 )
1327 ;; Search for information in log program output
1338 )
1339 )
1343 properties))
1344 )
1345 )
1348 "Return the name of the person currently holding a lock on FILE.
1349 Return nil if there is no such person."
1356 ;; This implementation assumes that any file which is under version
1357 ;; control and has -rw-r--r-- is locked by its owner. This is true
1358 ;; for both RCS and SCCS, which keep unlocked files at -r--r--r--.
1359 ;; We have to be careful not to exclude files with execute bits on;
1360 ;; scripts can be under version control too. Also, we must ignore
1361 ;; the group-read and other-read bits, since paranoid users turn them off.
1362 ;; This hack wins because calls to the very expensive vc-fetch-properties
1363 ;; function only have to be made if (a) the file is locked by someone
1364 ;; other than the current user, or (b) some untoward manipulation
1365 ;; behind vc's back has changed the owner or the `group' or `other'
1366 ;; write bits.
1369 nil)
1377 ;; The slow but reliable version
1382 ;; Return version level of the latest version of FILE
1387 ;; Return version level of the latest version of FILE checked in by you
1391 ;; Collect back-end-dependent stuff here
1392 ;;
1393 ;; Everything eventually funnels through these functions. To implement
1394 ;; support for a new version-control system, add another branch to the
1395 ;; vc-backend-dispatch macro and fill it in in each call. The variable
1396 ;; vc-master-templates in vc-hooks.el will also have to change.
1399 "Execute FORM1 or FORM2 depending on whether we're using SCCS or RCS."
1404 )))
1407 ;; Generate lock file name corresponding to FILE
1410 master
1414 "p."
1419 ;; Re-fetch all properties associated with the given file.
1420 ;; Currently these properties are:
1421 ;; vc-locking-user
1422 ;; vc-locked-version
1423 ;; vc-latest-version
1424 ;; vc-your-latest-version
1426 file
1427 ;; SCCS
1433 file
1440 )
1441 file
1443 )
1444 ;; RCS
1455 vc-latest-version vc-your-latest-version))
1456 ))
1459 ;; Where the master and lock files for the current directory are kept
1463 vc-default-back-end
1467 ;; Register a file into the version-control system
1468 ;; Automatically retrieves a read-only version of the file with
1469 ;; keywords expanded if vc-keep-workfiles is non-nil, otherwise
1470 ;; it deletes the workfile.
1484 "-fb"
1498 file)
1499 )))
1501 )
1504 ;; Retrieve a copy of a saved version into a workfile
1513 ;; RCS doesn't let us check out into arbitrary file names directly.
1514 ;; Use `co -p' and make stdout point to the correct file.
1526 filename
1534 )
1538 )
1547 nil)
1548 )
1551 ;; Register changes to FILE as level REV with explanatory COMMENT.
1552 ;; Automatically retrieves a read-only version of the file with
1553 ;; keywords expanded if vc-keep-workfiles is non-nil, otherwise
1554 ;; it deletes the workfile.
1557 ;; Change buffers to get local value of vc-checkin-switches.
1564 vc-checkin-switches)
1567 )
1571 vc-checkin-switches)
1572 ))
1575 )
1578 ;; Revert file to latest checked-in version.
1581 file
1588 )
1591 ;; Steal the lock on the current workfile. Needs RCS 5.6.2 or later for -M.
1597 )
1601 )
1604 ;; Undo the latest checkin. Note: this code will have to get a lot
1605 ;; smarter when we support multiple branches.
1610 )
1612 )
1615 ;; Print change log associated with FILE to buffer *vc*.
1618 file)
1619 )
1622 ;; Assign to a FILE's latest version a given NAME.
1626 )
1627 )
1630 ;; Get a difference report between two versions of FILE.
1631 ;; Get only a brief comparison report if CMP, a difference report otherwise.
1638 "-q"
1643 diff-switches
1646 ;; Some RCS versions don't understand "--brief"; work around this.
1649 status)))
1652 "Check if the current file has any headers in it."
1658 (re-search-forward "\\$[A-Za-z\300-\326\330-\366\370-\377]+\\(: [\t -#%-\176\240-\377]*\\)?\\$" nil t) ;; RCS
1659 )
1660 ))
1662 ;; Back-end-dependent stuff ends here.
1664 ;; Set up key bindings for use while editing log messages
1667 "Minor mode for driving version-control tools.
1668 These bindings are added to the global keymap when you enter this mode:
1681 While you are entering a change log message for a version, the following
1682 additional bindings will be in effect.
1686 Whenever you do a checkin, your log comment is added to a ring of
1687 saved comments. These can be recalled as follows:
1694 Entry to the change-log submode calls the value of text-mode-hook, then
1695 the value of vc-log-mode-hook.
1697 Global user options:
1698 vc-initial-comment If non-nil, require user to enter a change
1699 comment upon first checkin of the file.
1701 vc-keep-workfiles Non-nil value prevents workfiles from being
1702 deleted when changes are checked in
1704 vc-suppress-confirm Suppresses some confirmation prompts,
1705 notably for reversions.
1707 vc-header-alist Which keywords to insert when adding headers
1711 vc-static-header-alist By default, version headers inserted in C files
1712 get stuffed in a static string area so that
1713 ident(RCS) or what(SCCS) can see them in the
1714 compiled object code. You can override this
1715 by setting this variable to nil, or change
1716 the header template by changing it.
1718 vc-command-messages if non-nil, display run messages from the
1719 actual version-control utilities (this is
1720 intended primarily for people hacking vc
1721 itself).
1722 "
1735 )
1737 ;; Initialization code, to be done just once at load-time
1739 nil
1746 )
1748 ;;; These things should probably be generally available
1751 "Walk recursively through default directory.
1752 Invoke FUNC f ARGS on each non-directory file f underneath it."
1774 ;;; DEVELOPER'S NOTES ON CONCURRENCY PROBLEMS IN THIS CODE
1775 ;;;
1776 ;;; These may be useful to anyone who has to debug or extend the package.
1777 ;;;
1778 ;;; A fundamental problem in VC is that there are time windows between
1779 ;;; vc-next-action's computations of the file's version-control state and
1780 ;;; the actions that change it. This is a window open to lossage in a
1781 ;;; multi-user environment; someone else could nip in and change the state
1782 ;;; of the master during it.
1783 ;;;
1784 ;;; The performance problem is that rlog/prs calls are very expensive; we want
1785 ;;; to avoid them as much as possible.
1786 ;;;
1787 ;;; ANALYSIS:
1788 ;;;
1789 ;;; The performance problem, it turns out, simplifies in practice to the
1790 ;;; problem of making vc-locking-user fast. The two other functions that call
1791 ;;; prs/rlog will not be so commonly used that the slowdown is a problem; one
1792 ;;; makes snapshots, the other deletes the calling user's last change in the
1793 ;;; master.
1794 ;;;
1795 ;;; The race condition implies that we have to either (a) lock the master
1796 ;;; during the entire execution of vc-next-action, or (b) detect and
1797 ;;; recover from errors resulting from dispatch on an out-of-date state.
1798 ;;;
1799 ;;; Alternative (a) appears to be unfeasible. The problem is that we can't
1800 ;;; guarantee that the lock will ever be removed. Suppose a user starts a
1801 ;;; checkin, the change message buffer pops up, and the user, having wandered
1802 ;;; off to do something else, simply forgets about it?
1803 ;;;
1804 ;;; Alternative (b), on the other hand, works well with a cheap way to speed up
1805 ;;; vc-locking-user. Usually, if a file is registered, we can read its locked/
1806 ;;; unlocked state and its current owner from its permissions.
1807 ;;;
1808 ;;; This shortcut will fail if someone has manually changed the workfile's
1809 ;;; permissions; also if developers are munging the workfile in several
1810 ;;; directories, with symlinks to a master (in this latter case, the
1811 ;;; permissions shortcut will fail to detect a lock asserted from another
1812 ;;; directory).
1813 ;;;
1814 ;;; Note that these cases correspond exactly to the errors which could happen
1815 ;;; because of a competing checkin/checkout race in between two instances of
1816 ;;; vc-next-action.
1817 ;;;
1818 ;;; For VC's purposes, a workfile/master pair may have the following states:
1819 ;;;
1820 ;;; A. Unregistered. There is a workfile, there is no master.
1821 ;;;
1822 ;;; B. Registered and not locked by anyone.
1823 ;;;
1824 ;;; C. Locked by calling user and unchanged.
1825 ;;;
1826 ;;; D. Locked by the calling user and changed.
1827 ;;;
1828 ;;; E. Locked by someone other than the calling user.
1829 ;;;
1830 ;;; This makes for 25 states and 20 error conditions. Here's the matrix:
1831 ;;;
1832 ;;; VC's idea of state
1833 ;;; |
1834 ;;; V Actual state RCS action SCCS action Effect
1835 ;;; A B C D E
1836 ;;; A . 1 2 3 4 ci -u -t- admin -fb -i<file> initial admin
1837 ;;; B 5 . 6 7 8 co -l get -e checkout
1838 ;;; C 9 10 . 11 12 co -u unget; get revert
1839 ;;; D 13 14 15 . 16 ci -u -m<comment> delta -y<comment>; get checkin
1840 ;;; E 17 18 19 20 . rcs -u -M ; rcs -l unget -n ; get -g steal lock
1841 ;;;
1842 ;;; All commands take the master file name as a last argument (not shown).
1843 ;;;
1844 ;;; In the discussion below, a "self-race" is a pathological situation in
1845 ;;; which VC operations are being attempted simultaneously by two or more
1846 ;;; Emacsen running under the same username.
1847 ;;;
1848 ;;; The vc-next-action code has the following windows:
1849 ;;;
1850 ;;; Window P:
1851 ;;; Between the check for existence of a master file and the call to
1852 ;;; admin/checkin in vc-buffer-admin (apparent state A). This window may
1853 ;;; never close if the initial-comment feature is on.
1854 ;;;
1855 ;;; Window Q:
1856 ;;; Between the call to vc-workfile-unchanged-p in and the immediately
1857 ;;; following revert (apparent state C).
1858 ;;;
1859 ;;; Window R:
1860 ;;; Between the call to vc-workfile-unchanged-p in and the following
1861 ;;; checkin (apparent state D). This window may never close.
1862 ;;;
1863 ;;; Window S:
1864 ;;; Between the unlock and the immediately following checkout during a
1865 ;;; revert operation (apparent state C). Included in window Q.
1866 ;;;
1867 ;;; Window T:
1868 ;;; Between vc-locking-user and the following checkout (apparent state B).
1869 ;;;
1870 ;;; Window U:
1871 ;;; Between vc-locking-user and the following revert (apparent state C).
1872 ;;; Includes windows Q and S.
1873 ;;;
1874 ;;; Window V:
1875 ;;; Between vc-locking-user and the following checkin (apparent state
1876 ;;; D). This window may never be closed if the user fails to complete the
1877 ;;; checkin message. Includes window R.
1878 ;;;
1879 ;;; Window W:
1880 ;;; Between vc-locking-user and the following steal-lock (apparent
1881 ;;; state E). This window may never close if the user fails to complete
1882 ;;; the steal-lock message. Includes window X.
1883 ;;;
1884 ;;; Window X:
1885 ;;; Between the unlock and the immediately following re-lock during a
1886 ;;; steal-lock operation (apparent state E). This window may never cloce
1887 ;;; if the user fails to complete the steal-lock message.
1888 ;;;
1889 ;;; Errors:
1890 ;;;
1891 ;;; Apparent state A ---
1892 ;;;
1893 ;;; 1. File looked unregistered but is actually registered and not locked.
1894 ;;;
1895 ;;; Potential cause: someone else's admin during window P, with
1896 ;;; caller's admin happening before their checkout.
1897 ;;;
1898 ;;; RCS: ci will fail with a "no lock set by <user>" message.
1899 ;;; SCCS: admin will fail with error (ad19).
1900 ;;;
1901 ;;; We can let these errors be passed up to the user.
1902 ;;;
1903 ;;; 2. File looked unregistered but is actually locked by caller, unchanged.
1904 ;;;
1905 ;;; Potential cause: self-race during window P.
1906 ;;;
1907 ;;; RCS: will revert the file to the last saved version and unlock it.
1908 ;;; SCCS: will fail with error (ad19).
1909 ;;;
1910 ;;; Either of these consequences is acceptable.
1911 ;;;
1912 ;;; 3. File looked unregistered but is actually locked by caller, changed.
1913 ;;;
1914 ;;; Potential cause: self-race during window P.
1915 ;;;
1916 ;;; RCS: will register the caller's workfile as a delta with a
1917 ;;; null change comment (the -t- switch will be ignored).
1918 ;;; SCCS: will fail with error (ad19).
1919 ;;;
1920 ;;; 4. File looked unregistered but is locked by someone else.
1921 ;;;
1922 ;;; Potential cause: someone else's admin during window P, with
1923 ;;; caller's admin happening *after* their checkout.
1924 ;;;
1925 ;;; RCS: will fail with a "no lock set by <user>" message.
1926 ;;; SCCS: will fail with error (ad19).
1927 ;;;
1928 ;;; We can let these errors be passed up to the user.
1929 ;;;
1930 ;;; Apparent state B ---
1931 ;;;
1932 ;;; 5. File looked registered and not locked, but is actually unregistered.
1933 ;;;
1934 ;;; Potential cause: master file got nuked during window P.
1935 ;;;
1936 ;;; RCS: will fail with "RCS/<file>: No such file or directory"
1937 ;;; SCCS: will fail with error ut4.
1938 ;;;
1939 ;;; We can let these errors be passed up to the user.
1940 ;;;
1941 ;;; 6. File looked registered and not locked, but is actually locked by the
1942 ;;; calling user and unchanged.
1943 ;;;
1944 ;;; Potential cause: self-race during window T.
1945 ;;;
1946 ;;; RCS: in the same directory as the previous workfile, co -l will fail
1947 ;;; with "co error: writable foo exists; checkout aborted". In any other
1948 ;;; directory, checkout will succeed.
1949 ;;; SCCS: will fail with ge17.
1950 ;;;
1951 ;;; Either of these consequences is acceptable.
1952 ;;;
1953 ;;; 7. File looked registered and not locked, but is actually locked by the
1954 ;;; calling user and changed.
1955 ;;;
1956 ;;; As case 6.
1957 ;;;
1958 ;;; 8. File looked registered and not locked, but is actually locked by another
1959 ;;; user.
1960 ;;;
1961 ;;; Potential cause: someone else checks it out during window T.
1962 ;;;
1963 ;;; RCS: co error: revision 1.3 already locked by <user>
1964 ;;; SCCS: fails with ge4 (in directory) or ut7 (outside it).
1965 ;;;
1966 ;;; We can let these errors be passed up to the user.
1967 ;;;
1968 ;;; Apparent state C ---
1969 ;;;
1970 ;;; 9. File looks locked by calling user and unchanged, but is unregistered.
1971 ;;;
1972 ;;; As case 5.
1973 ;;;
1974 ;;; 10. File looks locked by calling user and unchanged, but is actually not
1975 ;;; locked.
1976 ;;;
1977 ;;; Potential cause: a self-race in window U, or by the revert's
1978 ;;; landing during window X of some other user's steal-lock or window S
1979 ;;; of another user's revert.
1980 ;;;
1981 ;;; RCS: succeeds, refreshing the file from the identical version in
1982 ;;; the master.
1983 ;;; SCCS: fails with error ut4 (p file nonexistent).
1984 ;;;
1985 ;;; Either of these consequences is acceptable.
1986 ;;;
1987 ;;; 11. File is locked by calling user. It looks unchanged, but is actually
1988 ;;; changed.
1989 ;;;
1990 ;;; Potential cause: the file would have to be touched by a self-race
1991 ;;; during window Q.
1992 ;;;
1993 ;;; The revert will succeed, removing whatever changes came with
1994 ;;; the touch. It is theoretically possible that work could be lost.
1995 ;;;
1996 ;;; 12. File looks like it's locked by the calling user and unchanged, but
1997 ;;; it's actually locked by someone else.
1998 ;;;
1999 ;;; Potential cause: a steal-lock in window V.
2000 ;;;
2001 ;;; RCS: co error: revision <rev> locked by <user>; use co -r or rcs -u
2002 ;;; SCCS: fails with error un2
2003 ;;;
2004 ;;; We can pass these errors up to the user.
2005 ;;;
2006 ;;; Apparent state D ---
2007 ;;;
2008 ;;; 13. File looks like it's locked by the calling user and changed, but it's
2009 ;;; actually unregistered.
2010 ;;;
2011 ;;; Potential cause: master file got nuked during window P.
2012 ;;;
2013 ;;; RCS: Checks in the user's version as an initial delta.
2014 ;;; SCCS: will fail with error ut4.
2015 ;;;
2016 ;;; This case is kind of nasty. It means VC may fail to detect the
2017 ;;; loss of previous version information.
2018 ;;;
2019 ;;; 14. File looks like it's locked by the calling user and changed, but it's
2020 ;;; actually unlocked.
2021 ;;;
2022 ;;; Potential cause: self-race in window V, or the checkin happening
2023 ;;; during the window X of someone else's steal-lock or window S of
2024 ;;; someone else's revert.
2025 ;;;
2026 ;;; RCS: ci will fail with "no lock set by <user>".
2027 ;;; SCCS: delta will fail with error ut4.
2028 ;;;
2029 ;;; 15. File looks like it's locked by the calling user and changed, but it's
2030 ;;; actually locked by the calling user and unchanged.
2031 ;;;
2032 ;;; Potential cause: another self-race --- a whole checkin/checkout
2033 ;;; sequence by the calling user would have to land in window R.
2034 ;;;
2035 ;;; SCCS: checks in a redundant delta and leaves the file unlocked as usual.
2036 ;;; RCS: reverts to the file state as of the second user's checkin, leaving
2037 ;;; the file unlocked.
2038 ;;;
2039 ;;; It is theoretically possible that work could be lost under RCS.
2040 ;;;
2041 ;;; 16. File looks like it's locked by the calling user and changed, but it's
2042 ;;; actually locked by a different user.
2043 ;;;
2044 ;;; RCS: ci error: no lock set by <user>
2045 ;;; SCCS: unget will fail with error un2
2046 ;;;
2047 ;;; We can pass these errors up to the user.
2048 ;;;
2049 ;;; Apparent state E ---
2050 ;;;
2051 ;;; 17. File looks like it's locked by some other user, but it's actually
2052 ;;; unregistered.
2053 ;;;
2054 ;;; As case 13.
2055 ;;;
2056 ;;; 18. File looks like it's locked by some other user, but it's actually
2057 ;;; unlocked.
2058 ;;;
2059 ;;; Potential cause: someone released a lock during window W.
2060 ;;;
2061 ;;; RCS: The calling user will get the lock on the file.
2062 ;;; SCCS: unget -n will fail with cm4.
2063 ;;;
2064 ;;; Either of these consequences will be OK.
2065 ;;;
2066 ;;; 19. File looks like it's locked by some other user, but it's actually
2067 ;;; locked by the calling user and unchanged.
2068 ;;;
2069 ;;; Potential cause: the other user relinquishing a lock followed by
2070 ;;; a self-race, both in window W.
2071 ;;;
2072 ;;; Under both RCS and SCCS, both unlock and lock will succeed, making
2073 ;;; the sequence a no-op.
2074 ;;;
2075 ;;; 20. File looks like it's locked by some other user, but it's actually
2076 ;;; locked by the calling user and changed.
2077 ;;;
2078 ;;; As case 19.
2079 ;;;
2080 ;;; PROBLEM CASES:
2081 ;;;
2082 ;;; In order of decreasing severity:
2083 ;;;
2084 ;;; Cases 11 and 15 under RCS are the only one that potentially lose work.
2085 ;;; They would require a self-race for this to happen.
2086 ;;;
2087 ;;; Case 13 in RCS loses information about previous deltas, retaining
2088 ;;; only the information in the current workfile. This can only happen
2089 ;;; if the master file gets nuked in window P.
2090 ;;;
2091 ;;; Case 3 in RCS and case 15 under SCCS insert a redundant delta with
2092 ;;; no change comment in the master. This would require a self-race in
2093 ;;; window P or R respectively.
2094 ;;;
2095 ;;; Cases 2, 10, 19 and 20 do extra work, but make no changes.
2096 ;;;
2097 ;;; Unfortunately, it appears to me that no recovery is possible in these
2098 ;;; cases. They don't yield error messages, so there's no way to tell that
2099 ;;; a race condition has occurred.
2100 ;;;
2101 ;;; All other cases don't change either the workfile or the master, and
2102 ;;; trigger command errors which the user will see.
2103 ;;;
2104 ;;; Thus, there is no explicit recovery code.
2106 ;;; vc.el ends here