| blob | 0f2551d49a3221a48063929aab7ad834e54deb02 |
1 ;;; vc-rcs.el --- support for RCS version-control
3 ;; Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000,
4 ;; 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
6 ;; Author: FSF (see vc.el for full credits)
7 ;; Maintainer: Andre Spiegel <spiegel@gnu.org>
9 ;; $Id$
11 ;; This file is part of GNU Emacs.
13 ;; GNU Emacs is free software; you can redistribute it and/or modify
14 ;; it under the terms of the GNU General Public License as published by
15 ;; the Free Software Foundation; either version 3, or (at your option)
16 ;; any later version.
18 ;; GNU Emacs is distributed in the hope that it will be useful,
19 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
20 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
21 ;; GNU General Public License for more details.
23 ;; You should have received a copy of the GNU General Public License
24 ;; along with GNU Emacs; see the file COPYING. If not, write to the
25 ;; Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
26 ;; Boston, MA 02110-1301, USA.
28 ;;; Commentary:
30 ;; See vc.el
32 ;; TODO:
33 ;; - remove call to vc-expand-dirs by implementing our own (which can just
34 ;; list the RCS subdir instead).
36 ;;; Code:
38 ;;;
39 ;;; Customization options
40 ;;;
47 "*The release number of your RCS installation, as a string.
48 If nil, VC itself computes this value when it is first needed."
55 "*Extra switches for registering a file in RCS.
56 A string or list of strings. These are passed to the checkin program
62 string))
67 "*A string or list of strings specifying extra switches for rcsdiff under VC."
72 string))
77 "*Header keywords to be inserted by `vc-insert-headers'."
83 "*Indicates whether rcsdiff understands the --brief option.
84 The value is either `yes', `no', or nil. If it is nil, VC tries
85 to use --brief and sets this variable to remember whether it worked."
89 ;;;###autoload
92 "*Where to look for RCS master files.
93 For a description of possible values, see `vc-check-master-templates'."
98 function)))
102 \f
103 ;;; Properties of the backend
108 ;;;
109 ;;; State-querying functions
110 ;;;
112 ;;; The autoload cookie below places vc-rcs-registered directly into
113 ;;; loaddefs.el, so that vc-rcs.el does not need to be loaded for
114 ;;; every file that is visited. The definition is repeated below
115 ;;; so that Help and etags can find it.
117 ;;;###autoload (defun vc-rcs-registered (f) (vc-default-registered 'RCS f))
121 "Implementation of `vc-state' for RCS."
126 ;; vc-working-revision might not be known; in that case the
127 ;; property is nil. vc-rcs-fetch-master-state knows how to
128 ;; handle that.
133 state
135 'up-to-date
137 'unlocked-changes
141 "State heuristic for RCS."
148 ;; If the headers say that the file is not locked, the
149 ;; permissions can tell us whether locking is used for
150 ;; the file or not.
158 'edited
162 state)
173 'edited
174 owner-name)
176 'edited
179 ;; Strange permissions. Fall through to
180 ;; expensive state computation.
185 "RCS-specific version of `vc-working-revision'."
194 "Return non-nil if workfile version of FILE is the latest on its branch.
195 When VERSION is given, perform check for that version."
201 ;; Compare VERSION to the head version number.
204 ;; If we are not on the trunk, we need to examine the
205 ;; whole current branch.
210 "RCS-specific version of `vc-checkout-model'."
221 "RCS-specific implementation of `vc-workfile-unchanged-p'."
222 ;; Try to use rcsdiff --brief. If rcsdiff does not understand that,
223 ;; do a double take and remember the fact for the future
234 ;; The workfile is unchanged if rcsdiff found no differences.
245 \f
246 ;;;
247 ;;; State-changing functions
248 ;;;
251 "Create a new RCS repository."
252 ;; RCS is totally file-oriented, so all we have to do is make the directory
256 "Register FILES into the RCS version-control system.
257 REV is the optional revision number for the files. COMMENT can be used
258 to provide an initial description for each FILES.
260 `vc-register-switches' and `vc-rcs-register-switches' are passed to
261 the RCS command (in that order).
263 Automatically retrieve a read-only version of the file with keywords
264 expanded if `vc-keep-workfiles' is non-nil, otherwise, delete the workfile."
273 ;; if available, use the secure registering option
278 ;; parse output to find master file name and workfile version
285 ;; if we couldn't find the master name,
286 ;; run vc-rcs-registered to get it
287 ;; (will be stored into the vc-name property)
291 name
293 name
298 nil t)
302 "Return non-nil if RCS thinks it would be responsible for registering FILE."
303 ;; TODO: check for all the patterns in vc-rcs-master-templates
307 "Implementation of receive-file for RCS."
315 "Unregister FILE from RCS.
316 If this leaves the RCS subdirectory empty, ask the user
317 whether to remove it."
326 ;; check whether RCS dir is empty, i.e. it does not
327 ;; contain any files except "." and ".."
334 "RCS-specific version of `vc-backend-checkin'."
336 ;; Now operate on the files
340 ;; Force branch creation if an appropriate
341 ;; default branch has been set.
343 default-branch
345 default-branch)
351 ;; if available, use the secure check-in option
355 switches)
358 ;; determine the new workfile version
368 ;; if we got to a different branch, adjust the default
369 ;; branch accordingly
377 ;; If this is an old RCS release, we might have
378 ;; to remove a remaining lock.
380 ;; exit status of 1 is also accepted.
381 ;; It means that the lock was removed before.
393 "Retrieve a copy of a saved version of FILE."
395 switches)
398 ;; Change buffers to get local value of vc-checkout-switches.
401 ;; Save this buffer's default-directory
402 ;; and use save-excursion to make sure it is restored
403 ;; in the same buffer it was saved in.
406 ;; Adjust the default-directory so that the check-out creates
407 ;; the file in the right place.
410 ;; if we should go to the head of the trunk,
411 ;; clear the default branch first
414 ;; now do the checkout
417 ;; If locking is not strict, force to overwrite
418 ;; the writable workfile.
422 ;; a literal revision was specified
428 ;; no revision specified:
429 ;; use current workfile version
430 workrev
431 ;; REV is t ...
433 ;; ... go to head of current branch
435 ;; ... go to head of trunk
437 nil)
439 switches)
440 ;; determine the new workfile version
445 ;; if necessary, adjust the default branch
448 file
452 new-version)))))
456 "Roll back, undoing the most recent checkins of FILES."
465 discard file)))
469 ;; Check out the most recent remaining version. If it
470 ;; fails, because the whole branch got deleted, do a
471 ;; double-take and check out the version where the branch
472 ;; started.
484 ;; vc-do-command popped up a window with
485 ;; the error message. Get rid of it, by
486 ;; restoring the old window configuration.
488 ;; No, it was some other error: re-signal it.
492 "Revert FILE to the version it was based on."
498 "Merge changes into current working copy of FILE.
499 The changes are between FIRST-VERSION and SECOND-VERSION."
506 "Steal the lock on the current workfile for FILE and revision REV.
507 Needs RCS 5.6.2 or later for -M."
509 ;; Do a real checkout after stealing the lock, so that we see
510 ;; expanded headers.
514 "Modify the change comments change on FILES on a specified REV."
519 \f
520 ;;;
521 ;;; History functions
522 ;;;
525 "Get change log associated with FILE."
529 "Get a difference report using RCS between two sets of files."
539 "Remove all non-comment information from log output."
557 "Annotate FILE, inserting the results in BUFFER.
558 Optional arg REVISION is a revision to annotate from."
560 ;; Aside from the "head revision on the trunk", the instructions for
561 ;; each revision on the trunk are an ordered list of kill and insert
562 ;; commands necessary to go from the chronologically-following
563 ;; revision to this one. That is, associated with revision N are
564 ;; edits that applied to revision N+1 would result in revision N.
565 ;;
566 ;; On a branch, however, (some) things are inverted: the commands
567 ;; listed are those necessary to go from the chronologically-preceding
568 ;; revision to this one. That is, associated with revision N are
569 ;; edits that applied to revision N-1 would result in revision N.
570 ;;
571 ;; So, to get per-line history info, we apply reverse-chronological
572 ;; edits, starting with the head revision on the trunk, all the way
573 ;; back through the initial revision (typically "1.1" or similar),
574 ;; then apply forward-chronological edits -- keeping track of which
575 ;; revision is associated with each inserted line -- until we reach
576 ;; the desired revision for display (which may be either on the trunk
577 ;; or on a branch).
582 ;; The revision N whose instructions we currently are processing.
584 ;; Alist from the parse tree for N.
586 ;; Point and temporary string, respectively.
587 p s
588 ;; "Next-branch list". Nil means the desired revision to
589 ;; display lives on the trunk. Non-nil means it lives on a
590 ;; branch, in which case the value is a list of revision pairs
591 ;; (PARENT . CHILD), the first PARENT being on the trunk, that
592 ;; links each series of revisions in the path from the initial
593 ;; revision to the desired revision to display.
594 nbls
595 ;; "Path-accumulate-predicate plus revision/date/author".
596 ;; Until set, forward-chronological edits are not accumulated.
597 ;; Once set, its value (updated every revision) is used for
598 ;; the text property `:vc-rcs-r/d/a' for inserts during
599 ;; processing of forward-chronological instructions for N.
600 ;; See internal func `r/d/a'.
601 prda
602 ;; List of forward-chronological instructions, each of the
603 ;; form: (POS . ACTION), where POS is a buffer position. If
604 ;; ACTION is a string, it is inserted, otherwise it is taken as
605 ;; the number of characters to be deleted.
606 path
607 ;; N+1. When `cur' is "", this is the initial revision.
608 pre)
613 ;; Find which branches (if any) must be included in the edits.
615 bpt kids)
619 ;; A branchpoint may have multiple children. Find the right one.
623 ;; Start with the full text.
626 ;; Apply reverse-chronological edits on the trunk, computing and
627 ;; accumulating forward-chronological edits after some point, for
628 ;; later.
635 ;; Start accumulating the forward-chronological edits when N+1
636 ;; on the trunk is either the desired revision to display, or
637 ;; the appropriate branchpoint for it. Do this before
638 ;; updating `meta' since `r/d/a' uses N+1's `meta' value.
642 ;; Edits in the parse tree specify a line number (in the buffer
643 ;; *BEFORE* editing occurs) to start from, but line numbers
644 ;; change as a result of edits. To DTRT, we apply edits in
645 ;; order of descending buffer position so that edits further
646 ;; down in the buffer occur first w/o corrupting specified
647 ;; buffer positions of edits occurring towards the beginning of
648 ;; the buffer. In this way we avoid using markers. A pleasant
649 ;; property of this approach is ability to push instructions
650 ;; onto `path' directly, w/o need to maintain rev boundaries.
665 ;; For the initial revision, setting `:vc-rcs-r/d/a' directly is
666 ;; equivalent to pushing an insert instruction (of the entire buffer
667 ;; contents) onto `path' then erasing the buffer, but less wasteful.
669 ;; Now apply the forward-chronological edits for the trunk.
675 ;; Now apply the forward-chronological edits (directly from the
676 ;; parse-tree) for the branch(es), if necessary. We re-use vars
677 ;; `pre' and `meta' for the sake of internal func `r/d/a'.
682 prda nil)
695 ;; Lastly, for each line, insert at bol nicely-formatted history info.
696 ;; We do two passes to collect summary information used to minimize
697 ;; the annotation's usage of screen real-estate: (1) Consider rendered
698 ;; width of revision plus author together as a unit; and (2) Omit
699 ;; author entirely if all authors are the same as the user.
704 rda w a)
714 ht)
722 " "
724 ls)
725 :vc-annotate-prefix t
733 ht)))
739 "Return the current time, based at midnight of the current day, and
740 encoded as fractional days."
745 "Return the time of the next annotation (as fraction of days)
746 systime, or nil if there is none. Also, reposition point."
755 \f
756 ;;;
757 ;;; Snapshot system
758 ;;;
761 "Assign to FILE's latest version a given NAME."
764 \f
765 ;;;
766 ;;; Miscellaneous
767 ;;;
770 "Check if the current file has any headers in it."
777 "Implementation of vc-clear-headers for RCS."
783 nil t)
787 ;; Just move the master file (using vc-rcs-master-templates).
790 \f
791 ;;;
792 ;;; Internal functions
793 ;;;
799 "Return non-nil if FILE is newer than its RCS master.
800 This likely means that FILE has been changed with respect
801 to its master version."
809 "Find most recent revision on BRANCH."
814 nil t)
823 "Compute the master file's idea of the state of FILE.
824 If a WORKFILE-VERSION is given, compute the state of that version,
825 otherwise determine the workfile version based on the master file.
826 This function sets the properties `vc-working-revision' and
827 `vc-checkout-model' to their correct values, based on the master
828 file."
838 ;; Workfile version not known yet. Determine that first. It
839 ;; is either the head of the trunk, the head of the default
840 ;; branch, or the "default branch" itself, if that is a full
841 ;; revision number.
843 ;; no default branch
848 ;; default branch is actually a revision
850 default-branch)
852 ;; else, search for the head of the default branch
858 ;; Check strict locking
863 ;; Compute state of workfile version
871 ;; not locked
875 ;; workfile version is latest on branch
876 'up-to-date
877 ;; workfile version is not latest on branch
879 ;; locked by the calling user
883 workfile-is-latest
885 'edited
886 ;; Locking is not used for the file, but the owner does
887 ;; have a lock, and there is a higher version on the current
888 ;; branch. Not sure if this can occur, and if it is right
889 ;; to use `needs-merge' in this case.
891 ;; locked by somebody else
893 locking-user)
898 "Search for RCS headers in FILE, and set properties accordingly.
900 Returns: nil if no headers were found
901 'rev if a workfile revision was found
902 'rev-and-lock if revision and lock info was found"
910 ;; search for $Id or $Header
911 ;; -------------------------
912 ;; The `\ 's below avoid an RCS 5.7 bug when checking in this file.
919 ;; if found, store the revision number ...
921 ;; ... and check for the locking state
929 ;; unlocked revision
933 ;; revision is locked by some user
937 ;; everything else: false
939 ;; unexpected information in
940 ;; keyword string --> quit
942 ;; search for $Revision
943 ;; --------------------
946 nil t)
947 ;; if found, store the revision number ...
949 ;; and see if there's any lock information
962 ;; else: nothing found
963 ;; -------------------
973 ;; If the file has headers, we don't want to query the
974 ;; master file, because that would eliminate all the
975 ;; performance gain the headers brought us. We therefore
976 ;; use a heuristic now to find out whether locking is used
977 ;; for this file. If we trust the file permissions, and the
978 ;; file is not locked, then if the file is read-only we
979 ;; assume that locking is used for the file, otherwise
980 ;; locking is not used.
986 status))))
989 "Compare release numbers, represented as strings.
990 Release components are assumed cardinal numbers, not decimal fractions
991 \(5.10 is a higher release than 5.9\). Omitted fields are considered
992 lower \(5.6.7 is earlier than 5.6.7.1\). Comparison runs till the end
993 of the string is found, or a non-numeric component shows up \(5.6.7 is
995 some cases\). This code is suitable for existing RCS release numbers.
996 CVS releases are handled reasonably, too \(1.3 < 1.4* < 1.5\)."
1017 "Return t if we have RELEASE or better."
1024 "Return the RCS release installed on this system, as a string.
1025 Return symbol UNKNOWN if the release cannot be deducted. The user can
1026 override this using variable `vc-rcs-release'.
1028 If the user has not set variable `vc-rcs-release' and it is nil,
1029 variable `vc-rcs-release' is set to the returned value."
1047 "Parse current buffer, presumed to be in RCS-style masterfile format.
1048 Optional arg BUFFER specifies another buffer to parse. Return an alist
1049 of two elements, w/ keys `headers' and `revisions' and values in turn
1050 sub-alists. For `headers', the values unless otherwise specified are
1051 strings and the keys are:
1053 desc -- description
1054 head -- latest revision
1056 absent if the head revision lies on the trunk
1057 access -- ???
1058 symbols -- sub-alist of (SYMBOL . REVISION) elements
1062 expand -- may be absent; ???
1064 For `revisions', the car is REVISION (string), the cdr a sub-alist,
1065 with string values (unless otherwise specified) and keys:
1067 date -- a time value (like that returned by `encode-time'); as a
1068 special case, a year value less than 100 is augmented by 1900
1069 author -- username
1071 branches -- list of revisions that begin branches from this revision
1074 log -- change log entry
1075 text -- for the head revision on the trunk, the body of the file;
1076 other revisions have `:insn' instead
1077 :insn -- for non-head revisions, a list of parsed instructions
1080 - `(START k COUNT)' -- kill COUNT lines
1081 - `(START i TEXT)' -- insert TEXT (a string)
1082 The list is in descending order by START.
1084 The `:insn' key is a keyword to distinguish it as a vc-rcs.el extension."
1087 ;; An RCS masterfile can be viewed as containing four regular (for the
1088 ;; most part) sections: (a) the "headers", (b) the "rev headers", (c)
1089 ;; the "description" and (d) the "rev bodies", in that order. In the
1090 ;; returned alist (see docstring), elements from (b) and (d) are
1091 ;; combined pairwise to form the "revisions", while those from (a) and
1092 ;; (c) are simply combined to form the "headers".
1093 ;;
1094 ;; Loosely speaking, each section contains a series of alternating
1095 ;; "tags" and "printed representations". In the (b) and (d), many
1096 ;; such series can appear, and a revision number on a line by itself
1097 ;; precedes the series of tags and printed representations associated
1098 ;; with it.
1099 ;;
1100 ;; In (a) and (b), the printed representations (with the exception of
1101 ;; the `comment' tag in the headers) terminate with a semicolon, which
1102 ;; is NOT part of the "value" finally associated with the tag. All
1103 ;; other printed representations are in "@@-format"; there is an "@",
1104 ;; the middle part (to be translated into the value), another "@" and
1105 ;; a newline. Each "@@" in the middle part indicates the position of
1106 ;; a single "@" (and consequently the requirement of an additional
1107 ;; initial step when translating to the value).
1108 ;;
1109 ;; Parser state includes vars that collect parts of the return value...
1111 ;; ... as well as vars that support a single-pass, tag-assisted,
1112 ;; minimal-data-copying scan. Basically -- skirting around the
1113 ;; grouping by revision required in (b) and (d) -- we repeatedly
1114 ;; and context-sensitively read a tag (that MUST be present),
1115 ;; determine the bounds of the printed representation, translate
1116 ;; it into a value, and push the tag plus value onto one of the
1117 ;; collection vars. Finally, we return the parse tree
1118 ;; incorporating the values of the collection vars (see "rv").
1119 ;;
1120 ;; A symbol or string to keep track of context (for error messages).
1121 context
1122 ;; A symbol, the current tag.
1123 tok
1124 ;; Region (begin and end buffer positions) of the printed
1125 ;; representation for the current tag.
1126 b e
1127 ;; A list of buffer positions where "@@" can be found within the
1128 ;; printed representation region. For each location, we push two
1129 ;; elements onto the list, 1+ and 2+ the location, respectively,
1130 ;; with the 2+ appearing at the head. In this way, the expression
1131 ;; `(,e ,@@-holes ,b)
1132 ;; describes regions that can be concatenated (in reverse order)
1133 ;; to "de-@@-format" the printed representation as the first step
1134 ;; to translating it into some value. See internal func `gather'.
1163 acc)
1167 acc)
1176 ;; headers
1190 two))
1196 t))
1197 headers)
1205 ;; rev headers
1214 b e)
1216 ;; Hack the year -- verified to be the
1217 ;; same algorithm used in RCS 5.7.
1227 revs)
1230 ;; desc
1233 ;; rev bodies
1235 ;; Element of `revs' that initially holds only header info.
1236 ;; "Pairwise combination" occurs when we add body info.
1237 rev
1238 ;; Components of the editing commands (aside from the actual
1239 ;; text) that comprise the `text' printed representations
1240 ;; (not including the "head" revision).
1241 cmd start act
1242 ;; Ascending (reversed) `@-holes' which the internal func
1243 ;; `incg' pops to effect incremental gathering.
1244 asc
1245 ;; Function to extract text (for the `a' command), either
1246 ;; `incg' or `buffer-substring-no-properties'. (This is
1247 ;; for speed; strictly speaking, it is sufficient to use
1248 ;; only the former since it behaves identically to the
1249 ;; latter in the absense of "@@".)
1250 sub)
1254 ;; Self-deprecate when work is done.
1255 ;; Folding many dimensions into one.
1256 ;; Thanks B.Mandelbrot, for complex sum.
1257 ;; O beauteous math! --the Unvexed Bum
1266 context))))
1268 ;; For rev body `text' tags, delay translation slightly...
1270 ;; ... until we decide which tag and value is appropriate to
1271 ;; collect. For the "head" revision, compute the value of the
1272 ;; `text' printed representation by simple `gather'. For all
1273 ;; other revisions, replace the `text' tag+value with `:insn'
1274 ;; plus value, always scanning in-place.
1290 (?d
1291 ;; `d' means "delete lines".
1292 ;; For Emacs spirit, we use `k' for "kill".
1294 (?a
1295 ;; `a' means "append after this line" but
1296 ;; internally we normalize it so that START
1297 ;; specifies the actual line for insert, thus
1298 ;; requiring less hair in the realization algs.
1299 ;; For Emacs spirit, we use `i' for "insert".
1304 cmd context)))
1305 acc))
1308 ;; rv
1314 ;; arch-tag: 759b4916-5b0d-431d-b647-b185b8c652cf
1315 ;;; vc-rcs.el ends here