| blob | 8d58611cb5bc11aef28e01b0afda65cebbd03205 |
1 ;;; vc-rcs.el --- support for RCS version-control -*- lexical-binding:t -*-
3 ;; Copyright (C) 1992-2016 Free Software Foundation, Inc.
5 ;; Author: FSF (see vc.el for full credits)
6 ;; Maintainer: Andre Spiegel <spiegel@gnu.org>
7 ;; Package: vc
9 ;; This file is part of GNU Emacs.
11 ;; GNU Emacs is free software: you can redistribute it and/or modify
12 ;; it under the terms of the GNU General Public License as published by
13 ;; the Free Software Foundation, either version 3 of the License, or
14 ;; (at your option) any later version.
16 ;; GNU Emacs is distributed in the hope that it will be useful,
17 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
18 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
19 ;; GNU General Public License for more details.
21 ;; You should have received a copy of the GNU General Public License
22 ;; along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.
24 ;;; Commentary:
26 ;; See vc.el
28 ;; Some features will not work with ancient RCS versions. Where
29 ;; appropriate, VC finds out which version you have, and allows or
30 ;; disallows those features.
32 ;; You can support the RCS -x option by customizing vc-rcs-master-templates.
34 ;;; Code:
36 ;;;
37 ;;; Customization options
38 ;;;
45 "VC RCS backend."
50 "The release number of your RCS installation, as a string.
51 If nil, VC itself computes this value when it is first needed."
58 "Switches for registering a file in RCS.
59 A string or list of strings passed to the checkin program by
61 If t, use no switches."
70 "String or list of strings specifying switches for RCS diff under VC.
71 If nil, use the value of `vc-diff-switches'. If t, use no switches."
80 "Header keywords to be inserted by `vc-insert-headers'."
86 "Indicates whether rcsdiff understands the --brief option.
87 The value is either `yes', `no', or nil. If it is nil, VC tries
88 to use --brief and sets this variable to remember whether it worked."
92 ;; This needs to be autoloaded because vc-rcs-registered uses it (via
93 ;; vc-default-registered), and vc-hooks needs to be able to check
94 ;; for a registered backend without loading every backend.
95 ;;;###autoload
98 "Where to look for RCS master files.
99 For a description of possible values, see `vc-check-master-templates'."
104 function)))
108 \f
109 ;;; Properties of the backend
114 "RCS-specific version of `vc-checkout-model'."
116 result)
125 ;;;
126 ;;; State-querying functions
127 ;;;
129 ;; The autoload cookie below places vc-rcs-registered directly into
130 ;; loaddefs.el, so that vc-rcs.el does not need to be loaded for
131 ;; every file that is visited.
132 ;;;###autoload
137 "Implementation of `vc-state' for RCS."
139 'unregistered
144 ;; vc-working-revision might not be known; in that case the
145 ;; property is nil. vc-rcs-fetch-master-state knows how to
146 ;; handle that.
151 state
153 'up-to-date
155 'unlocked-changes
172 "RCS-specific version of `vc-working-revision'."
183 "Return non-nil if workfile version of FILE is the latest on its branch.
184 When VERSION is given, perform check for that version."
190 ;; Compare VERSION to the head version number.
193 ;; If we are not on the trunk, we need to examine the
194 ;; whole current branch.
199 "Has FILE remained unchanged since last checkout?"
200 ;; Try to use rcsdiff --brief. If rcsdiff does not understand that,
201 ;; do a double take and remember the fact for the future
212 ;; The workfile is unchanged if rcsdiff found no differences.
215 \f
216 ;;;
217 ;;; State-changing functions
218 ;;;
221 "Create a new RCS repository."
222 ;; RCS is totally file-oriented, so all we have to do is make the directory.
228 "Register FILES into the RCS version-control system.
229 Automatically retrieve a read-only version of the file with keywords expanded.
230 COMMENT can be used to provide an initial description for each FILES.
231 Passes either `vc-rcs-register-switches' or `vc-register-switches'
232 to the RCS command."
243 ;; if available, use the secure registering option
245 "-u"
246 ;; Some old MS-Windows ports of RCS crash when "ci -i" is
247 ;; invoked without -t; indulge them.
250 ;; parse output to find master file name and workfile version
257 ;; if we couldn't find the master name,
258 ;; run vc-rcs-registered to get it
259 ;; (will be stored into the vc-master-name property)
263 name
265 name
270 nil t)
274 "Return non-nil if RCS thinks it would be responsible for registering FILE."
275 ;; TODO: check for all the patterns in vc-rcs-master-templates
278 file
282 "Implementation of receive-file for RCS."
290 "Unregister FILE from RCS.
291 If this leaves the RCS subdirectory empty, ask the user
292 whether to remove it."
302 ;; check whether RCS dir is empty, i.e. it does not
303 ;; contain any files except "." and ".."
310 "RCS-specific version of `vc-backend-checkin'."
312 ;; Now operate on the files
316 ;; Force branch creation if an appropriate
317 ;; default branch has been set.
319 default-branch
321 default-branch)
327 ;; if available, use the secure check-in option
331 switches)
334 ;; determine the new workfile version
344 ;; if we got to a different branch, adjust the default
345 ;; branch accordingly
353 ;; If this is an old (pre-1992!) RCS release, we might have
354 ;; to remove a remaining lock.
356 ;; exit status of 1 is also accepted.
357 ;; It means that the lock was removed before.
369 "Retrieve a copy of a saved version of FILE. If FILE is a directory,
370 attempt the checkout for all registered files beneath it."
374 switches)
377 ;; Change buffers to get local value of vc-checkout-switches.
380 ;; Save this buffer's default-directory
381 ;; and use save-excursion to make sure it is restored
382 ;; in the same buffer it was saved in.
385 ;; Adjust the default-directory so that the check-out creates
386 ;; the file in the right place.
389 ;; if we should go to the head of the trunk,
390 ;; clear the default branch first
393 ;; now do the checkout
396 ;; If locking is not strict, force to overwrite
397 ;; the writable workfile.
399 "-l"
401 ;; a literal revision was specified
407 ;; no revision specified:
408 ;; use current workfile version
409 workrev
410 ;; REV is t ...
412 ;; ... go to head of current branch
414 ;; ... go to head of trunk
416 nil)
418 switches)
419 ;; determine the new workfile version
424 ;; if necessary, adjust the default branch
427 file
431 new-version)))))
435 "Revert FILE to the version it was based on. If FILE is a directory,
436 revert all registered files beneath it."
444 "Accept a file merge request, prompting for revisions."
450 second-revision)
458 "Second RCS revision: "
461 ;; We want to merge an entire branch. Set revisions
462 ;; accordingly, so that vc-rcs-merge understands us.
464 ;; first-revision must be the starting point of the branch
469 "Merge changes into current working copy of FILE.
470 The changes are between FIRST-VERSION and SECOND-VERSION."
477 "Steal the lock on the current workfile for FILE and revision REV.
478 If FILE is a directory, steal the lock on all registered files beneath it.
479 Needs RCS 5.6.2 or later for -M."
483 ;; Do a real checkout after stealing the lock, so that we see
484 ;; expanded headers.
486 ;; Must clear any headers here because they wouldn't
487 ;; show that the file is locked now.
492 ;; save-excursion may be able to relocate point and mark
493 ;; properly. If it fails, vc-restore-buffer-context
494 ;; will give it a second try.
503 "Modify the change comments change on FILES on a specified REV. If FILE is a
504 directory the operation is applied to all registered files beneath it."
509 \f
510 ;;;
511 ;;; History functions
512 ;;;
526 _start-revision-ignored limit)
527 "Print commit log associated with FILES into specified BUFFER.
528 Remaining arguments are ignored.
529 If FILE is a directory the operation is applied to all registered
530 files beneath it."
538 "Get a difference report using RCS between two sets of files."
540 ;; The repo is local, so this is fast anyway.
549 "Return the administrative directory of FILE."
553 "Return a string with all log entries stored in BACKEND for FILE."
555 ;; Has to be written this way, this function is used by the CVS backend too
557 ;; Remove cruft
573 ;; Return the de-crufted comment list
577 "Annotate FILE, inserting the results in BUFFER.
578 Optional arg REVISION is a revision to annotate from."
580 ;; Aside from the "head revision on the trunk", the instructions for
581 ;; each revision on the trunk are an ordered list of kill and insert
582 ;; commands necessary to go from the chronologically-following
583 ;; revision to this one. That is, associated with revision N are
584 ;; edits that applied to revision N+1 would result in revision N.
585 ;;
586 ;; On a branch, however, (some) things are inverted: the commands
587 ;; listed are those necessary to go from the chronologically-preceding
588 ;; revision to this one. That is, associated with revision N are
589 ;; edits that applied to revision N-1 would result in revision N.
590 ;;
591 ;; So, to get per-line history info, we apply reverse-chronological
592 ;; edits, starting with the head revision on the trunk, all the way
593 ;; back through the initial revision (typically "1.1" or similar),
594 ;; then apply forward-chronological edits -- keeping track of which
595 ;; revision is associated with each inserted line -- until we reach
596 ;; the desired revision for display (which may be either on the trunk
597 ;; or on a branch).
602 ;; The revision N whose instructions we currently are processing.
604 ;; Alist from the parse tree for N.
606 ;; Point and temporary string, respectively.
607 p s
608 ;; "Next-branch list". Nil means the desired revision to
609 ;; display lives on the trunk. Non-nil means it lives on a
610 ;; branch, in which case the value is a list of revision pairs
611 ;; (PARENT . CHILD), the first PARENT being on the trunk, that
612 ;; links each series of revisions in the path from the initial
613 ;; revision to the desired revision to display.
614 nbls
615 ;; "Path-accumulate-predicate plus revision/date/author".
616 ;; Until set, forward-chronological edits are not accumulated.
617 ;; Once set, its value (updated every revision) is used for
618 ;; the text property `:vc-rcs-r/d/a' for inserts during
619 ;; processing of forward-chronological instructions for N.
620 ;; See internal func `r/d/a'.
621 prda
622 ;; List of forward-chronological instructions, each of the
623 ;; form: (POS . ACTION), where POS is a buffer position. If
624 ;; ACTION is a string, it is inserted, otherwise it is taken as
625 ;; the number of characters to be deleted.
626 path
627 ;; N+1. When `cur' is "", this is the initial revision.
628 pre)
633 ;; Find which branches (if any) must be included in the edits.
635 bpt kids)
639 ;; A branchpoint may have multiple children. Find the right one.
643 ;; Start with the full text.
646 ;; Apply reverse-chronological edits on the trunk, computing and
647 ;; accumulating forward-chronological edits after some point, for
648 ;; later.
655 ;; Start accumulating the forward-chronological edits when N+1
656 ;; on the trunk is either the desired revision to display, or
657 ;; the appropriate branchpoint for it. Do this before
658 ;; updating `meta' since `r/d/a' uses N+1's `meta' value.
662 ;; Edits in the parse tree specify a line number (in the buffer
663 ;; *BEFORE* editing occurs) to start from, but line numbers
664 ;; change as a result of edits. To DTRT, we apply edits in
665 ;; order of descending buffer position so that edits further
666 ;; down in the buffer occur first w/o corrupting specified
667 ;; buffer positions of edits occurring towards the beginning of
668 ;; the buffer. In this way we avoid using markers. A pleasant
669 ;; property of this approach is ability to push instructions
670 ;; onto `path' directly, w/o need to maintain rev boundaries.
686 ;; For the initial revision, setting `:vc-rcs-r/d/a' directly is
687 ;; equivalent to pushing an insert instruction (of the entire buffer
688 ;; contents) onto `path' then erasing the buffer, but less wasteful.
690 ;; Now apply the forward-chronological edits for the trunk.
696 ;; Now apply the forward-chronological edits (directly from the
697 ;; parse-tree) for the branch(es), if necessary. We re-use vars
698 ;; `pre' and `meta' for the sake of internal func `r/d/a'.
703 prda nil)
717 ;; Lastly, for each line, insert at bol nicely-formatted history info.
718 ;; We do two passes to collect summary information used to minimize
719 ;; the annotation's usage of screen real-estate: (1) Consider rendered
720 ;; width of revision plus author together as a unit; and (2) Omit
721 ;; author entirely if all authors are the same as the user.
726 rda w a)
736 ht)
744 " "
746 ls)
747 :vc-annotate-prefix t
755 ht)))
763 "Return the current time, based at midnight of the current day, and
764 encoded as fractional days."
769 "Return the time of the next annotation (as fraction of days)
770 systime, or nil if there is none. Also, reposition point."
779 \f
780 ;;;
781 ;;; Tag system
782 ;;;
794 dir
798 \f
799 ;;;
800 ;;; Miscellaneous
801 ;;;
804 "Return t if REV is a revision on the trunk."
808 "Return the minor revision number of a revision number REV."
813 "Return the revision number immediately preceding REV for FILE,
814 or nil if there is no previous revision. This default
815 implementation works for MAJOR.MINOR-style revision numbers as
816 used by RCS and CVS."
821 ;; revision does probably not start a branch or release
824 ;; we are at the beginning of the trunk --
825 ;; don't know anything to return here
826 nil
827 ;; we are at the beginning of a branch --
828 ;; return revision of starting point
832 "Return the revision number immediately following REV for FILE,
833 or nil if there is no next revision. This default implementation
834 works for MAJOR.MINOR-style revision numbers as used by RCS
835 and CVS."
841 ;; You might think that this should be distributed with RCS, but
842 ;; apparently not. CVS sometimes provides a version of it.
843 ;; http://lists.gnu.org/archive/html/emacs-devel/2014-05/msg00288.html
848 exe)
849 ;; In the unlikely event that someone is running an
850 ;; uninstalled Emacs and wants to do something RCS-related.
853 exe)
860 "Default implementation of update-changelog.
861 Uses `rcs2log' which only works for RCS and CVS."
862 ;; FIXME: We (c|sh)ould add support for cvs2cl
865 ;; Presumably not portable to non-Unixy systems, along with rcs2log:
869 temporary-file-directory))))
877 user-mail-address)))
891 "-c" changelog
899 files)))
900 "done"
909 "Check if the current file has any headers in it."
916 "Clear RCS header value parts."
922 nil t)
928 ;; Just move the master file (using vc-rcs-master-templates).
932 ;; If the file is locked by some other user, make
933 ;; the buffer read-only. Like this, even root
934 ;; cannot modify a file that someone else has locked.
938 \f
939 ;;;
940 ;;; Internal functions
941 ;;;
944 "Return non-nil if FILE is newer than its RCS master.
945 This likely means that FILE has been changed with respect
946 to its master version."
954 "Find most recent revision on BRANCH."
959 nil t)
968 "Compute the master file's idea of the state of FILE.
969 If a WORKING-REVISION is given, compute the state of that version,
970 otherwise determine the workfile version based on the master file.
971 This function sets the properties `vc-working-revision' and
972 `vc-checkout-model' to their correct values, based on the master
973 file."
984 ;; Workfile version not known yet. Determine that first. It
985 ;; is either the head of the trunk, the head of the default
986 ;; branch, or the "default branch" itself, if that is a full
987 ;; revision number.
989 ;; no default branch
994 ;; default branch is actually a revision
996 default-branch)
998 ;; else, search for the head of the default branch
1004 ;; Check strict locking
1009 ;; Compute state of workfile version
1017 ;; not locked
1021 ;; workfile version is latest on branch
1022 'up-to-date
1023 ;; workfile version is not latest on branch
1025 ;; locked by the calling user
1028 ;; Don't call `vc-rcs-checkout-model' to avoid inf-looping.
1030 workfile-is-latest
1032 'edited
1033 ;; Locking is not used for the file, but the owner does
1034 ;; have a lock, and there is a higher version on the current
1035 ;; branch. Not sure if this can occur, and if it is right
1036 ;; to use `needs-merge' in this case.
1038 ;; locked by somebody else
1040 locking-user)
1045 "Search for RCS headers in FILE, and set properties accordingly.
1047 Returns: nil if no headers were found
1048 'rev if a workfile revision was found
1049 'rev-and-lock if revision and lock info was found"
1057 ;; search for $Id or $Header
1058 ;; -------------------------
1059 ;; The `\ 's below avoid an RCS 5.7 bug when checking in this file.
1066 ;; if found, store the revision number ...
1068 ;; ... and check for the locking state
1076 ;; unlocked revision
1078 ;;(setq locking-user 'none)
1080 ;; revision is locked by some user
1082 ;;(setq locking-user (match-string-no-properties 1))
1084 ;; everything else: false
1086 ;; unexpected information in
1087 ;; keyword string --> quit
1089 ;; search for $Revision
1090 ;; --------------------
1093 nil t)
1094 ;; if found, store the revision number ...
1096 ;; and see if there's any lock information
1100 ;;(setq locking-user (match-string-no-properties 1))
1103 ;;(setq locking-user 'none)
1106 ;;(setq locking-user 'none)
1109 ;; else: nothing found
1110 ;; -------------------
1113 status))))
1116 "Compare release numbers, represented as strings.
1117 Release components are assumed cardinal numbers, not decimal fractions
1118 \(5.10 is a higher release than 5.9). Omitted fields are considered
1119 lower \(5.6.7 is earlier than 5.6.7.1). Comparison runs till the end
1120 of the string is found, or a non-numeric component shows up \(5.6.7 is
1122 some cases). This code is suitable for existing RCS release numbers.
1123 CVS releases are handled reasonably, too \(1.3 < 1.4* < 1.5)."
1144 "Return t if we have RELEASE or better."
1151 "Return the RCS release installed on this system, as a string.
1152 Return symbol `unknown' if the release cannot be deducted. The user can
1153 override this using variable `vc-rcs-release'.
1155 If the user has not set variable `vc-rcs-release' and it is nil,
1156 variable `vc-rcs-release' is set to the returned value."
1174 "Parse current buffer, presumed to be in RCS-style masterfile format.
1175 Optional arg BUFFER specifies another buffer to parse. Return an alist
1176 of two elements, w/ keys `headers' and `revisions' and values in turn
1177 sub-alists. For `headers', the values unless otherwise specified are
1178 strings and the keys are:
1180 desc -- description
1181 head -- latest revision
1183 absent if the head revision lies on the trunk
1184 access -- ???
1185 symbols -- sub-alist of (SYMBOL . REVISION) elements
1189 expand -- may be absent; ???
1191 For `revisions', the car is REVISION (string), the cdr a sub-alist,
1192 with string values (unless otherwise specified) and keys:
1194 date -- a time value (like that returned by `encode-time'); as a
1195 special case, a year value less than 100 is augmented by 1900
1196 author -- username
1198 branches -- list of revisions that begin branches from this revision
1201 log -- change log entry
1202 text -- for the head revision on the trunk, the body of the file;
1203 other revisions have `:insn' instead
1204 :insn -- for non-head revisions, a list of parsed instructions
1207 - `(START k COUNT)' -- kill COUNT lines
1208 - `(START i TEXT)' -- insert TEXT (a string)
1209 The list is in descending order by START.
1211 The `:insn' key is a keyword to distinguish it as a vc-rcs.el extension."
1214 ;; An RCS masterfile can be viewed as containing four regular (for the
1215 ;; most part) sections: (a) the "headers", (b) the "rev headers", (c)
1216 ;; the "description" and (d) the "rev bodies", in that order. In the
1217 ;; returned alist (see docstring), elements from (b) and (d) are
1218 ;; combined pairwise to form the "revisions", while those from (a) and
1219 ;; (c) are simply combined to form the "headers".
1220 ;;
1221 ;; Loosely speaking, each section contains a series of alternating
1222 ;; "tags" and "printed representations". In the (b) and (d), many
1223 ;; such series can appear, and a revision number on a line by itself
1224 ;; precedes the series of tags and printed representations associated
1225 ;; with it.
1226 ;;
1227 ;; In (a) and (b), the printed representations (with the exception of
1228 ;; the `comment' tag in the headers) terminate with a semicolon, which
1229 ;; is NOT part of the "value" finally associated with the tag. All
1230 ;; other printed representations are in "@@-format"; there is an "@",
1231 ;; the middle part (to be translated into the value), another "@" and
1232 ;; a newline. Each "@@" in the middle part indicates the position of
1233 ;; a single "@" (and consequently the requirement of an additional
1234 ;; initial step when translating to the value).
1235 ;;
1236 ;; Parser state includes vars that collect parts of the return value...
1238 ;; ... as well as vars that support a single-pass, tag-assisted,
1239 ;; minimal-data-copying scan. Basically -- skirting around the
1240 ;; grouping by revision required in (b) and (d) -- we repeatedly
1241 ;; and context-sensitively read a tag (that MUST be present),
1242 ;; determine the bounds of the printed representation, translate
1243 ;; it into a value, and push the tag plus value onto one of the
1244 ;; collection vars. Finally, we return the parse tree
1245 ;; incorporating the values of the collection vars (see "rv").
1246 ;;
1247 ;; A symbol or string to keep track of context (for error messages).
1248 context
1249 ;; A symbol, the current tag.
1250 tok
1251 ;; Region (begin and end buffer positions) of the printed
1252 ;; representation for the current tag.
1253 b e
1254 ;; A list of buffer positions where "@@" can be found within the
1255 ;; printed representation region. For each location, we push two
1256 ;; elements onto the list, 1+ and 2+ the location, respectively,
1257 ;; with the 2+ appearing at the head. In this way, the expression
1258 ;; `(,e ,@@-holes ,b)
1259 ;; describes regions that can be concatenated (in reverse order)
1260 ;; to "de-@@-format" the printed representation as the first step
1261 ;; to translating it into some value. See internal func `gather'.
1291 acc)
1295 acc)
1303 ;; headers
1317 two))
1323 t))
1324 headers)
1332 ;; rev headers
1341 b e)
1343 ;; Hack the year -- verified to be the
1344 ;; same algorithm used in RCS 5.7.
1354 revs)
1357 ;; desc
1360 ;; rev bodies
1362 ;; Element of `revs' that initially holds only header info.
1363 ;; "Pairwise combination" occurs when we add body info.
1364 rev
1365 ;; Components of the editing commands (aside from the actual
1366 ;; text) that comprise the `text' printed representations
1367 ;; (not including the "head" revision).
1368 cmd start act
1369 ;; Ascending (reversed) `@-holes' which the internal func
1370 ;; `incg' pops to effect incremental gathering.
1371 asc
1372 ;; Function to extract text (for the `a' command), either
1373 ;; `incg' or `buffer-substring-no-properties'. (This is
1374 ;; for speed; strictly speaking, it is sufficient to use
1375 ;; only the former since it behaves identically to the
1376 ;; latter in the absence of "@@".)
1377 sub)
1383 ;; Self-deprecate when work is done.
1384 ;; Folding many dimensions into one.
1385 ;; Thanks B.Mandelbrot, for complex sum.
1386 ;; O beauteous math! --the Unvexed Bum
1395 context))))
1397 ;; For rev body `text' tags, delay translation slightly...
1399 ;; ... until we decide which tag and value is appropriate to
1400 ;; collect. For the "head" revision, compute the value of the
1401 ;; `text' printed representation by simple `gather'. For all
1402 ;; other revisions, replace the `text' tag+value with `:insn'
1403 ;; plus value, always scanning in-place.
1419 (?d
1420 ;; `d' means "delete lines".
1421 ;; For Emacs spirit, we use `k' for "kill".
1423 (?a
1424 ;; `a' means "append after this line" but
1425 ;; internally we normalize it so that START
1426 ;; specifies the actual line for insert, thus
1427 ;; requiring less hair in the realization algs.
1428 ;; For Emacs spirit, we use `i' for "insert".
1433 cmd context)))
1434 acc))
1437 ;; rv
1443 ;;; vc-rcs.el ends here