| blob | 6705ab891820cd4721ee7c11705dd01cbe171b35 |
1 ;;; vc.el --- drive a version-control system from within Emacs
3 ;; Copyright (C) 1992,93,94,95,96,97,98,2000 Free Software Foundation, Inc.
5 ;; Author: FSF (see below for full credits)
6 ;; Maintainer: Andre Spiegel <spiegel@gnu.org>
8 ;; $Id: vc.el,v 1.279 2000/10/08 19:12:52 monnier Exp $
10 ;; This file is part of GNU Emacs.
12 ;; GNU Emacs is free software; you can redistribute it and/or modify
13 ;; it under the terms of the GNU General Public License as published by
14 ;; the Free Software Foundation; either version 2, or (at your option)
15 ;; any later version.
17 ;; GNU Emacs is distributed in the hope that it will be useful,
18 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
19 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
20 ;; GNU General Public License for more details.
22 ;; You should have received a copy of the GNU General Public License
23 ;; along with GNU Emacs; see the file COPYING. If not, write to the
24 ;; Free Software Foundation, Inc., 59 Temple Place - Suite 330,
25 ;; Boston, MA 02111-1307, USA.
27 ;;; Credits:
29 ;; VC was initially designed and implemented by Eric S. Raymond
30 ;; <esr@snark.thyrsus.com>. Over the years, many people have
31 ;; contributed substantial amounts of work to VC. These include:
32 ;; Per Cederqvist <ceder@lysator.liu.se>
33 ;; Paul Eggert <eggert@twinsun.com>
34 ;; Sebastian Kremer <sk@thp.uni-koeln.de>
35 ;; Martin Lorentzson <martinl@gnu.org>
36 ;; Dave Love <d.love@gnu.org>
37 ;; Stefan Monnier <monnier@cs.yale.edu>
38 ;; Andre Spiegel <spiegel@gnu.org>
39 ;; Richard Stallman <rms@gnu.org>
40 ;; ttn@netcom.com
42 ;;; Commentary:
44 ;; This mode is fully documented in the Emacs user's manual.
45 ;;
46 ;; Supported version-control systems presently include SCCS, RCS, and CVS.
47 ;;
48 ;; Some features will not work with old RCS versions. Where
49 ;; appropriate, VC finds out which version you have, and allows or
50 ;; disallows those features (stealing locks, for example, works only
51 ;; from 5.6.2 onwards).
52 ;; Even initial checkins will fail if your RCS version is so old that ci
53 ;; doesn't understand -t-; this has been known to happen to people running
54 ;; NExTSTEP 3.0.
55 ;;
56 ;; You can support the RCS -x option by customizing vc-rcs-master-templates.
57 ;;
58 ;; Proper function of the SCCS diff commands requires the shellscript vcdiff
59 ;; to be installed somewhere on Emacs's path for executables.
60 ;;
61 ;; If your site uses the ChangeLog convention supported by Emacs, the
62 ;; function vc-comment-to-change-log should prove a useful checkin hook.
63 ;;
64 ;; The vc code maintains some internal state in order to reduce expensive
65 ;; version-control operations to a minimum. Some names are only computed
66 ;; once. If you perform version control operations with RCS/SCCS/CVS while
67 ;; vc's back is turned, or move/rename master files while vc is running,
68 ;; vc may get seriously confused. Don't do these things!
69 ;;
70 ;; Developer's notes on some concurrency issues are included at the end of
71 ;; the file.
73 ;;; Code:
75 ;;;;;;;;;;;;;;;;; Backend-specific functions ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
76 ;;
77 ;; for each operation FUN, the backend should provide a function vc-BACKEND-FUN.
78 ;; Operations marked with a `-' instead of a `*' are optional.
80 ;; * registered (file)
81 ;; * state (file)
82 ;; - state-heuristic (file)
83 ;; The default behavior delegates to `state'.
84 ;; - dir-state (dir)
85 ;; * checkout-model (file)
86 ;; - mode-line-string (file)
87 ;; * workfile-version (file)
88 ;; * revert (file)
89 ;; - merge-news (file)
90 ;; Only needed if state `needs-merge' is possible.
91 ;; - merge (file rev1 rev2)
92 ;; - steal-lock (file &optional version)
93 ;; Only required if files can be locked by somebody else.
94 ;; * register (file rev comment)
95 ;; * unregister (file backend)
96 ;; - receive-file (file rev)
97 ;; - responsible-p (file)
98 ;; Should also work if FILE is a directory (ends with a slash).
99 ;; - could-register (file)
100 ;; * checkout (file writable &optional rev destfile)
101 ;; Checkout revision REV of FILE into DESTFILE.
102 ;; DESTFILE defaults to FILE.
103 ;; The file should be made writable if WRITABLE is non-nil.
104 ;; REV can be nil (BASE) or "" (HEAD) or any other revision.
105 ;; * checkin (file rev comment)
106 ;; - logentry-check ()
107 ;; * diff (file &optional rev1 rev2)
108 ;; Insert the diff for FILE into the current buffer.
109 ;; REV1 should default to workfile-version.
110 ;; REV2 should default to the current workfile
111 ;; Return a status of either 0 (i.e. no diff) or 1 (i.e. either non-empty
112 ;; diff or the diff is run asynchronously).
113 ;; - workfile-unchanged-p (file)
114 ;; Return non-nil if FILE is unchanged from its current workfile version.
115 ;; This function should do a brief comparison of FILE's contents
116 ;; with those of the master version. If the backend does not have
117 ;; such a brief-comparison feature, the default implementation of this
118 ;; function can be used, which delegates to a full vc-BACKEND-diff.
119 ;; - clear-headers ()
120 ;; * check-headers ()
121 ;; - dired-state-info (file)
122 ;; - create-snapshot (dir name branchp)
123 ;; Take a snapshot of the current state of files under DIR and name it NAME.
124 ;; This should make sure that files are up-to-date before proceeding
125 ;; with the action.
126 ;; DIR can also be a file and if BRANCHP is specified, NAME
127 ;; should be created as a branch and DIR should be checked out under
128 ;; this new branch. The default behavior does not support branches
129 ;; but does a sanity check, a tree traversal and for each file calls
130 ;; `assign-name'.
131 ;; * assign-name (file name)
132 ;; Give name NAME to the current version of FILE, assuming it is
133 ;; up-to-date. Only used by the default version of `create-snapshot'.
134 ;; - retrieve-snapshot (dir name update)
135 ;; Retrieve a named snapshot of all registered files at or below DIR.
136 ;; If UPDATE is non-nil, then update buffers of any files in the snapshot
137 ;; that are currently visited.
138 ;; * print-log (file)
139 ;; Insert the revision log of FILE into the current buffer.
140 ;; - show-log-entry (version)
141 ;; - wash-log (file)
142 ;; Remove all non-comment information from the output of print-log
143 ;; - comment-history (file)
144 ;; - update-changelog (files)
145 ;; Find changelog entries for FILES, or for all files at or below
146 ;; the default-directory if FILES is nil.
147 ;; * latest-on-branch-p (file)
148 ;; - cancel-version (file writable)
149 ;; - rename-file (old new)
150 ;; - annotate-command (file buf)
151 ;; - annotate-difference (pos)
152 ;; Only required if `annotate-command' is defined for the backend.
165 minor-mode-alist)))
167 ;; General customization
170 "Version-control system in Emacs."
174 "*If non-nil, treat user as expert; suppress yes-no prompts on some things."
179 "*If non-nil, delete the *VC-log* buffer and window after each logical action.
180 If nil, bury that buffer instead.
181 This is most useful if you have multiple windows on a frame and would like to
182 preserve the setting."
187 "*If non-nil, prompt for initial comment when a file is registered."
192 "*A string used as the default version number when a new file is registered.
199 "*If non-nil, display run messages from back-end commands."
204 "*A string or list of strings specifying extra switches for checkin.
210 string))
214 "*A string or list of strings specifying extra switches for checkout.
220 string))
224 "*A string or list of strings; extra switches for registering a file.
230 string))
234 "*Switches passed to `ls' for vc-dired. MUST contain the `l' option."
240 "*If non-nil, show directory trees recursively in VC Dired."
246 "*If non-nil, show only locked files in VC Dired."
252 "*List of directory names to be ignored while recursively walking file trees."
259 ;;; This is duplicated in diff.el.
263 ;;;###autoload
265 "*Normal hook (list of functions) run after a checkin is done.
266 See `run-hooks'."
271 ;;;###autoload
273 "*Normal hook (list of functions) run before a file gets checked in.
274 See `run-hooks'."
279 "*Normal hook run by `vc-backend-logentry-check'.
280 Use this to impose your own rules on the entry in addition to any the
281 version control backend imposes itself."
285 ;; Annotate customization
305 Ages are given in units of 2**-16 seconds.
306 Default is eighteen steps using a twenty day increment."
311 "*Color for lines older than CAR of last cons in `vc-annotate-color-map'."
317 Default color is used if nil."
322 "*Menu elements for the mode-specific menu of VC-Annotate mode.
323 List of factors, used to expand/compress the time scale. See `vc-annotate'."
327 ;; vc-annotate functionality (CVS only).
334 m)
340 ;; Header-insertion hair
345 "*Associate static header string templates with file types.
346 A \%s in the template is replaced with the first string associated with
347 the file's version control type in `vc-header-alist'."
355 "*Special comment delimiters to be used in generating vc headers only.
356 Add an entry in this list if you need to override the normal `comment-start'
357 and `comment-end' variables. This will only be necessary if the mode language
358 is sensitive to blank lines."
365 ;; Default is to be extra careful for super-user.
366 ;; TODO: This variable is no longer used; the corresponding checks
367 ;; are always done now. If that turns out to be fast enough,
368 ;; the variable can be obsoleted.
370 "*Non-nil means be extra-careful in checkout.
371 Verify that the file really is not locked
372 and that its contents match what the master file says."
376 \f
377 ;;; The main keymap
396 map))
399 ;; Initialization code, to be done just once at load-time
407 map))
408 ;; Compatibility with old name. Should we bother ?
411 \f
412 ;; Variables the user doesn't need to know about.
418 ;; In a log entry buffer, this is a local variable
419 ;; that points to the buffer for which it was made
420 ;; (either a file, or a VC dired buffer).
436 ;;; functions that operate on RCS revision numbers. This code should
437 ;;; also be moved into the backends. It stays for now, however, since
438 ;;; it is used in code below.
440 "Return t if REV is a revision on the trunk."
444 "Return t if REV is a branch revision."
448 "Return the branch part of a revision number REV."
452 "Return the minor version number of a revision number REV."
457 "Guess the version number immediately preceding REV."
461 ;; version does probably not start a branch or release
464 ;; we are at the beginning of the trunk --
465 ;; don't know anything to return here
466 ""
467 ;; we are at the beginning of a branch --
468 ;; return version of starting point
471 ;; File property caching
474 "Clear all cached file properties and the comment ring."
477 ;; Note: there is potential for minor lossage here if there is an open
478 ;; log buffer with a nonzero local value of vc-comment-ring-index.
482 "Execute FORM, then set per-file properties for FILE,
483 but only those that have not been set during the execution of FORM.
484 SETTINGS is a list of two-element lists, each of which has the
485 form (PROPERTY . VALUE)."
488 ,form
496 ;; Random helper functions
502 ;;; Two macros for elisp programming
503 ;;;###autoload
505 "Check out a writable copy of FILE if necessary and execute the body.
506 Check in FILE with COMMENT (a string) after BODY has been executed.
507 FILE is passed through `expand-file-name'; BODY executed within
508 `save-excursion'. If FILE is not under version control, or locked by
509 somebody else, signal error."
522 ;;;###autoload
524 "Edit FILE under version control, executing body.
525 Checkin with COMMENT after executing BODY.
526 This macro uses `with-vc-file', passing args to it.
527 However, before executing BODY, find FILE, and after BODY, save buffer."
531 ,@body
536 "Make sure that the current buffer visits a version-controlled file."
553 "An alternative output filter for async process P.
554 The only difference with the default filter is to insert S after markers."
563 "Prepare BUF for executing a VC command and make it the current buffer.
578 "Eval CODE when the current buffer's process is done.
579 If the current buffer has no process, just evaluate CODE.
580 Else, add CODE to the process' sentinel."
583 ;; If there's no background process, just execute the code.
585 ;; If the background process has exited, reap it and try again
589 ;; If a process is running, add CODE to the sentinel
597 ; (goto-char...)'
599 sentinel))))))
602 nil)
605 "Hook run at the end of `vc-do-command'.
606 Each function is called inside the buffer in which the command was run
610 "Execute a version control command, notifying user and checking for errors.
611 Output from COMMAND goes to BUFFER, or *vc* if BUFFER is nil or the current
612 buffer (which is assumed to be properly setup) if BUFFER is t. The
613 command is considered successful if its exit status does not exceed
614 OKSTATUS (if OKSTATUS is nil, that means to ignore errors, if it is 'async,
615 that means not to wait for termination of the subprocess). FILE is
616 the name of the working file (may also be nil, to execute commands
617 that don't expect a file name). If an optional list of FLAGS is present,
618 that is inserted into the command line before the filename."
629 ;; FIXME: file-relative-name can return a bogus result because
630 ;; it doesn't look at the actual file-system to see if symlinks
631 ;; come into play.
634 ;; Add vc-path to PATH for the execution of this command.
637 path-separator
639 process-environment))
643 squeezed)))
645 ;;(set-process-sentinel proc (lambda (p msg) (delete-process p)))
660 status)))
663 "Save a bit of the text around POSN in the current buffer.
664 Used to help us find the corresponding position again later
665 if markers are destroyed or corrupted."
666 ;; A lot of this was shamelessly lifted from Sebastian Kremer's
667 ;; rcs.el mode.
674 "Return the position of CONTEXT in the current buffer, or nil if not found."
683 ;; Can't use search-backward since the match may continue
684 ;; after point.
686 ;; goto-char doesn't signal an error at
687 ;; beginning of buffer like backward-char would
689 ;; to beginning of OSTRING
693 "Return t if POSN matches CONTEXT, nil otherwise."
698 nil
702 "Return a list (POINT-CONTEXT MARK-CONTEXT REPARSE).
703 Used by `vc-restore-buffer-context' to later restore the context."
705 ;; Use mark-marker to avoid confusion in transient-mark-mode.
708 ;; Make the right thing happen in transient-mark-mode.
710 ;; We may want to reparse the compilation buffer after revert
713 ;; Construct a list; each elt is nil or a buffer
714 ;; iff that buffer is a compilation output buffer
715 ;; that contains markers into the current buffer.
720 compilation-old-error-list
721 compilation-error-list))
736 "Restore point/mark, and reparse any affected compilation buffers.
737 CONTEXT is that which `vc-buffer-context' returns."
741 ;; Reparse affected compilation buffers.
746 ;; Record the position in the compilation buffer of
747 ;; the last error next-error went to.
750 ;; Reparse the error messages as far as they were parsed before.
752 ;; Move the pointer up to find the error we were at before
753 ;; reparsing. Now next-error should properly go to the next one.
759 ;; if necessary, restore point and mark
764 mark-context
770 "Revert buffer, trying to keep point and mark where user expects them.
771 Tries to be clever in the face of changes due to expanded version control
772 key words. This is important for typeahead to work as expected.
773 ARG and NO-CONFIRM are passed on to `revert-buffer'."
777 ;; Use save-excursion here, because it may be able to restore point
778 ;; and mark properly even in cases where vc-restore-buffer-context
779 ;; would fail. However, save-excursion might also get it wrong --
780 ;; in this case, vc-restore-buffer-context gives it a second try.
782 ;; t means don't call normal-mode;
783 ;; that's to preserve various minor modes.
789 "Make sure the current buffer and its working file are in sync.
790 NOT-URGENT means it is ok to continue if the user says not to save."
799 "Has FILE changed since last checkout?"
806 unchanged))))
809 "Default check whether FILE is unchanged: diff against master version."
813 "Force a recomputation of the version control state of FILE.
814 The state is computed using the exact, and possibly expensive
815 function `vc-BACKEND-state', not the heuristic."
819 "Do The Right Thing for a given version-controlled FILE.
820 If COMMENT is specified, it will be used as an admin or checkin comment.
821 If VERBOSE is non-nil, query the user rather than using default parameters."
823 state version)
825 ;; Check relation of buffer and file, and make sure
826 ;; user knows what he's doing. First, finding the file
827 ;; will check whether the file on disk is newer.
835 ;; Now, check if we have unsaved changes.
841 ;; Do the right thing
848 ;; up-to-date
853 ;; go to a different version
860 version))))
862 ;; check the file out
865 ;; do nothing
868 ;; Abnormal: edited but read-only
870 ;; Make the file+buffer read-write. If the user really wanted to
871 ;; commit, he'll get a chance to do that next time around, anyway.
877 ;; edited
880 ;; For files with locking, if the file does not contain
881 ;; any changes, just let go of the lock, i.e. revert.
884 ;; If buffer is modified, that means the user just
885 ;; said no to saving it; in that case, don't revert,
886 ;; because the user might intend to save after
887 ;; finishing the log entry.
889 ;; DO NOT revert the file without asking the user!
902 ;; locked by somebody else
910 state))
912 ;; needs-patch
915 "%s is not up-to-date. Get latest version? "
923 ;; needs-merge
926 "%s is not up-to-date. Merge in changes now? "
931 ;; unlocked-changes
944 ;; Must clear any headers here because they wouldn't
945 ;; show that the file is locked now.
957 "Call `vc-next-action-on-file' on all the marked files.
958 Ignores FILE and REV, but passes on COMMENT."
968 nil t))
971 ;; Here's the major entry point.
973 ;;;###autoload
975 "Do the next logical checkin or checkout operation on the current file.
977 If you call this from within a VC dired buffer with no files marked,
978 it will operate on the file in the current line.
980 If you call this from within a VC dired buffer, and one or more
981 files are marked, it will accept a log message and then operate on
982 each one. The log message will be used as a comment for any register
983 or checkin operations, but ignored when doing checkouts. Attempted
984 lock steals will raise an error.
986 A prefix argument lets you specify the version number to use.
988 For RCS and SCCS files:
989 If the file is not already registered, this registers it for version
990 control.
991 If the file is registered and not locked by anyone, this checks out
992 a writable and locked file ready for editing.
993 If the file is checked out and locked by the calling user, this
994 first checks to see if the file has changed since checkout. If not,
995 it performs a revert.
996 If the file has been changed, this pops up a buffer for entry
997 of a log message; when the message has been entered, it checks in the
998 resulting changes along with the log message as change commentary. If
999 the variable `vc-keep-workfiles' is non-nil (which is its default), a
1000 read-only copy of the changed file is left in place afterwards.
1001 If the file is registered and locked by someone else, you are given
1002 the option to steal the lock.
1004 For CVS files:
1005 If the file is not already registered, this registers it for version
1007 If the file is added but not committed, it is committed.
1008 If your working file is changed, but the repository file is
1009 unchanged, this pops up a buffer for entry of a log message; when the
1010 message has been entered, it checks in the resulting changes along
1011 with the logmessage as change commentary. A writable file is retained.
1012 If the repository file is changed, you are asked if you want to
1013 merge in the changes into your working copy."
1028 "Enter a change comment for the marked files."
1037 ;;; These functions help the vc-next-action entry point
1039 ;;;###autoload
1041 "Register the current file into a version control system.
1042 With prefix argument SET-VERSION, allow user to specify initial version
1043 level. If COMMENT is present, use that as an initial comment.
1045 The version control system to use is found by cycling through the list
1046 `vc-handled-backends'. The first backend in that list which declares
1047 itself responsible for the file (usually because other files in that
1048 directory are already registered under that backend) will be used to
1049 register the file. If no backend declares itself responsible, the
1050 first backend that could register the file is used."
1058 ;; Watch out for new buffers of size 0: the corresponding file
1059 ;; does not exist yet, even though buffer-modified-p is nil.
1070 ;; TODO: Use backend-specific init version.
1071 vc-default-init-version)
1073 nil
1074 "Enter initial comment."
1088 "Return the name of a backend system that is responsible for FILE.
1089 The optional argument REGISTER means that a backend suitable for
1090 registration should be found.
1092 If REGISTER is nil, then if FILE is already registered, return the
1093 backend of FILE. If FILE is not registered, or a directory, then the
1094 first backend in `vc-handled-backends' that declares itself
1095 responsible for FILE is returned. If no backend declares itself
1096 responsible, return the first backend.
1098 If REGISTER is non-nil, return the first responsible backend under
1099 which FILE is not yet registered. If there is no such backend, return
1100 the first backend under which FILE is not yet registered, but could
1101 be registered."
1106 ;; First try: find a responsible backend. If this is for registration,
1107 ;; it must be a backend under which FILE is not yet registered.
1113 ;; no responsible backend
1115 ;; if this is not for registration, the first backend must do
1117 ;; for registration, we need to find a new backend that
1118 ;; could register FILE
1126 "Indicate whether BACKEND is reponsible for FILE.
1127 The default is to return nil always."
1128 nil)
1131 "Return non-nil if BACKEND could be used to register FILE.
1132 The default implementation returns t for all files."
1133 t)
1136 "If FILE is in the current buffer, either revert or unvisit it.
1137 The choice between revert (to see expanded keywords) and unvisit depends on
1138 `vc-keep-workfiles'. NOQUERY if non-nil inhibits confirmation for
1139 reverting. NOQUERY should be t *only* if it is known the only
1140 difference between the buffer and the file is due to version control
1141 rather than user editing!"
1146 ;; TODO: Adjusting view mode might no longer be necessary
1147 ;; after RMS change to files.el of 1999-08-08. Investigate
1148 ;; this when we install the new VC.
1161 "If FILE is currently visited, resynch its buffer."
1171 "Accept a comment for an operation on FILE revision REV.
1172 If COMMENT is nil, pop up a VC-log buffer, emit MSG, and set the
1173 action on close to ACTION. If COMMENT is a string and
1174 INITIAL-CONTENTS is non-nil, then COMMENT is used as the initial
1175 contents of the log entry buffer. If COMMENT is a string and
1176 INITIAL-CONTENTS is nil, do action immediately as if the user had
1177 entered COMMENT. If COMMENT is t, also do action immediately with an
1178 empty comment. Remember the file's buffer in `vc-parent-buffer'
1179 \(current one if no file). AFTER-HOOK specifies the local value
1180 for vc-log-operation-hook."
1210 "Retrieve a copy of the revision REV of FILE.
1211 If WRITABLE is non-nil, make sure the retrieved file is writable.
1212 REV defaults to the latest revision."
1220 file
1224 ;; Maybe the backend is not installed ;-(
1232 'up-to-date
1239 "Steal the lock on FILE."
1245 file-description owner)))
1248 nil nil nil nil
1259 ;; This is called when the notification has been sent.
1262 file
1269 "Check in FILE.
1270 The optional argument REV may be a string specifying the new version
1271 level (if nil increment the current level). COMMENT is a comment
1272 string; if omitted, a buffer is popped up to accept a comment. If
1273 INITIAL-CONTENTS is non-nil, then COMMENT is used as the initial contents
1274 of the log entry buffer.
1276 If `vc-keep-workfiles' is nil, FILE is deleted afterwards, provided
1277 that the version control system supports this mode of operation.
1279 Runs the normal hook `vc-checkin-hook'."
1281 file rev comment initial-contents
1282 "Enter a change comment."
1285 ;; "This log message intentionally left almost blank".
1286 ;; RCS 5.7 gripes about white-space-only comments too.
1290 file
1291 ;; Change buffers to get local value of vc-checkin-switches.
1303 "Enter last VC comment into change log file for current buffer's file.
1304 Optional arg (interactive prefix) non-nil means prompt for user name and site.
1305 Second arg is file name of change log. \
1306 If nil, uses `change-log-default-name'.
1308 May be useful as a `vc-checkin-hook' to update change logs automatically."
1312 ;; Make sure the defvar for add-log-current-defun-function has been executed
1313 ;; before binding it.
1317 ;; Don't let add-change-log-entry insert a defun name.
1319 end)
1320 ;; Call add-log to do half the work.
1322 ;; Insert the VC comment, leaving point before it.
1325 ;; It starts with an open-paren, as in "(foo): Frobbed."
1326 ;; So remove the ": " add-log inserted.
1328 ;; Canonicalize the white space between the file name and comment.
1330 ;; Indent rest of the text the same way add-log indented the first line.
1337 ;; Fill the inserted text, preserving open-parens at bol.
1342 ;; Canonicalize the white space at the end of the entry so it is
1343 ;; separated from the next entry by a single blank line.
1350 "Complete the operation implied by the current log entry."
1352 ;; Check and record the comment, if any.
1354 ;; Comment too long?
1359 ;; Record the comment in the comment ring
1365 ;; Sync parent buffer in case the user modified it while editing the comment.
1366 ;; But not if it is a vc-dired buffer.
1370 ;; save the parameters held in buffer-local variables
1378 ;; OK, do it to it
1381 log-file
1382 log-version
1383 log-entry))
1384 ;; Remove checkin window (after the checkin so that if that fails
1385 ;; we don't zap the *VC-log* buffer and the typing therein).
1389 ;; Kill buffer and delete any other dedicated windows/frames.
1394 ;; Now make sure we see the expanded headers
1401 ;; Code for access to the comment ring
1406 ;; Initialize the index on the first use of this command
1407 ;; so that the first M-p gets index 0, and the first M-n gets
1408 ;; index -1.
1411 len))
1414 "Cycle backwards through comment history."
1425 "Cycle forwards through comment history."
1430 "Search backwards through comment history for substring match."
1431 ;; Why substring rather than regexp ? -sm
1448 "Search forwards through comment history for substring match."
1453 ;; Additional entry points for examining version histories
1455 ;;;###autoload
1457 "Display diffs between file versions.
1458 Normally this compares the current file and buffer with the most recent
1459 checked in version of that file. This uses no arguments.
1460 With a prefix argument, it reads the file name to use
1461 and two version designators specifying which versions to compare."
1473 "For FILE, report diffs between two stored versions REL1 and REL2 of it.
1474 If FILE is a directory, generate diffs between versions for all registered
1475 files in or below it."
1479 "File or dir to diff: (default visited file) "
1481 default-directory buffer-file-name t)))
1483 ;; compute default versions based on the file state
1485 ;; if it's a directory, don't supply any version default
1487 nil)
1488 ;; if the file is not up-to-date, use current version as older version
1491 ;; if the file is not locked, use last and previous version as default
1496 ;; construct argument list
1502 nil nil rel1-default)
1507 nil nil rel2-default))))
1510 ;; recursive directory diff
1516 " and "
1520 ;; FIXME: this should do a single exec in CVS.
1522 default-directory
1530 ;; single file diff
1537 file
1542 diff-switches
1556 nil)
1558 ;; Gnus-5.8.5 sets up an autoload for diff-mode, even if it's
1559 ;; not available. Work around that.
1565 t))
1567 ;;;###autoload
1569 "Visit version REV of the current buffer in another window.
1570 If the current buffer is named `F', the version is named `F.~REV~'.
1571 If `F.~REV~' already exists, it is used instead of being re-created."
1576 rev))
1582 ;; Header-insertion code
1584 ;;;###autoload
1586 "Insert headers in a file for use with your version control system.
1587 Headers desired are inserted at point, and are pulled from
1588 the variable `vc-BACKEND-header'."
1606 hdstrings)
1611 vc-static-header-alist))
1612 )
1613 )))))
1616 "Clear all version headers in the current buffer (or FILE).
1617 I.e. reset them to the non-expanded form."
1624 ;; save-excursion may be able to relocate point and mark
1625 ;; properly. If it fails, vc-restore-buffer-context
1626 ;; will give it a second try.
1634 ;;;###autoload
1636 "Merge changes between two versions into the current buffer's file.
1637 This asks for two versions to merge from in the minibuffer. If the
1638 first version is a branch number, then merge all changes from that
1639 branch. If the first version is empty, merge news, i.e. recent changes
1640 from the current branch.
1642 See Info node `Merging'."
1649 first-version second-version status)
1671 ;; We want to merge an entire branch. Set versions
1672 ;; accordingly, so that vc-BACKEND-merge understands us.
1674 ;; first-version must be the starting point of the branch
1696 ;;;###autoload
1698 "Invoke ediff to resolve conflicts in the current buffer.
1699 The conflicts must be marked with rcsmerge conflict markers."
1748 ;; Fire up ediff.
1752 ;; Ediff is now set up, and we are in the control buffer.
1753 ;; Do a few further adjustments and take precautions for exit.
1777 nil))))
1779 ;; The VC directory major mode. Coopt Dired for this.
1780 ;; All VC commands get mapped into logical equivalents.
1789 ;; Emacs-20 has a lousy keymap inheritance that won't work here.
1790 ;; Emacs-21's is still lousy but just better enough that it'd work. -sm
1791 ;; (set-keymap-parent vmap vc-prefix-map)
1795 map))
1798 "The major mode used in VC directory buffers.
1800 It works like Dired, but lists only files under version control, with
1801 the current VC state of each file being indicated in the place of the
1802 file's link count, owner, group and size. Subdirectories are also
1803 listed, and you may insert them into the buffer as desired, like in
1804 Dired.
1806 All Dired commands operate normally, with the exception of `v', which
1807 is redefined as the version control prefix, so that you can type
1808 `vl', `v=' etc. to invoke `vc-print-log', `vc-diff', and the like on
1809 the file named in the current Dired buffer line. `vv' invokes
1810 `vc-next-action' on this file, or on all files currently marked.
1811 There is a special command, `*l', to mark all files currently locked."
1812 ;; define-derived-mode does it for us in Emacs-21, but not in Emacs-20.
1813 ;; We do it here because dired might not be loaded yet
1814 ;; when vc-dired-mode-map is initialized.
1818 ;; The following is slightly modified from dired.el,
1819 ;; because file lines look a bit different in vc-dired-mode.
1823 ;; In some locales, month abbreviations are as short as 2 letters,
1824 ;; and they can be padded on the right with spaces.
1826 ;; Recognize any non-ASCII character.
1827 ;; The purpose is to match a Kanji character.
1829 ;; (k "[^\x00-\x7f\x80-\xff]")
1838 ;; the .* below ensures that we find the last match on a line
1841 vc-dired-switches
1843 vc-dired-switches))
1848 "Toggle terse display in VC Dired."
1851 nil
1858 "Mark all files currently locked."
1878 "Reformat a directory-listing line.
1879 Replace various columns with version control information.
1880 This code, like dired, assumes UNIX -l format."
1890 limit t)
1893 limit t)
1896 limit t))
1903 "Reformat the listing according to version control.
1904 Called by dired after any portion of a vc-dired buffer has been read in."
1910 ;; subdir header line
1912 ;; if the backend supports it, get the state
1913 ;; of all files in this directory at once
1918 ;; erase (but don't remove) the "total" line
1922 ;; file line
1925 ;; subdir
1929 vc-directory-exclusion-list)
1935 ;; Don't show directories in terse mode. Don't use
1936 ;; dired-kill-line to remove it, because in recursive listings,
1937 ;; that would remove the directory contents as well.
1945 ;; ordinary file
1953 ;; any other line
1964 "Remove empty subdirs."
1975 ;; We cannot remove the top level directory.
1976 ;; Just make it look a little nicer.
1984 "Return a list of all vc-dired buffers that currently display DIR."
1986 ;; Check whether dired is loaded.
1993 result))
1996 "Update the entries for FILE in any VC Dired buffers that list it."
2002 ;; bind vc-dired-terse-mode to nil so that
2003 ;; files won't vanish when they are checked in
2006 buffers))))
2008 ;;;###autoload
2010 "Create a buffer in VC Dired Mode for directory DIR.
2012 See Info node `VC Dired Mode'.
2014 With prefix arg READ-SWITCHES, specify a value to override
2015 `dired-listing-switches' when generating the listing."
2022 vc-dired-switches)))
2027 vc-dired-switches
2031 ;; Named-configuration entry points
2034 "Scan the tree below DIR, looking for non-uptodate files.
2035 If any file is not up-to-date, return the name of the first such file.
2036 \(This means, neither snapshot creation nor retrieval is allowed.\)
2037 If one or more of the files are currently visited, return `visited'.
2038 Otherwise, return nil."
2042 dir
2046 status)))
2048 ;;;###autoload
2050 "Descending recursively from DIR, make a snapshot called NAME.
2051 For each registered file, the version level of its latest version
2052 becomes part of the named configuration. If the prefix argument
2053 BRANCHP is given, the snapshot is made as a new branch and the files
2054 are checked out in that new branch."
2058 current-prefix-arg))
2072 dir
2076 ;;;###autoload
2078 "Descending recursively from DIR, retrieve the snapshot called NAME.
2079 If NAME is empty, it refers to the latest versions.
2080 If locking is used for the files in DIR, then there must not be any
2081 locked files at or below DIR (but if NAME is empty, locked files are
2082 allowed and simply skipped)."
2100 dir
2111 dir
2117 ;; Miscellaneous other entry points
2119 ;;;###autoload
2121 "List the change log of the current buffer in a window."
2140 ;; move point to the log entry for the current version
2145 'show-log-entry
2149 "Return a string with all log entries that were made under BACKEND for FILE."
2157 "Remove all non-comment information from log output.
2158 This default implementation works for RCS logs; backends should override
2159 it if their logs are not in RCS format."
2176 ;;;###autoload
2178 "Revert the current buffer's file back to the version it was based on.
2179 This asks for confirmation if the buffer contents are not identical
2180 to that version. This function does not automatically pick up newer
2185 ;; This operation should always ask for confirmation.
2188 status)
2190 ;; vc-diff selects the new window, which is not what we want:
2191 ;; if the new window is on another frame, that'd require the user
2192 ;; moving her mouse to answer the yes-or-no-p question.
2206 ;; Do the reverting
2212 "If version backups should be used for FILE, and there exists
2213 such a backup for REV or the current workfile version of file,
2214 return the name of it; otherwise return nil."
2218 backup-file))))
2221 "Revert FILE back to the version it was based on."
2223 file
2233 ;;;###autoload
2235 "Get rid of most recently checked in version of this file.
2236 A prefix argument NOREVERT means do not revert the buffer afterwards."
2249 (error (substitute-command-keys "File is not up to date; use \\[vc-revert-buffer] to discard changes"))))
2257 file
2261 0
2270 ;; inhibit backup for this buffer
2281 ;;;autoload
2283 "Make BACKEND the current version control system for FILE.
2284 FILE must already be registered in BACKEND. The change is not
2285 permanent, only for the current session. This function only changes
2286 VC's perspective on FILE, it does not register or unregister it.
2287 By default, this command cycles through the registered backends.
2288 To get a prompt, use a prefix argument."
2291 buffer-file-name
2294 ;; Find the registered backends.
2298 ;; Find the next backend.
2314 ;; Force recomputation of the state
2320 ;;;autoload
2322 "Transfer FILE to another version control system NEW-BACKEND.
2323 If NEW-BACKEND has a higher precedence than FILE's current backend
2324 \(i.e. it comes earlier in `vc-handled-backends'), then register FILE in
2325 NEW-BACKEND, using the version number from the current backend as the
2326 base level. If NEW-BACKEND has a lower precedence than the current
2327 backend, then commit all changes that were made under the current
2328 backend to NEW-BACKEND, and unregister FILE from the current backend.
2329 \(If FILE is not yet registered under NEW-BACKEND, register it.)"
2335 ;; move if new-backend comes later in vc-handled-backends
2343 ;; `registered' might have switched under us.
2348 ;; Go back to the base unmodified file.
2353 ;; If we have a local copy of the unmodified file, handle that
2354 ;; here and not in vc-revert-file because we don't want to
2355 ;; delete that copy -- it is still useful for OLD-BACKEND.
2378 "Default implementation of `vc-unregister', signals an error."
2382 "Let BACKEND receive FILE from another version control system."
2386 "Rename OLDMASTER to be the master file for NEWFILE based on TEMPLATES."
2391 ;; List of potential master files for `newfile'
2394 templates)))
2399 oldmaster
2401 ;; If possible, keep the master file in the same directory.
2404 dir))
2406 masters)
2407 ;; If not, just use the first possible place.
2413 masters)
2416 ;;;###autoload
2418 "Rename file OLD to NEW, and rename its master file likewise."
2420 ;; There are several ways of renaming files under CVS 1.3, but they all
2421 ;; have serious disadvantages. See the FAQ (available from think.com in
2422 ;; pub/cvs/). I'd rather send the user an error, than do something he might
2423 ;; consider to be wrong. When the famous, long-awaited rename database is
2424 ;; implemented things might change for the better. This is unlikely to occur
2425 ;; until CVS 2.0 is released. --ceder 1994-01-23 21:27:51
2440 ;; Move the actual file (unless the backend did it already)
2443 ;; ?? Renaming a file might change its contents due to keyword expansion.
2444 ;; We should really check out a new copy if the old copy was precisely equal
2445 ;; to some checked in version. However, testing for this is tricky....
2454 ;; Only defined in very recent Emacsen
2457 ;;;###autoload
2459 "Find change log file and add entries from recent version control logs.
2460 Normally, find log entries for all registered files in the default
2461 directory.
2463 With prefix arg of \\[universal-argument], only find log entries for the current buffer's file.
2465 With any numeric prefix arg, find log entries for all currently visited
2466 files that are under version control. This puts all the entries in the
2467 log for the default directory, which may not be appropriate.
2469 From a program, any ARGS are assumed to be filenames for which
2470 log entries should be gathered."
2477 file)
2483 files))
2485 ;; Don't supply any filenames to backend; this means
2486 ;; it should find all relevant files relative to
2487 ;; the default-directory.
2488 nil)))
2493 "Default implementation of update-changelog.
2494 Uses `rcs2log' which only works for RCS and CVS."
2495 ;; FIXME: We (c|sh)ould add support for cvs2cl
2498 ;; Presumably not portable to non-Unixy systems, along with rcs2log:
2503 temporary-file-directory))))
2509 user-mail-address)))
2523 exec-directory)
2525 "-c" changelog
2533 f
2535 files)))
2536 "done"
2545 ;;; Annotate functionality
2547 ;; Declare globally instead of additional parameter to
2548 ;; temp-buffer-show-function (not possible to pass more than one
2549 ;; parameter).
2555 Return NIL if no match made. Associations are made based on
2556 `vc-annotate-buffers'."
2560 "Major mode for buffers displaying output from the `annotate' command.
2562 You can use the mode-specific menu to alter the time-span of the used
2563 colors. See variable `vc-annotate-menu-elements' for customizing the
2564 menu items."
2568 "Use the default color spectrum for VC Annotate mode."
2572 nil
2577 "Add the menu 'Annotate' to the menu bar in VC-Annotate mode."
2582 '("Default" . vc-annotate-display-default))
2583 (let ((menu-elements vc-annotate-menu-elements))
2584 (while menu-elements
2585 (let* ((element (car menu-elements))
2586 (days (round (* element
2587 (vc-annotate-car-last-cons vc-annotate-color-map)
2588 0.7585))))
2589 (setq menu-elements (cdr menu-elements))
2590 (define-key vc-annotate-mode-menu
2591 (vector days)
2592 (cons (format "Span %d days"
2593 days)
2594 `(lambda ()
2595 ,(format "Use colors spanning %d days" days)
2596 (interactive)
2597 (message "Redisplaying annotation...")
2598 (vc-annotate-display
2599 (get-buffer (buffer-name))
2600 (vc-annotate-time-span vc-annotate-color-map ,element)
2601 (vc-annotate-get-backend (current-buffer)))
2602 (message "Redisplaying annotation...done"))))))))
2605 ;;;; (defun vc-BACKEND-annotate-command (file buffer) ...)
2606 ;;;; Execute "annotate" on FILE by using `call-process' and insert
2607 ;;;; the contents in BUFFER.
2609 ;;;###autoload
2610 (defun vc-annotate (ratio)
2613 are displayed in red, old in blue. A prefix argument specifies a
2614 factor for stretching the time scale.
2616 `vc-annotate-menu-elements' customizes the menu elements of the
2617 mode-specific menu. `vc-annotate-color-map' and
2618 `vc-annotate-very-old-color' defines the mapping of time to
2619 colors. `vc-annotate-background' specifies the background color."
2620 (interactive "p")
2621 (vc-ensure-vc-buffer)
2622 (message "Annotating...")
2623 (let ((temp-buffer-name (concat "*Annotate " (buffer-name) "*"))
2624 (temp-buffer-show-function 'vc-annotate-display)
2625 (vc-annotate-ratio ratio)
2626 (vc-annotate-backend (vc-backend (buffer-file-name))))
2627 (if (not (vc-find-backend-function vc-annotate-backend 'annotate-command))
2628 (error "Sorry, annotating is not implemented for %s"
2629 vc-annotate-backend))
2630 (with-output-to-temp-buffer temp-buffer-name
2631 (vc-call-backend vc-annotate-backend 'annotate-command
2632 (file-name-nondirectory (buffer-file-name))
2633 (get-buffer temp-buffer-name)))
2634 ;; Don't use the temp-buffer-name until the buffer is created
2635 ;; (only after `with-output-to-temp-buffer'.)
2636 (setq vc-annotate-buffers
2637 (append vc-annotate-buffers
2638 (list (cons (get-buffer temp-buffer-name) vc-annotate-backend)))))
2639 (message "Annotating... done"))
2642 (defun vc-annotate-car-last-cons (a-list)
2643 "Return car of last cons in association list A-LIST."
2644 (if (not (eq nil (cdr a-list)))
2645 (vc-annotate-car-last-cons (cdr a-list))
2646 (car (car a-list))))
2648 (defun vc-annotate-time-span (a-list span &optional quantize)
2649 "Apply factor SPAN to the time-span of association list A-LIST.
2650 Return the new alist.
2651 Optionally quantize to the factor of QUANTIZE."
2652 ;; Apply span to each car of every cons
2653 (if (not (eq nil a-list))
2654 (append (list (cons (* (car (car a-list)) span)
2655 (cdr (car a-list))))
2656 (vc-annotate-time-span (nthcdr (or quantize ; optional
2657 1) ; Default to cdr
2658 a-list) span quantize))))
2660 (defun vc-annotate-compcar (threshold a-list)
2661 "Test successive cons cells of association list A-LIST against THRESHOLD.
2662 Return the first cons cell which car is not less than THRESHOLD,
2663 nil otherwise"
2664 (let ((i 1)
2665 (tmp-cons (car a-list)))
2666 (while (and tmp-cons (< (car tmp-cons) threshold))
2667 (setq tmp-cons (car (nthcdr i a-list)))
2668 (setq i (+ i 1)))
2669 tmp-cons)) ; Return the appropriate value
2672 ;;;; (defun vc-BACKEND-annotate-difference (point) ...)
2673 ;;;;
2674 ;;;; Return the difference between the age of the line at point and
2675 ;;;; the current time. Return NIL if there is no more comparison to
2676 ;;;; be made in the buffer. Return value as defined for
2677 ;;;; `current-time'. You can safely assume that point is placed at
2678 ;;;; the beginning of each line, starting at `point-min'. The buffer
2679 ;;;; that point is placed in is the Annotate output, as defined by
2680 ;;;; the relevant backend.
2682 (defun vc-annotate-display (buffer &optional color-map backend)
2683 "Do the VC-Annotate display in BUFFER using COLOR-MAP.
2684 The original annotating file is supposed to be handled by BACKEND.
2685 If BACKEND is NIL, variable VC-ANNOTATE-BACKEND is used instead.
2686 This function is destructive on VC-ANNOTATE-BACKEND when BACKEND is non-nil."
2688 ;; Handle the case of the global variable vc-annotate-ratio being
2689 ;; set. This variable is used to pass information from function
2690 ;; vc-annotate since it is not possible to use another parameter
2691 ;; (see temp-buffer-show-function).
2692 (if (and (not color-map) vc-annotate-ratio)
2693 ;; This will only be true if called from vc-annotate with ratio
2694 ;; being non-nil.
2695 (setq color-map (vc-annotate-time-span vc-annotate-color-map
2696 vc-annotate-ratio)))
2697 (set-buffer buffer)
2698 (display-buffer buffer)
2699 (if (not vc-annotate-mode) ; Turn on vc-annotate-mode if not done
2700 (vc-annotate-mode))
2701 (goto-char (point-min)) ; Position at the top of the buffer.
2702 ;; Delete old overlays
2703 (mapcar
2704 (lambda (overlay)
2705 (if (overlay-get overlay 'vc-annotation)
2706 (delete-overlay overlay)))
2707 (overlays-in (point-min) (point-max)))
2708 (goto-char (point-min)) ; Position at the top of the buffer.
2710 (if backend (setq vc-annotate-backend backend)) ; Destructive on `vc-annotate-backend'
2712 (let ((difference (vc-call-backend vc-annotate-backend 'annotate-difference (point))))
2713 (while difference
2714 (let*
2715 ((color (or (vc-annotate-compcar
2716 difference (or color-map vc-annotate-color-map))
2717 (cons nil vc-annotate-very-old-color)))
2718 ;; substring from index 1 to remove any leading `#' in the name
2719 (face-name (concat "vc-annotate-face-" (substring (cdr color) 1)))
2720 ;; Make the face if not done.
2721 (face (or (intern-soft face-name)
2722 (let ((tmp-face (make-face (intern face-name))))
2723 (set-face-foreground tmp-face (cdr color))
2724 (if vc-annotate-background
2725 (set-face-background tmp-face vc-annotate-background))
2726 tmp-face))) ; Return the face
2727 (point (point))
2728 overlay)
2729 (forward-line 1)
2730 (setq overlay (make-overlay point (point)))
2731 (overlay-put overlay 'face face)
2732 (overlay-put overlay 'vc-annotation t))
2733 (setq difference (vc-call-backend vc-annotate-backend 'annotate-difference (point))))))
2735 \f
2736 ;; Collect back-end-dependent stuff here
2738 (defalias 'vc-default-logentry-check 'ignore)
2740 (defun vc-check-headers ()
2741 "Check if the current file has any headers in it."
2742 (interactive)
2743 (vc-call-backend (vc-backend buffer-file-name) 'check-headers))
2745 ;; Back-end-dependent stuff ends here.
2747 ;; Set up key bindings for use while editing log messages
2749 (define-derived-mode vc-log-mode text-mode "VC-Log"
2750 "Major mode for editing VC log entries.
2751 These bindings are added to the global keymap when you enter this mode:
2765 While you are entering a change log message for a version, the following
2766 additional bindings will be in effect.
2770 Whenever you do a checkin, your log comment is added to a ring of
2771 saved comments. These can be recalled as follows:
2778 Entry to the change-log submode calls the value of `text-mode-hook', then
2779 the value of `vc-log-mode-hook'.
2781 Global user options:
2782 `vc-initial-comment' If non-nil, require user to enter a change
2783 comment upon first checkin of the file.
2785 `vc-keep-workfiles' Non-nil value prevents workfiles from being
2786 deleted when changes are checked in
2788 `vc-suppress-confirm' Suppresses some confirmation prompts,
2789 notably for reversions.
2791 vc-BACKEND-header Which keywords to insert when adding headers
2794 RCS and CVS.
2796 `vc-static-header-alist' By default, version headers inserted in C files
2797 get stuffed in a static string area so that
2798 ident(RCS/CVS) or what(SCCS) can see them in
2799 the compiled object code. You can override
2800 this by setting this variable to nil, or change
2801 the header template by changing it.
2803 `vc-command-messages' if non-nil, display run messages from the
2804 actual version-control utilities (this is
2805 intended primarily for people hacking vc
2806 itself)."
2807 (make-local-variable 'vc-comment-ring-index))
2809 (defun vc-log-edit (file)
2810 "Set up `log-edit' for use with VC on FILE.
2811 If `log-edit' is not available, resort to `vc-log-mode'."
2812 (setq default-directory
2813 (if file (file-name-directory file)
2814 (with-current-buffer vc-parent-buffer default-directory)))
2815 (if (fboundp 'log-edit)
2816 (log-edit 'vc-finish-logentry nil
2817 (if file `(lambda () ',(list (file-name-nondirectory file)))
2818 ;; If FILE is nil, we were called from vc-dired.
2819 (lambda ()
2820 (with-current-buffer vc-parent-buffer
2821 (dired-get-marked-files t)))))
2822 (vc-log-mode))
2823 (set (make-local-variable 'vc-log-file) file)
2824 (make-local-variable 'vc-log-version)
2825 (set-buffer-modified-p nil)
2826 (setq buffer-file-name nil))
2828 ;;; These things should probably be generally available
2830 (defun vc-file-tree-walk (dirname func &rest args)
2831 "Walk recursively through DIRNAME.
2832 Invoke FUNC f ARGS on each VC-managed file f underneath it."
2833 (vc-file-tree-walk-internal (expand-file-name dirname) func args)
2834 (message "Traversing directory %s...done" dirname))
2836 (defun vc-file-tree-walk-internal (file func args)
2837 (if (not (file-directory-p file))
2838 (if (vc-backend file) (apply func file args))
2839 (message "Traversing directory %s..." (abbreviate-file-name file))
2840 (let ((dir (file-name-as-directory file)))
2841 (mapcar
2842 (lambda (f) (or
2843 (string-equal f ".")
2844 (string-equal f "..")
2845 (member f vc-directory-exclusion-list)
2846 (let ((dirf (expand-file-name f dir)))
2847 (or
2848 (file-symlink-p dirf);; Avoid possible loops
2849 (vc-file-tree-walk-internal dirf func args)))))
2850 (directory-files dir)))))
2852 (provide 'vc)
2854 ;;; DEVELOPER'S NOTES ON CONCURRENCY PROBLEMS IN THIS CODE
2855 ;;;
2856 ;;; These may be useful to anyone who has to debug or extend the package.
2857 ;;; (Note that this information corresponds to versions 5.x. Some of it
2858 ;;; might have been invalidated by the additions to support branching
2859 ;;; and RCS keyword lookup. AS, 1995/03/24)
2860 ;;;
2861 ;;; A fundamental problem in VC is that there are time windows between
2862 ;;; vc-next-action's computations of the file's version-control state and
2863 ;;; the actions that change it. This is a window open to lossage in a
2864 ;;; multi-user environment; someone else could nip in and change the state
2865 ;;; of the master during it.
2866 ;;;
2867 ;;; The performance problem is that rlog/prs calls are very expensive; we want
2868 ;;; to avoid them as much as possible.
2869 ;;;
2870 ;;; ANALYSIS:
2871 ;;;
2872 ;;; The performance problem, it turns out, simplifies in practice to the
2873 ;;; problem of making vc-state fast. The two other functions that call
2874 ;;; prs/rlog will not be so commonly used that the slowdown is a problem; one
2875 ;;; makes snapshots, the other deletes the calling user's last change in the
2876 ;;; master.
2877 ;;;
2878 ;;; The race condition implies that we have to either (a) lock the master
2879 ;;; during the entire execution of vc-next-action, or (b) detect and
2880 ;;; recover from errors resulting from dispatch on an out-of-date state.
2881 ;;;
2882 ;;; Alternative (a) appears to be infeasible. The problem is that we can't
2883 ;;; guarantee that the lock will ever be removed. Suppose a user starts a
2884 ;;; checkin, the change message buffer pops up, and the user, having wandered
2885 ;;; off to do something else, simply forgets about it?
2886 ;;;
2887 ;;; Alternative (b), on the other hand, works well with a cheap way to speed up
2888 ;;; vc-state. Usually, if a file is registered, we can read its locked/
2889 ;;; unlocked state and its current owner from its permissions.
2890 ;;;
2891 ;;; This shortcut will fail if someone has manually changed the workfile's
2892 ;;; permissions; also if developers are munging the workfile in several
2893 ;;; directories, with symlinks to a master (in this latter case, the
2894 ;;; permissions shortcut will fail to detect a lock asserted from another
2895 ;;; directory).
2896 ;;;
2897 ;;; Note that these cases correspond exactly to the errors which could happen
2898 ;;; because of a competing checkin/checkout race in between two instances of
2899 ;;; vc-next-action.
2900 ;;;
2901 ;;; For VC's purposes, a workfile/master pair may have the following states:
2902 ;;;
2903 ;;; A. Unregistered. There is a workfile, there is no master.
2904 ;;;
2905 ;;; B. Registered and not locked by anyone.
2906 ;;;
2907 ;;; C. Locked by calling user and unchanged.
2908 ;;;
2909 ;;; D. Locked by the calling user and changed.
2910 ;;;
2911 ;;; E. Locked by someone other than the calling user.
2912 ;;;
2913 ;;; This makes for 25 states and 20 error conditions. Here's the matrix:
2914 ;;;
2915 ;;; VC's idea of state
2916 ;;; |
2917 ;;; V Actual state RCS action SCCS action Effect
2918 ;;; A B C D E
2919 ;;; A . 1 2 3 4 ci -u -t- admin -fb -i<file> initial admin
2920 ;;; B 5 . 6 7 8 co -l get -e checkout
2921 ;;; C 9 10 . 11 12 co -u unget; get revert
2922 ;;; D 13 14 15 . 16 ci -u -m<comment> delta -y<comment>; get checkin
2923 ;;; E 17 18 19 20 . rcs -u -M -l unget -n ; get -g steal lock
2924 ;;;
2925 ;;; All commands take the master file name as a last argument (not shown).
2926 ;;;
2927 ;;; In the discussion below, a "self-race" is a pathological situation in
2928 ;;; which VC operations are being attempted simultaneously by two or more
2929 ;;; Emacsen running under the same username.
2930 ;;;
2931 ;;; The vc-next-action code has the following windows:
2932 ;;;
2933 ;;; Window P:
2934 ;;; Between the check for existence of a master file and the call to
2935 ;;; admin/checkin in vc-buffer-admin (apparent state A). This window may
2936 ;;; never close if the initial-comment feature is on.
2937 ;;;
2938 ;;; Window Q:
2939 ;;; Between the call to vc-workfile-unchanged-p in and the immediately
2940 ;;; following revert (apparent state C).
2941 ;;;
2942 ;;; Window R:
2943 ;;; Between the call to vc-workfile-unchanged-p in and the following
2944 ;;; checkin (apparent state D). This window may never close.
2945 ;;;
2946 ;;; Window S:
2947 ;;; Between the unlock and the immediately following checkout during a
2948 ;;; revert operation (apparent state C). Included in window Q.
2949 ;;;
2950 ;;; Window T:
2951 ;;; Between vc-state and the following checkout (apparent state B).
2952 ;;;
2953 ;;; Window U:
2954 ;;; Between vc-state and the following revert (apparent state C).
2955 ;;; Includes windows Q and S.
2956 ;;;
2957 ;;; Window V:
2958 ;;; Between vc-state and the following checkin (apparent state
2959 ;;; D). This window may never be closed if the user fails to complete the
2960 ;;; checkin message. Includes window R.
2961 ;;;
2962 ;;; Window W:
2963 ;;; Between vc-state and the following steal-lock (apparent
2964 ;;; state E). This window may never close if the user fails to complete
2965 ;;; the steal-lock message. Includes window X.
2966 ;;;
2967 ;;; Window X:
2968 ;;; Between the unlock and the immediately following re-lock during a
2969 ;;; steal-lock operation (apparent state E). This window may never close
2970 ;;; if the user fails to complete the steal-lock message.
2971 ;;;
2972 ;;; Errors:
2973 ;;;
2974 ;;; Apparent state A ---
2975 ;;;
2976 ;;; 1. File looked unregistered but is actually registered and not locked.
2977 ;;;
2978 ;;; Potential cause: someone else's admin during window P, with
2979 ;;; caller's admin happening before their checkout.
2980 ;;;
2981 ;;; RCS: Prior to version 5.6.4, ci fails with message
2982 ;;; "no lock set by <user>". From 5.6.4 onwards, VC uses the new
2983 ;;; ci -i option and the message is "<file>,v: already exists".
2984 ;;; SCCS: admin will fail with error (ad19).
2985 ;;;
2986 ;;; We can let these errors be passed up to the user.
2987 ;;;
2988 ;;; 2. File looked unregistered but is actually locked by caller, unchanged.
2989 ;;;
2990 ;;; Potential cause: self-race during window P.
2991 ;;;
2992 ;;; RCS: Prior to version 5.6.4, reverts the file to the last saved
2993 ;;; version and unlocks it. From 5.6.4 onwards, VC uses the new
2994 ;;; ci -i option, failing with message "<file>,v: already exists".
2995 ;;; SCCS: will fail with error (ad19).
2996 ;;;
2997 ;;; Either of these consequences is acceptable.
2998 ;;;
2999 ;;; 3. File looked unregistered but is actually locked by caller, changed.
3000 ;;;
3001 ;;; Potential cause: self-race during window P.
3002 ;;;
3003 ;;; RCS: Prior to version 5.6.4, VC registers the caller's workfile as
3004 ;;; a delta with a null change comment (the -t- switch will be
3005 ;;; ignored). From 5.6.4 onwards, VC uses the new ci -i option,
3006 ;;; failing with message "<file>,v: already exists".
3007 ;;; SCCS: will fail with error (ad19).
3008 ;;;
3009 ;;; 4. File looked unregistered but is locked by someone else.
3010 ;;;
3011 ;;; Potential cause: someone else's admin during window P, with
3012 ;;; caller's admin happening *after* their checkout.
3013 ;;;
3014 ;;; RCS: Prior to version 5.6.4, ci fails with a
3015 ;;; "no lock set by <user>" message. From 5.6.4 onwards,
3016 ;;; VC uses the new ci -i option, failing with message
3017 ;;; "<file>,v: already exists".
3018 ;;; SCCS: will fail with error (ad19).
3019 ;;;
3020 ;;; We can let these errors be passed up to the user.
3021 ;;;
3022 ;;; Apparent state B ---
3023 ;;;
3024 ;;; 5. File looked registered and not locked, but is actually unregistered.
3025 ;;;
3026 ;;; Potential cause: master file got nuked during window P.
3027 ;;;
3028 ;;; RCS: will fail with "RCS/<file>: No such file or directory"
3029 ;;; SCCS: will fail with error ut4.
3030 ;;;
3031 ;;; We can let these errors be passed up to the user.
3032 ;;;
3033 ;;; 6. File looked registered and not locked, but is actually locked by the
3034 ;;; calling user and unchanged.
3035 ;;;
3036 ;;; Potential cause: self-race during window T.
3037 ;;;
3038 ;;; RCS: in the same directory as the previous workfile, co -l will fail
3039 ;;; with "co error: writable foo exists; checkout aborted". In any other
3040 ;;; directory, checkout will succeed.
3041 ;;; SCCS: will fail with ge17.
3042 ;;;
3043 ;;; Either of these consequences is acceptable.
3044 ;;;
3045 ;;; 7. File looked registered and not locked, but is actually locked by the
3046 ;;; calling user and changed.
3047 ;;;
3048 ;;; As case 6.
3049 ;;;
3050 ;;; 8. File looked registered and not locked, but is actually locked by another
3051 ;;; user.
3052 ;;;
3053 ;;; Potential cause: someone else checks it out during window T.
3054 ;;;
3055 ;;; RCS: co error: revision 1.3 already locked by <user>
3056 ;;; SCCS: fails with ge4 (in directory) or ut7 (outside it).
3057 ;;;
3058 ;;; We can let these errors be passed up to the user.
3059 ;;;
3060 ;;; Apparent state C ---
3061 ;;;
3062 ;;; 9. File looks locked by calling user and unchanged, but is unregistered.
3063 ;;;
3064 ;;; As case 5.
3065 ;;;
3066 ;;; 10. File looks locked by calling user and unchanged, but is actually not
3067 ;;; locked.
3068 ;;;
3069 ;;; Potential cause: a self-race in window U, or by the revert's
3070 ;;; landing during window X of some other user's steal-lock or window S
3071 ;;; of another user's revert.
3072 ;;;
3073 ;;; RCS: succeeds, refreshing the file from the identical version in
3074 ;;; the master.
3075 ;;; SCCS: fails with error ut4 (p file nonexistent).
3076 ;;;
3077 ;;; Either of these consequences is acceptable.
3078 ;;;
3079 ;;; 11. File is locked by calling user. It looks unchanged, but is actually
3080 ;;; changed.
3081 ;;;
3082 ;;; Potential cause: the file would have to be touched by a self-race
3083 ;;; during window Q.
3084 ;;;
3085 ;;; The revert will succeed, removing whatever changes came with
3086 ;;; the touch. It is theoretically possible that work could be lost.
3087 ;;;
3088 ;;; 12. File looks like it's locked by the calling user and unchanged, but
3089 ;;; it's actually locked by someone else.
3090 ;;;
3091 ;;; Potential cause: a steal-lock in window V.
3092 ;;;
3093 ;;; RCS: co error: revision <rev> locked by <user>; use co -r or rcs -u
3094 ;;; SCCS: fails with error un2
3095 ;;;
3096 ;;; We can pass these errors up to the user.
3097 ;;;
3098 ;;; Apparent state D ---
3099 ;;;
3100 ;;; 13. File looks like it's locked by the calling user and changed, but it's
3101 ;;; actually unregistered.
3102 ;;;
3103 ;;; Potential cause: master file got nuked during window P.
3104 ;;;
3105 ;;; RCS: Prior to version 5.6.4, checks in the user's version as an
3106 ;;; initial delta. From 5.6.4 onwards, VC uses the new ci -j
3107 ;;; option, failing with message "no such file or directory".
3108 ;;; SCCS: will fail with error ut4.
3109 ;;;
3110 ;;; This case is kind of nasty. Under RCS prior to version 5.6.4,
3111 ;;; VC may fail to detect the loss of previous version information.
3112 ;;;
3113 ;;; 14. File looks like it's locked by the calling user and changed, but it's
3114 ;;; actually unlocked.
3115 ;;;
3116 ;;; Potential cause: self-race in window V, or the checkin happening
3117 ;;; during the window X of someone else's steal-lock or window S of
3118 ;;; someone else's revert.
3119 ;;;
3120 ;;; RCS: ci will fail with "no lock set by <user>".
3121 ;;; SCCS: delta will fail with error ut4.
3122 ;;;
3123 ;;; 15. File looks like it's locked by the calling user and changed, but it's
3124 ;;; actually locked by the calling user and unchanged.
3125 ;;;
3126 ;;; Potential cause: another self-race --- a whole checkin/checkout
3127 ;;; sequence by the calling user would have to land in window R.
3128 ;;;
3129 ;;; SCCS: checks in a redundant delta and leaves the file unlocked as usual.
3130 ;;; RCS: reverts to the file state as of the second user's checkin, leaving
3131 ;;; the file unlocked.
3132 ;;;
3133 ;;; It is theoretically possible that work could be lost under RCS.
3134 ;;;
3135 ;;; 16. File looks like it's locked by the calling user and changed, but it's
3136 ;;; actually locked by a different user.
3137 ;;;
3138 ;;; RCS: ci error: no lock set by <user>
3139 ;;; SCCS: unget will fail with error un2
3140 ;;;
3141 ;;; We can pass these errors up to the user.
3142 ;;;
3143 ;;; Apparent state E ---
3144 ;;;
3145 ;;; 17. File looks like it's locked by some other user, but it's actually
3146 ;;; unregistered.
3147 ;;;
3148 ;;; As case 13.
3149 ;;;
3150 ;;; 18. File looks like it's locked by some other user, but it's actually
3151 ;;; unlocked.
3152 ;;;
3153 ;;; Potential cause: someone released a lock during window W.
3154 ;;;
3155 ;;; RCS: The calling user will get the lock on the file.
3156 ;;; SCCS: unget -n will fail with cm4.
3157 ;;;
3158 ;;; Either of these consequences will be OK.
3159 ;;;
3160 ;;; 19. File looks like it's locked by some other user, but it's actually
3161 ;;; locked by the calling user and unchanged.
3162 ;;;
3163 ;;; Potential cause: the other user relinquishing a lock followed by
3164 ;;; a self-race, both in window W.
3165 ;;;
3166 ;;; Under both RCS and SCCS, both unlock and lock will succeed, making
3167 ;;; the sequence a no-op.
3168 ;;;
3169 ;;; 20. File looks like it's locked by some other user, but it's actually
3170 ;;; locked by the calling user and changed.
3171 ;;;
3172 ;;; As case 19.
3173 ;;;
3174 ;;; PROBLEM CASES:
3175 ;;;
3176 ;;; In order of decreasing severity:
3177 ;;;
3178 ;;; Cases 11 and 15 are the only ones that potentially lose work.
3179 ;;; They would require a self-race for this to happen.
3180 ;;;
3181 ;;; Case 13 in RCS loses information about previous deltas, retaining
3182 ;;; only the information in the current workfile. This can only happen
3183 ;;; if the master file gets nuked in window P.
3184 ;;;
3185 ;;; Case 3 in RCS and case 15 under SCCS insert a redundant delta with
3186 ;;; no change comment in the master. This would require a self-race in
3187 ;;; window P or R respectively.
3188 ;;;
3189 ;;; Cases 2, 10, 19 and 20 do extra work, but make no changes.
3190 ;;;
3191 ;;; Unfortunately, it appears to me that no recovery is possible in these
3192 ;;; cases. They don't yield error messages, so there's no way to tell that
3193 ;;; a race condition has occurred.
3194 ;;;
3195 ;;; All other cases don't change either the workfile or the master, and
3196 ;;; trigger command errors which the user will see.
3197 ;;;
3198 ;;; Thus, there is no explicit recovery code.
3200 ;;; vc.el ends here