* New VC mode -- review request
@ 2007-10-03 10:35 Eric S. Raymond
2007-10-03 14:31 ` Dan Nicolaescu
2007-10-04 2:02 ` Richard Stallman
0 siblings, 2 replies; 20+ messages in thread
From: Eric S. Raymond @ 2007-10-03 10:35 UTC (permalink / raw)
To: emacs-devel
[-- Attachment #1: Type: text/plain, Size: 3630 bytes --]
I am the original author of the VC mode shipped with Emacs, back in 1992-1993.
Its design was well matched to the file-oriented version-control systems
(VCSes) of its day, and it has proven a useful tool. But it has long been in
need of a rewrite, for two reasons:
(1) The code has accreted cruft over the years, and
(2) the design is poorly matched to modern changeset-oriented VCSes,
beginning with Subversion and including third-generation systems such
as Mercurial and Bazaar.
Some months ago I set out to fix these problems. The principal goal of the
project was to change VC so that its primitive operations (notably
checkin/commit) take sets of files as arguments rather than single files.
The new VC implementation has two layers: a set of back-ends specific
to each VCS, and a front end that contains VC-independent control an UI logic
Over the summer I worked with Stefan Monnier and a test group (copied)
on qualifying this code. The most significant event in this process
was a felicitous mistake.
Due to a CVS command error on my part, the new back-end code and a
version of the front end with old control behavior but using the new
back ends got checked into CVS HEAD rather than a branch. Fortunately,
the new back-end code functioned without a hitch and Stefan decided
reverting it was not necessary,
Now I think it has come time for the front end to be merged. I have
been using it in my everyday development work with Subversion for months.
Stefan asked me to submit it to this list for final review, and I am
doing so. Please find it attached.
Here are the user-visible changes you should expect relative to what's
in the manual:
* The following commands now operate on filesets rather than files.
vc-next-action = C-x v v
vc-diff = C-x v =
vc-print-log = C-x v l
vc-revert = C-x v u
vc-rollback = C-x v c
vc-update = C-x v +
The current fileset is either (a) one file, when you are visiting a
buffer for a file under version control, or (b) marked files
selected in a VC Dired buffer. If you are in a derived buffer such
as a log or diff buffer, the current fileset will be that associated
with the parent buffer.
* In particular, C-x v v on a fileset of edited files should produce a
single commit rather than a separate commit for each file. This is the
big feature the mode rewrite was aimed at.
* In VC Dired mode, you must explicitly mark files to put them in a fileset.
The old behavior of operating on the file named on the current line has
been switched off.
* vc-diff works slightly differently. In the new interface you never
explicitly give it a file or directory; instead it operates on the current
fileset. As a special exception, if you run diff while visiting a buffer
that VC knows nothing about (such as a Dired listing) and it thus cannot
deduce a fileset, it will act on all version-controlled files at and below
the current directory.
* The prefix argument of vc-cancel-version is no longer processed.
There is an equivalent command (vc-rollback) also bound to C-x v c,
but it always reverts associated buffers. The old C-u
vc-cancel-version behavior was all three of dangerous, hard to
document, and prone to variation across back ends; we're better off
without it.
Changes other than these are probably bugs and you should report them.
You need not restrict criticism to outright bugs; the user interface hasn't
been reviewed or refreshed in a very long time before this, and it is
possible we could be doing things more gracefully.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
[-- Attachment #2: vc.el --]
[-- Type: text/plain, Size: 149114 bytes --]
;;; vc.el --- drive a version-control system from within Emacs
;; Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 2000,
;; 2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc.
;; Author: FSF (see below for full credits)
;; Maintainer: Andre Spiegel <spiegel@gnu.org>
;; Keywords: tools
;; $Id: vc.el,v 1.120 2007/07/24 17:46:20 esr Exp esr $
;; This file is part of GNU Emacs.
;; GNU Emacs is free software; you can redistribute it and/or modify
;; it under the terms of the GNU General Public License as published by
;; the Free Software Foundation; either version 2, or (at your option)
;; any later version.
;; GNU Emacs is distributed in the hope that it will be useful,
;; but WITHOUT ANY WARRANTY; without even the implied warranty of
;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
;; GNU General Public License for more details.
;; You should have received a copy of the GNU General Public License
;; along with GNU Emacs; see the file COPYING. If not, write to the
;; Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor,
;; Boston, MA 02110-1301, USA.
;;; Credits:
;; VC was initially designed and implemented by Eric S. Raymond
;; <esr@thyrsus.com> in 1992. Over the years, many other people have
;; contributed substantial amounts of work to VC. These include:
;;
;; Per Cederqvist <ceder@lysator.liu.se>
;; Paul Eggert <eggert@twinsun.com>
;; Sebastian Kremer <sk@thp.uni-koeln.de>
;; Martin Lorentzson <martinl@gnu.org>
;; Dave Love <fx@gnu.org>
;; Stefan Monnier <monnier@cs.yale.edu>
;; J.D. Smith <jdsmith@alum.mit.edu>
;; Andre Spiegel <spiegel@gnu.org>
;; Richard Stallman <rms@gnu.org>
;; Thien-Thi Nguyen <ttn@gnu.org>
;;
;; In July 2007 ESR returned and redesigned the mode to cope better
;; with modern version-control systems that do commits by fileset
;; rather than per individual file.
;;
;; Features in the new version:
;; * Key commands (vc-next-action = C-x v v, vc-print-log = C-x v l, vc-revert
;; = C-x v u, vc-rollback = C-x v c, vc-diff = C-x v =, vc-update = C-x v +)
;; now operate on filesets rather than individual files.
;; * The fileset for a command is either (a) all marked files in VC-dired
;; mode, (b) the currently visited file if it's under version control,
;; or (c) the current directory if the visited buffer is not under
;; version control and a wildcarding-enable flag has been set.
;;
;; If you maintain a client of the mode or customize it in your .emacs,
;; note that some backend functions which formerly took single file arguments
;; now take a list of files. These include: register, checkin, print-log,
;; rollback, and diff.
;;; Commentary:
;; This mode is fully documented in the Emacs user's manual.
;;
;; Supported version-control systems presently include CVS, RCS, GNU Arch,
;; Subversion, Meta-CVS, and SCCS (or its free replacement, CSSC).
;;
;; Some features will not work with old RCS versions. Where
;; appropriate, VC finds out which version you have, and allows or
;; disallows those features (stealing locks, for example, works only
;; from 5.6.2 onwards).
;; Even initial checkins will fail if your RCS version is so old that ci
;; doesn't understand -t-; this has been known to happen to people running
;; NExTSTEP 3.0.
;;
;; You can support the RCS -x option by customizing vc-rcs-master-templates.
;;
;; Proper function of the SCCS diff commands requires the shellscript vcdiff
;; to be installed somewhere on Emacs's path for executables.
;;
;; If your site uses the ChangeLog convention supported by Emacs, the
;; function log-edit-comment-to-change-log could prove a useful checkin hook,
;; although you might prefer to use C-c C-a (i.e. log-edit-insert-changelog)
;; from the commit buffer instead or to set `log-edit-setup-invert'.
;;
;; The vc code maintains some internal state in order to reduce expensive
;; version-control operations to a minimum. Some names are only computed
;; once. If you perform version control operations with the backend while
;; vc's back is turned, or move/rename master files while vc is running,
;; vc may get seriously confused. Don't do these things!
;;
;; Developer's notes on some concurrency issues are included at the end of
;; the file.
;;
;; ADDING SUPPORT FOR OTHER BACKENDS
;;
;; VC can use arbitrary version control systems as a backend. To add
;; support for a new backend named SYS, write a library vc-sys.el that
;; contains functions of the form `vc-sys-...' (note that SYS is in lower
;; case for the function and library names). VC will use that library if
;; you put the symbol SYS somewhere into the list of
;; `vc-handled-backends'. Then, for example, if `vc-sys-registered'
;; returns non-nil for a file, all SYS-specific versions of VC commands
;; will be available for that file.
;;
;; VC keeps some per-file information in the form of properties (see
;; vc-file-set/getprop in vc-hooks.el). The backend-specific functions
;; do not generally need to be aware of these properties. For example,
;; `vc-sys-workfile-version' should compute the focus version and
;; return it; it should not look it up in the property, and it needn't
;; store it there either. However, if a backend-specific function does
;; store a value in a property, that value takes precedence over any
;; value that the generic code might want to set (check for uses of
;; the macro `with-vc-properties' in vc.el).
;;
;; In the list of functions below, each identifier needs to be prepended
;; with `vc-sys-'. Some of the functions are mandatory (marked with a
;; `*'), others are optional (`-').
;;
;; BACKEND PROPERTIES
;;
;; * revision-granularity
;;
;; Takes no arguments. Returns either 'file or 'repository.
;;
;; STATE-QUERYING FUNCTIONS
;;
;; * registered (file)
;;
;; Return non-nil if FILE is registered in this backend.
;;
;; * state (file)
;;
;; Return the current version control state of FILE. For a list of
;; possible values, see `vc-state'. This function should do a full and
;; reliable state computation; it is usually called immediately after
;; C-x v v. If you want to use a faster heuristic when visiting a
;; file, put that into `state-heuristic' below.
;;
;; - state-heuristic (file)
;;
;; If provided, this function is used to estimate the version control
;; state of FILE at visiting time. It should be considerably faster
;; than the implementation of `state'. For a list of possible values,
;; see the doc string of `vc-state'.
;;
;; - dir-state (dir)
;;
;; If provided, this function is used to find the version control state
;; of all files in DIR in a fast way. The function should not return
;; anything, but rather store the files' states into the corresponding
;; `vc-state' properties.
;;
;; * workfile-version (file)
;;
;; Return the current focus version of FILE. This is the version fetched
;; by the last checkout or upate, not necessarily the same thing as a the
;; head or tip version. Should return "0" for a file added but not yet
;; committed.
;;
;; - latest-on-branch-p (file)
;;
;; Return non-nil if the current focus version of FILE is the latest
;; or tip version on its branch. The default implementation always
;; returns t, which means that working with non-current versions is
;; not supported by default.
;;
;; * checkout-model (file)
;;
;; Indicate whether FILE needs to be "checked out" before it can be
;; edited. See `vc-checkout-model' for a list of possible values.
;;
;; - workfile-unchanged-p (file)
;;
;; Return non-nil if FILE is unchanged from its current focus
;; version. This function should do a brief comparison of FILE's
;; contents with those of the master version. If the backend does not
;; have such a brief-comparison feature, the default implementation of
;; this function can be used, which delegates to a full
;; vc-BACKEND-diff. (Note that vc-BACKEND-diff must not run
;; asynchronously in this case.)
;;
;; - mode-line-string (file)
;;
;; If provided, this function should return the VC-specific mode line
;; string for FILE. The default implementation deals well with all
;; states that `vc-state' can return.
;;
;; - dired-state-info (file)
;;
;; Translate the `vc-state' property of FILE into a string that can be
;; used in a vc-dired buffer. The default implementation deals well
;; with all states that `vc-state' can return.
;;
;; STATE-CHANGING FUNCTIONS
;;
;; * create-repo (backend)
;;
;; Create an empty repository in the current directory and initialize
;; it so VC mode can add files to it. For file-oriented systems, this
;; need do no more than create a subdirectory with the right name.
;;
;; * register (files &optional rev comment)
;;
;; Register FILES in this backend. Optionally, an initial revision REV
;; and an initial description of the file, COMMENT, may be specified,
;; but it is not guaranteed that the backend will do anything with this.
;; The implementation should pass the value of vc-register-switches
;; to the backend command. (Note: in older versions of VC, this
;; command took a single file argument and not a list.)
;;
;; - init-version (file)
;;
;; The initial version to use when registering FILE if one is not
;; specified by the user. If not provided, the variable
;; vc-default-init-version is used instead.
;;
;; - responsible-p (file)
;;
;; Return non-nil if this backend considers itself "responsible" for
;; FILE, which can also be a directory. This function is used to find
;; out what backend to use for registration of new files and for things
;; like change log generation. The default implementation always
;; returns nil.
;;
;; - could-register (file)
;;
;; Return non-nil if FILE could be registered under this backend. The
;; default implementation always returns t.
;;
;; - receive-file (file rev)
;;
;; Let this backend "receive" a file that is already registered under
;; another backend. The default implementation simply calls `register'
;; for FILE, but it can be overridden to do something more specific,
;; e.g. keep revision numbers consistent or choose editing modes for
;; FILE that resemble those of the other backend.
;;
;; - unregister (file)
;;
;; Unregister FILE from this backend. This is only needed if this
;; backend may be used as a "more local" backend for temporary editing.
;;
;; * checkin (files rev comment)
;;
;; Commit changes in FILES to this backend. If REV is non-nil, that
;; should become the new revision number (not all backends do
;; anything with it). COMMENT is used as a check-in comment. The
;; implementation should pass the value of vc-checkin-switches to
;; the backend command. (Note: in older versions of VC, this
;; command took a single file argument and not a list.)
;;
;; * find-version (file rev buffer)
;;
;; Fetch revision REV of file FILE and put it into BUFFER.
;; If REV is the empty string, fetch the head of the trunk.
;; The implementation should pass the value of vc-checkout-switches
;; to the backend command.
;;
;; * checkout (file &optional editable rev)
;;
;; Check out revision REV of FILE into the working area. If EDITABLE
;; is non-nil, FILE should be writable by the user and if locking is
;; used for FILE, a lock should also be set. If REV is non-nil, that
;; is the revision to check out (default is current focus version).
;; If REV is t, that means to check out the head of the current branch;
;; if it is the empty string, check out the head of the trunk.
;; The implementation should pass the value of vc-checkout-switches
;; to the backend command.
;;
;; * revert (file &optional contents-done)
;;
;; Revert FILE back to the current focus version. If optional
;; arg CONTENTS-DONE is non-nil, then the contents of FILE have
;; already been reverted from a version backup, and this function
;; only needs to update the status of FILE within the backend.
;;
;; - rollback (files)
;;
;; Remove the tip version of each of FILES from the repository. If
;; this function is not provided, trying to cancel a version is
;; caught as an error. (Most backends don't provide it.) (Also
;; note that older versions of this backend command were called
;; 'cancel-version' and took a single file arg, not a list of
;; files.)
;;
;; - merge (file rev1 rev2)
;;
;; Merge the changes between REV1 and REV2 into the current working file.
;;
;; - merge-news (file)
;;
;; Merge recent changes from the current branch into FILE.
;;
;; - steal-lock (file &optional version)
;;
;; Steal any lock on the current focus version of FILE, or on
;; VERSION if that is provided. This function is only needed if
;; locking is used for files under this backend, and if files can
;; indeed be locked by other users.
;;
;; HISTORY FUNCTIONS
;;
;; * print-log (files &optional buffer)
;;
;; Insert the revision log for FILES into BUFFER, or the *vc* buffer
;; if BUFFER is nil. (Note: older versions of this function expected
;; only a single file argument.)
;;
;; - show-log-entry (version)
;;
;; If provided, search the log entry for VERSION in the current buffer,
;; and make sure it is displayed in the buffer's window. The default
;; implementation of this function works for RCS-style logs.
;;
;; - wash-log (file)
;;
;; Remove all non-comment information from the output of print-log.
;;
;; - logentry-check ()
;;
;; If defined, this function is run to find out whether the user
;; entered a valid log entry for check-in. The log entry is in the
;; current buffer, and if it is not a valid one, the function should
;; throw an error.
;;
;; - comment-history (file)
;;
;; Return a string containing all log entries that were made for FILE.
;; This is used for transferring a file from one backend to another,
;; retaining comment information. The default implementation of this
;; function does this by calling print-log and then wash-log, and
;; returning the resulting buffer contents as a string.
;;
;; - update-changelog (files)
;;
;; Using recent log entries, create ChangeLog entries for FILES, or for
;; all files at or below the default-directory if FILES is nil. The
;; default implementation runs rcs2log, which handles RCS- and
;; CVS-style logs.
;;
;; * diff (files &optional rev1 rev2 buffer)
;;
;; Insert the diff for FILE into BUFFER, or the *vc-diff* buffer if
;; BUFFER is nil. If REV1 and REV2 are non-nil, report differences
;; from REV1 to REV2. If REV1 is nil, use the current focus
;; version (as found in the repository) as the older version; if
;; REV2 is nil, use the current focus contents as the newer
;; version. This function should pass the value of (vc-switches
;; BACKEND 'diff) to the backend command. It should return a status
;; of either 0 (no differences found), or 1 (either non-empty diff
;; or the diff is run asynchronously).
;;
;; - annotate-command (file buf &optional rev)
;;
;; If this function is provided, it should produce an annotated display
;; of FILE in BUF, relative to version REV. Annotation means each line
;; of FILE displayed is prefixed with version information associated with
;; its addition (deleted lines leave no history) and that the text of the
;; file is fontified according to age.
;;
;; - annotate-time ()
;;
;; Only required if `annotate-command' is defined for the backend.
;; Return the time of the next line of annotation at or after point,
;; as a floating point fractional number of days. The helper
;; function `vc-annotate-convert-time' may be useful for converting
;; multi-part times as returned by `current-time' and `encode-time'
;; to this format. Return nil if no more lines of annotation appear
;; in the buffer. You can safely assume that point is placed at the
;; beginning of each line, starting at `point-min'. The buffer that
;; point is placed in is the Annotate output, as defined by the
;; relevant backend. This function also affects how much of the line
;; is fontified; where it leaves point is where fontification begins.
;;
;; - annotate-current-time ()
;;
;; Only required if `annotate-command' is defined for the backend,
;; AND you'd like the current time considered to be anything besides
;; (vs-annotate-convert-time (current-time)) -- i.e. the current
;; time with hours, minutes, and seconds included. Probably safe to
;; ignore. Return the current-time, in units of fractional days.
;;
;; - annotate-extract-revision-at-line ()
;;
;; Only required if `annotate-command' is defined for the backend.
;; Invoked from a buffer in vc-annotate-mode, return the revision
;; corresponding to the current line, or nil if there is no revision
;; corresponding to the current line.
;;
;; SNAPSHOT SYSTEM
;;
;; - create-snapshot (dir name branchp)
;;
;; Take a snapshot of the current state of files under DIR and name it
;; NAME. This should make sure that files are up-to-date before
;; proceeding with the action. DIR can also be a file and if BRANCHP
;; is specified, NAME should be created as a branch and DIR should be
;; checked out under this new branch. The default implementation does
;; not support branches but does a sanity check, a tree traversal and
;; for each file calls `assign-name'.
;;
;; - assign-name (file name)
;;
;; Give name NAME to the current version of FILE, assuming it is
;; up-to-date. Only used by the default version of `create-snapshot'.
;;
;; - retrieve-snapshot (dir name update)
;;
;; Retrieve a named snapshot of all registered files at or below DIR.
;; If UPDATE is non-nil, then update buffers of any files in the
;; snapshot that are currently visited. The default implementation
;; does a sanity check whether there aren't any uncommitted changes at
;; or below DIR, and then performs a tree walk, using the `checkout'
;; function to retrieve the corresponding versions.
;;
;; MISCELLANEOUS
;;
;; - make-version-backups-p (file)
;;
;; Return non-nil if unmodified repository versions of FILE should be
;; backed up locally. If this is done, VC can perform `diff' and
;; `revert' operations itself, without calling the backend system. The
;; default implementation always returns nil.
;;
;; - repository-hostname (dirname)
;;
;; Return the hostname that the backend will have to contact
;; in order to operate on a file in DIRNAME. If the return value
;; is nil, it means that the repository is local.
;; This function is used in `vc-stay-local-p' which backends can use
;; for their convenience.
;;
;; - previous-version (file rev)
;;
;; Return the version number that precedes REV for FILE, or nil if no such
;; version exists.
;;
;; - next-version (file rev)
;;
;; Return the version number that follows REV for FILE, or nil if no such
;; version exists.
;;
;; - check-headers ()
;;
;; Return non-nil if the current buffer contains any version headers.
;;
;; - clear-headers ()
;;
;; In the current buffer, reset all version headers to their unexpanded
;; form. This function should be provided if the state-querying code
;; for this backend uses the version headers to determine the state of
;; a file. This function will then be called whenever VC changes the
;; version control state in such a way that the headers would give
;; wrong information.
;;
;; - delete-file (file)
;;
;; Delete FILE and mark it as deleted in the repository. If this
;; function is not provided, the command `vc-delete-file' will
;; signal an error.
;;
;; - rename-file (old new)
;;
;; Rename file OLD to NEW, both in the working area and in the
;; repository. If this function is not provided, the renaming
;; will be done by (vc-delete-file old) and (vc-register new).
;;
;; - find-file-hook ()
;;
;; Operation called in current buffer when opening a file. This can
;; be used by the backend to setup some local variables it might need.
;
;; - find-file-not-found-hook ()
;;
;; Operation called in current buffer when opening a non-existing file.
;; By default, this asks the user if she wants to check out the file.
;;; Code:
(require 'vc-hooks)
(require 'ring)
(eval-when-compile
(require 'cl)
(require 'compile)
(require 'dired) ; for dired-map-over-marks macro
(require 'dired-aux)) ; for dired-kill-{line,tree}
(if (not (assoc 'vc-parent-buffer minor-mode-alist))
(setq minor-mode-alist
(cons '(vc-parent-buffer vc-parent-buffer-name)
minor-mode-alist)))
;; General customization
(defgroup vc nil
"Version-control system in Emacs."
:group 'tools)
(defcustom vc-suppress-confirm nil
"If non-nil, treat user as expert; suppress yes-no prompts on some things."
:type 'boolean
:group 'vc)
(defcustom vc-delete-logbuf-window t
"If non-nil, delete the *VC-log* buffer and window after each logical action.
If nil, bury that buffer instead.
This is most useful if you have multiple windows on a frame and would like to
preserve the setting."
:type 'boolean
:group 'vc)
(defcustom vc-initial-comment nil
"If non-nil, prompt for initial comment when a file is registered."
:type 'boolean
:group 'vc)
(defcustom vc-default-init-version "1.1"
"A string used as the default version number when a new file is registered.
This can be overridden by giving a prefix argument to \\[vc-register]. This
can also be overridden by a particular VC backend."
:type 'string
:group 'vc
:version "20.3")
(defcustom vc-command-messages nil
"If non-nil, display run messages from back-end commands."
:type 'boolean
:group 'vc)
(defcustom vc-checkin-switches nil
"A string or list of strings specifying extra switches for checkin.
These are passed to the checkin program by \\[vc-checkin]."
:type '(choice (const :tag "None" nil)
(string :tag "Argument String")
(repeat :tag "Argument List"
:value ("")
string))
:group 'vc)
(defcustom vc-checkout-switches nil
"A string or list of strings specifying extra switches for checkout.
These are passed to the checkout program by \\[vc-checkout]."
:type '(choice (const :tag "None" nil)
(string :tag "Argument String")
(repeat :tag "Argument List"
:value ("")
string))
:group 'vc)
(defcustom vc-register-switches nil
"A string or list of strings; extra switches for registering a file.
These are passed to the checkin program by \\[vc-register]."
:type '(choice (const :tag "None" nil)
(string :tag "Argument String")
(repeat :tag "Argument List"
:value ("")
string))
:group 'vc)
(defcustom vc-dired-listing-switches "-al"
"Switches passed to `ls' for vc-dired. MUST contain the `l' option."
:type 'string
:group 'vc
:version "21.1")
(defcustom vc-dired-recurse t
"If non-nil, show directory trees recursively in VC Dired."
:type 'boolean
:group 'vc
:version "20.3")
(defcustom vc-dired-terse-display t
"If non-nil, show only locked files in VC Dired."
:type 'boolean
:group 'vc
:version "20.3")
(defcustom vc-directory-exclusion-list '("SCCS" "RCS" "CVS" "MCVS" ".svn" "{arch}")
"List of directory names to be ignored when walking directory trees."
:type '(repeat string)
:group 'vc)
(defcustom vc-diff-switches nil
"A string or list of strings specifying switches for diff under VC.
When running diff under a given BACKEND, VC concatenates the values of
`diff-switches', `vc-diff-switches', and `vc-BACKEND-diff-switches' to
get the switches for that command. Thus, `vc-diff-switches' should
contain switches that are specific to version control, but not
specific to any particular backend."
:type '(choice (const :tag "None" nil)
(string :tag "Argument String")
(repeat :tag "Argument List"
:value ("")
string))
:group 'vc
:version "21.1")
(defcustom vc-diff-knows-L nil
"*Indicates whether diff understands the -L option.
The value is either `yes', `no', or nil. If it is nil, VC tries
to use -L and sets this variable to remember whether it worked."
:type '(choice (const :tag "Work out" nil) (const yes) (const no))
:group 'vc)
(defcustom vc-allow-async-revert nil
"Specifies whether the diff during \\[vc-revert] may be asynchronous.
Enabling this option means that you can confirm a revert operation even
if the local changes in the file have not been found and displayed yet."
:type '(choice (const :tag "No" nil)
(const :tag "Yes" t))
:group 'vc
:version "22.1")
;;;###autoload
(defcustom vc-checkout-hook nil
"Normal hook (list of functions) run after checking out a file.
See `run-hooks'."
:type 'hook
:group 'vc
:version "21.1")
(defcustom vc-annotate-display-mode 'fullscale
"Which mode to color the output of \\[vc-annotate] with by default."
:type '(choice (const :tag "By Color Map Range" nil)
(const :tag "Scale to Oldest" scale)
(const :tag "Scale Oldest->Newest" fullscale)
(number :tag "Specify Fractional Number of Days"
:value "20.5"))
:group 'vc)
;;;###autoload
(defcustom vc-checkin-hook nil
"Normal hook (list of functions) run after commit or file checkin.
See also `log-edit-done-hook'."
:type 'hook
:options '(log-edit-comment-to-change-log)
:group 'vc)
;;;###autoload
(defcustom vc-before-checkin-hook nil
"Normal hook (list of functions) run before a commit or a file checkin.
See `run-hooks'."
:type 'hook
:group 'vc)
(defcustom vc-logentry-check-hook nil
"Normal hook run by `vc-backend-logentry-check'.
Use this to impose your own rules on the entry in addition to any the
version control backend imposes itself."
:type 'hook
:group 'vc)
;; Annotate customization
(defcustom vc-annotate-color-map
(if (and (tty-display-color-p) (<= (display-color-cells) 8))
;; A custom sorted TTY colormap
(let* ((colors
(sort
(delq nil
(mapcar (lambda (x)
(if (not (or
(string-equal (car x) "white")
(string-equal (car x) "black") ))
(car x)))
(tty-color-alist)))
(lambda (a b)
(cond
((or (string-equal a "red") (string-equal b "blue")) t)
((or (string-equal b "red") (string-equal a "blue")) nil)
((string-equal a "yellow") t)
((string-equal b "yellow") nil)
((string-equal a "cyan") t)
((string-equal b "cyan") nil)
((string-equal a "green") t)
((string-equal b "green") nil)
((string-equal a "magenta") t)
((string-equal b "magenta") nil)
(t (string< a b))))))
(date 20.)
(delta (/ (- 360. date) (1- (length colors)))))
(mapcar (lambda (x)
(prog1
(cons date x)
(setq date (+ date delta)))) colors))
;; Normal colormap: hue stepped from 0-240deg, value=1., saturation=0.75
'(( 20. . "#FF3F3F")
( 40. . "#FF6C3F")
( 60. . "#FF993F")
( 80. . "#FFC63F")
(100. . "#FFF33F")
(120. . "#DDFF3F")
(140. . "#B0FF3F")
(160. . "#83FF3F")
(180. . "#56FF3F")
(200. . "#3FFF56")
(220. . "#3FFF83")
(240. . "#3FFFB0")
(260. . "#3FFFDD")
(280. . "#3FF3FF")
(300. . "#3FC6FF")
(320. . "#3F99FF")
(340. . "#3F6CFF")
(360. . "#3F3FFF")))
"Association list of age versus color, for \\[vc-annotate].
Ages are given in units of fractional days. Default is eighteen
steps using a twenty day increment, from red to blue. For TTY
displays with 8 or fewer colors, the default is red to blue with
all other colors between (excluding black and white)."
:type 'alist
:group 'vc)
(defcustom vc-annotate-very-old-color "#3F3FFF"
"Color for lines older than the current color range in \\[vc-annotate]]."
:type 'string
:group 'vc)
(defcustom vc-annotate-background "black"
"Background color for \\[vc-annotate].
Default color is used if nil."
:type 'string
:group 'vc)
(defcustom vc-annotate-menu-elements '(2 0.5 0.1 0.01)
"Menu elements for the mode-specific menu of VC-Annotate mode.
List of factors, used to expand/compress the time scale. See `vc-annotate'."
:type '(repeat number)
:group 'vc)
(defvar vc-annotate-mode-map
(let ((m (make-sparse-keymap)))
(define-key m "A" 'vc-annotate-revision-previous-to-line)
(define-key m "D" 'vc-annotate-show-diff-revision-at-line)
(define-key m "J" 'vc-annotate-revision-at-line)
(define-key m "L" 'vc-annotate-show-log-revision-at-line)
(define-key m "N" 'vc-annotate-next-version)
(define-key m "P" 'vc-annotate-prev-version)
(define-key m "W" 'vc-annotate-workfile-version)
m)
"Local keymap used for VC-Annotate mode.")
;; Header-insertion hair
(defcustom vc-static-header-alist
'(("\\.c\\'" .
"\n#ifndef lint\nstatic char vcid[] = \"\%s\";\n#endif /* lint */\n"))
"*Associate static header string templates with file types.
A \%s in the template is replaced with the first string associated with
the file's version control type in `vc-header-alist'."
:type '(repeat (cons :format "%v"
(regexp :tag "File Type")
(string :tag "Header String")))
:group 'vc)
(defcustom vc-comment-alist
'((nroff-mode ".\\\"" ""))
"*Special comment delimiters for generating VC headers.
Add an entry in this list if you need to override the normal `comment-start'
and `comment-end' variables. This will only be necessary if the mode language
is sensitive to blank lines."
:type '(repeat (list :format "%v"
(symbol :tag "Mode")
(string :tag "Comment Start")
(string :tag "Comment End")))
:group 'vc)
(defcustom vc-checkout-carefully (= (user-uid) 0)
"*Non-nil means be extra-careful in checkout.
Verify that the file really is not locked
and that its contents match what the master file says."
:type 'boolean
:group 'vc)
(make-obsolete-variable 'vc-checkout-carefully
"the corresponding checks are always done now."
"21.1")
\f
;; Variables the user doesn't need to know about.
(defvar vc-log-operation nil)
(defvar vc-log-after-operation-hook nil)
;; In a log entry buffer, this is a local variable
;; that points to the buffer for which it was made
;; (either a file, or a VC dired buffer).
(defvar vc-parent-buffer nil)
(put 'vc-parent-buffer 'permanent-local t)
(defvar vc-parent-buffer-name nil)
(put 'vc-parent-buffer-name 'permanent-local t)
(defvar vc-disable-async-diff nil
"VC sets this to t locally to disable some async diff operations.
Backends that offer asynchronous diffs should respect this variable
in their implementation of vc-BACKEND-diff.")
(defvar vc-log-fileset)
(defvar vc-log-version)
(defvar vc-dired-mode nil)
(make-variable-buffer-local 'vc-dired-mode)
;; File property caching
(defun vc-clear-context ()
"Clear all cached file properties."
(interactive)
(fillarray vc-file-prop-obarray 0))
(defmacro with-vc-properties (files form settings)
"Execute FORM, then maybe set per-file properties for FILES.
SETTINGS is an association list of property/value pairs. After
executing FORM, set those properties from SETTINGS that have not yet
been updated to their corresponding values."
(declare (debug t))
`(let ((vc-touched-properties (list t)))
,form
(dolist (file ,files)
(mapc (lambda (setting)
(let ((property (car setting)))
(unless (memq property vc-touched-properties)
(put (intern file vc-file-prop-obarray)
property (cdr setting)))))
,settings))))
;; Two macros for elisp programming (not used in VC-mode itself)
;;;###autoload
(defmacro with-vc-file (file comment &rest body)
"Check out a writable copy of FILE if necessary, then execute BODY.
Check in FILE with COMMENT (a string) after BODY has been executed.
FILE is passed through `expand-file-name'; BODY executed within
`save-excursion'. If FILE is not under version control, or locked by
somebody else, signal error."
(declare (debug t) (indent 2))
(let ((filevar (make-symbol "file")))
`(let ((,filevar (expand-file-name ,file)))
(or (vc-backend ,filevar)
(error "File not under version control: `%s'" file))
(unless (vc-editable-p ,filevar)
(let ((state (vc-state ,filevar)))
(if (stringp state)
(error "`%s' is locking `%s'" state ,filevar)
(vc-checkout ,filevar t))))
(save-excursion
,@body)
(vc-checkin (list ,filevar) nil ,comment))))
;;;###autoload
(defmacro edit-vc-file (file comment &rest body)
"Edit FILE under version control, executing body.
Checkin with COMMENT after executing BODY.
This macro uses `with-vc-file', passing args to it.
However, before executing BODY, find FILE, and after BODY, save buffer."
(declare (debug t) (indent 2))
(let ((filevar (make-symbol "file")))
`(let ((,filevar (expand-file-name ,file)))
(with-vc-file
,filevar ,comment
(set-buffer (find-file-noselect ,filevar))
,@body
(save-buffer)))))
;; Common command execution logic to be used by backends
(defun vc-process-filter (p s)
"An alternative output filter for async process P.
One difference with the default filter is that this inserts S after markers.
Another is that undo information is not kept."
(with-current-buffer (process-buffer p)
(save-excursion
(let ((buffer-undo-list t)
(inhibit-read-only t))
(goto-char (process-mark p))
(insert s)
(set-marker (process-mark p) (point))))))
(defun vc-setup-buffer (&optional buf)
"Prepare BUF for executing a VC command and make it current.
BUF defaults to \"*vc*\", can be a string and will be created if necessary."
(unless buf (setq buf "*vc*"))
(let ((camefrom (current-buffer))
(olddir default-directory))
(set-buffer (get-buffer-create buf))
(kill-all-local-variables)
(set (make-local-variable 'vc-parent-buffer) camefrom)
(set (make-local-variable 'vc-parent-buffer-name)
(concat " from " (buffer-name camefrom)))
(setq default-directory olddir)
(let ((buffer-undo-list t)
(inhibit-read-only t))
(erase-buffer))))
(defun vc-exec-after (code)
"Eval CODE when the current buffer's process is done.
If the current buffer has no process, just evaluate CODE.
Else, add CODE to the process' sentinel."
(let ((proc (get-buffer-process (current-buffer))))
(cond
;; If there's no background process, just execute the code.
;; We used to explicitly call delete-process on exited processes,
;; but this led to timing problems causing process output to be
;; lost. Terminated processes get deleted automatically
;; anyway. -- cyd
((or (null proc) (eq (process-status proc) 'exit))
(eval code))
;; If a process is running, add CODE to the sentinel
((eq (process-status proc) 'run)
(let ((sentinel (process-sentinel proc)))
(set-process-sentinel proc
`(lambda (p s)
(with-current-buffer ',(current-buffer)
(goto-char (process-mark p))
,@(append (cdr (cdr (cdr ;strip off `with-current-buffer buf
; (goto-char...)'
(car (cdr (cdr ;strip off `lambda (p s)'
sentinel))))))
(list `(vc-exec-after ',code))))))))
(t (error "Unexpected process state"))))
nil)
(defvar vc-post-command-functions nil
"Hook run at the end of `vc-do-command'.
Each function is called inside the buffer in which the command was run
and is passed 3 arguments: the COMMAND, the FILES and the FLAGS.")
(defvar w32-quote-process-args)
(defun vc-delistify (filelist)
"Smash a FILELIST into a file list string suitable for info messages."
(cond ((not filelist) ".")
((= (length filelist) 1) (car filelist))
(t (concat (car filelist) " " (vc-delistify (cdr filelist))))))
;;;###autoload
(defun vc-do-command (buffer okstatus command file-or-list &rest flags)
"Execute a VC command, notifying user and checking for errors.
Output from COMMAND goes to BUFFER, or *vc* if BUFFER is nil or the
current buffer if BUFFER is t. If the destination buffer is not
already current, set it up properly and erase it. The command is
considered successful if its exit status does not exceed OKSTATUS (if
OKSTATUS is nil, that means to ignore error status, if it is `async', that
means not to wait for termination of the subprocess; if it is t it means to
ignore all execution errors). FILE-OR-LIST is the name of a working file;
it may be a list of files or be nil (to execute commands that don't expect
a file name or set of files). If an optional list of FLAGS is present,
that is inserted into the command line before the filename."
;; FIXME: file-relative-name can return a bogus result because
;; it doesn't look at the actual file-system to see if symlinks
;; come into play.
(let* ((files
(mapcar 'file-relative-name
(cond ((not file-or-list) '())
((listp file-or-list) (mapcar 'expand-file-name file-or-list))
(t (list (expand-file-name file-or-list))))))
(full-command
(concat command " "
(vc-delistify (mapcar (lambda (s) (if (> (length s) 20) (concat (substring s 0 2) "<stuff>") s)) flags))
" " (vc-delistify files))))
(save-current-buffer
(unless (or (eq buffer t)
(and (stringp buffer)
(string= (buffer-name) buffer))
(eq buffer (current-buffer)))
(vc-setup-buffer buffer))
(let ((squeezed (remq nil flags))
(inhibit-read-only t)
(status 0))
(when files
(setq squeezed (nconc squeezed files)))
(let ((exec-path (append vc-path exec-path))
;; Add vc-path to PATH for the execution of this command.
(process-environment
(cons (concat "PATH=" (getenv "PATH")
path-separator
(mapconcat 'identity vc-path path-separator))
process-environment))
(w32-quote-process-args t))
(if (and (eq okstatus 'async) (file-remote-p default-directory))
;; start-process does not support remote execution
(setq okstatus nil))
(if (eq okstatus 'async)
;; Run asynchronously
(let ((proc
(let ((process-connection-type nil))
(apply 'start-process command (current-buffer) command
squeezed))))
(if vc-command-messages
(message "Running %s in background..." full-command))
;;(set-process-sentinel proc (lambda (p msg) (delete-process p)))
(set-process-filter proc 'vc-process-filter)
(vc-exec-after
`(if vc-command-messages
(message "Running %s in background... done" ',full-command))))
;; Run synchrously
(if vc-command-messages
(message "Running %s in foreground..." full-command))
(let ((buffer-undo-list t))
(setq status (apply 'process-file command nil t nil squeezed)))
(when (and (not (eq t okstatus))
(or (not (integerp status))
(and okstatus (< okstatus status))))
(pop-to-buffer (current-buffer))
(goto-char (point-min))
(shrink-window-if-larger-than-buffer)
(error "Running %s...FAILED (%s)" full-command
(if (integerp status) (format "status %d" status) status))))
;; We're done
(if vc-command-messages
(message "Running %s...OK = %d" full-command status)))
(vc-exec-after
`(run-hook-with-args 'vc-post-command-functions ',command ',file-or-list ',flags))
status))))
(defun vc-position-context (posn)
"Save a bit of the text around POSN in the current buffer.
Used to help us find the corresponding position again later
if markers are destroyed or corrupted."
;; A lot of this was shamelessly lifted from Sebastian Kremer's
;; rcs.el mode.
(list posn
(buffer-size)
(buffer-substring posn
(min (point-max) (+ posn 100)))))
(defun vc-find-position-by-context (context)
"Return the position of CONTEXT in the current buffer.
If CONTEXT cannot be found, return nil."
(let ((context-string (nth 2 context)))
(if (equal "" context-string)
(point-max)
(save-excursion
(let ((diff (- (nth 1 context) (buffer-size))))
(if (< diff 0) (setq diff (- diff)))
(goto-char (nth 0 context))
(if (or (search-forward context-string nil t)
;; Can't use search-backward since the match may continue
;; after point.
(progn (goto-char (- (point) diff (length context-string)))
;; goto-char doesn't signal an error at
;; beginning of buffer like backward-char would
(search-forward context-string nil t)))
;; to beginning of OSTRING
(- (point) (length context-string))))))))
(defun vc-context-matches-p (posn context)
"Return t if POSN matches CONTEXT, nil otherwise."
(let* ((context-string (nth 2 context))
(len (length context-string))
(end (+ posn len)))
(if (> end (1+ (buffer-size)))
nil
(string= context-string (buffer-substring posn end)))))
(defun vc-buffer-context ()
"Return a list (POINT-CONTEXT MARK-CONTEXT REPARSE).
Used by `vc-restore-buffer-context' to later restore the context."
(let ((point-context (vc-position-context (point)))
;; Use mark-marker to avoid confusion in transient-mark-mode.
(mark-context (if (eq (marker-buffer (mark-marker)) (current-buffer))
(vc-position-context (mark-marker))))
;; Make the right thing happen in transient-mark-mode.
(mark-active nil)
(reparse nil))
(list point-context mark-context reparse)))
(defun vc-restore-buffer-context (context)
"Restore point/mark, and reparse any affected compilation buffers.
CONTEXT is that which `vc-buffer-context' returns."
(let ((point-context (nth 0 context))
(mark-context (nth 1 context))
(reparse (nth 2 context)))
;; The new compilation code does not use compilation-error-list any
;; more, so the code below is now ineffective and might as well
;; be disabled. -- Stef
;; ;; Reparse affected compilation buffers.
;; (while reparse
;; (if (car reparse)
;; (with-current-buffer (car reparse)
;; (let ((compilation-last-buffer (current-buffer)) ;select buffer
;; ;; Record the position in the compilation buffer of
;; ;; the last error next-error went to.
;; (error-pos (marker-position
;; (car (car-safe compilation-error-list)))))
;; ;; Reparse the error messages as far as they were parsed before.
;; (compile-reinitialize-errors '(4) compilation-parsing-end)
;; ;; Move the pointer up to find the error we were at before
;; ;; reparsing. Now next-error should properly go to the next one.
;; (while (and compilation-error-list
;; (/= error-pos (car (car compilation-error-list))))
;; (setq compilation-error-list (cdr compilation-error-list))))))
;; (setq reparse (cdr reparse)))
;; if necessary, restore point and mark
(if (not (vc-context-matches-p (point) point-context))
(let ((new-point (vc-find-position-by-context point-context)))
(if new-point (goto-char new-point))))
(and mark-active
mark-context
(not (vc-context-matches-p (mark) mark-context))
(let ((new-mark (vc-find-position-by-context mark-context)))
(if new-mark (set-mark new-mark))))))
;;; Code for deducing what fileset and backend to assume
(defun vc-responsible-backend (file &optional register)
"Return the name of a backend system that is responsible for FILE.
The optional argument REGISTER means that a backend suitable for
registration should be found.
If REGISTER is nil, then if FILE is already registered, return the
backend of FILE. If FILE is not registered, or a directory, then the
first backend in `vc-handled-backends' that declares itself
responsible for FILE is returned. If no backend declares itself
responsible, return the first backend.
If REGISTER is non-nil, return the first responsible backend under
which FILE is not yet registered. If there is no such backend, return
the first backend under which FILE is not yet registered, but could
be registered."
(if (not vc-handled-backends)
(error "No handled backends"))
(or (and (not (file-directory-p file)) (not register) (vc-backend file))
(catch 'found
;; First try: find a responsible backend. If this is for registration,
;; it must be a backend under which FILE is not yet registered.
(dolist (backend vc-handled-backends)
(and (or (not register)
(not (vc-call-backend backend 'registered file)))
(vc-call-backend backend 'responsible-p file)
(throw 'found backend)))
;; no responsible backend
(if (not register)
;; if this is not for registration, the first backend must do
(car vc-handled-backends)
;; for registration, we need to find a new backend that
;; could register FILE
(dolist (backend vc-handled-backends)
(and (not (vc-call-backend backend 'registered file))
(vc-call-backend backend 'could-register file)
(throw 'found backend)))
(error "No backend that could register")))))
(defun vc-expand-dirs (file-or-dir-list)
"Expands directories in a file list specification.
Only files already under version control are noticed."
(let ((flattened '()))
(dolist (node file-or-dir-list)
(vc-file-tree-walk node (lambda (f) (if (vc-backend f) (setq flattened (cons f flattened))))))
(nreverse flattened)))
(defun vc-deduce-fileset (&optional allow-directory-wildcard)
"Deduce a set of files and a backend to apply an operation to.
If we're in VC-dired-mode, the fileset is the list of marked
files. Otherwise, if we're looking at a buffer visiting a
version-controlled file. the fileset is a singleton containing
the relative filename, throw an error.
If neither of these things is true, but allow-directory-wildcard is on,
select all files under version control at and below the current
directory.
Otherwise, throw an error.
"
(cond (vc-dired-mode
(let ((regexp (dired-marker-regexp))
(marked '()))
(save-excursion
(goto-char (point-min))
(while (re-search-forward regexp nil t)
(if (setq filename (dired-get-filename nil t))
(setq marked (append marked (list filename))))))
(unless marked
(error "No files have been selected."))
;; All members of the fileset must have the same backend
(let ((firstbackend (vc-backend (car marked))))
(mapc (lambda (f) (unless (eq (vc-backend f) firstbackend)
(error "All members of a fileset must be under the same version-control system.")))
(cdr marked)))
marked))
((vc-backend buffer-file-name)
(list buffer-file-name))
((and vc-parent-buffer (buffer-file-name vc-parent-buffer))
(progn
(if vc-dired-mode
(pop-to-buffer vc-parent-buffer)
(set-buffer vc-parent-buffer))
(vc-deduce-fileset)))
;; This is guarded by an enabling arg so users won't potentially
;; shoot themselves in the foot by modifying a fileset they can't
;; verify by eyeball. Allow it for nondestructive commands like
;; making diffs, or possibly for destructive ones that have
;; confirmation prompts.
(allow-directory-wildcard
(progn
(setq marked (list default-directory))
(message "All version-controlled files below %s selected."
default-directory)
(list default-directory)))
(t (error "No fileset is available here."))))
(defun vc-ensure-vc-buffer ()
"Make sure that the current buffer visits a version-controlled file."
(if vc-dired-mode
(set-buffer (find-file-noselect (dired-get-filename)))
(while vc-parent-buffer
(set-buffer vc-parent-buffer))
(if (not buffer-file-name)
(error "Buffer %s is not associated with a file" (buffer-name))
(if (not (vc-backend buffer-file-name))
(error "File %s is not under version control" buffer-file-name)))))
;;; Support for the C-x v v command. This is where all the single-file-oriented
;;; code from before the fileset rewrite lives.
(defsubst vc-editable-p (file)
"Return non-nil if FILE can be edited."
(or (eq (vc-checkout-model file) 'implicit)
(memq (vc-state file) '(edited needs-merge))))
(defun vc-revert-buffer-internal (&optional arg no-confirm)
"Revert buffer, keeping point and mark where user expects them.
Try to be clever in the face of changes due to expanded version control
key words. This is important for typeahead to work as expected.
ARG and NO-CONFIRM are passed on to `revert-buffer'."
(interactive "P")
(widen)
(let ((context (vc-buffer-context)))
;; Use save-excursion here, because it may be able to restore point
;; and mark properly even in cases where vc-restore-buffer-context
;; would fail. However, save-excursion might also get it wrong --
;; in this case, vc-restore-buffer-context gives it a second try.
(save-excursion
;; t means don't call normal-mode;
;; that's to preserve various minor modes.
(revert-buffer arg no-confirm t))
(vc-restore-buffer-context context)))
(defun vc-buffer-sync (&optional not-urgent)
"Make sure the current buffer and its working file are in sync.
NOT-URGENT means it is ok to continue if the user says not to save."
(if (buffer-modified-p)
(if (or vc-suppress-confirm
(y-or-n-p (format "Buffer %s modified; save it? " (buffer-name))))
(save-buffer)
(unless not-urgent
(error "Aborted")))))
;;;###autoload
(defun vc-next-action (verbose)
"Do the next logical version control operation on the current fileset.
This requires that all files in the fileset be in the same state.
For locking systems:
If every file is not already registered, this registers each for version
control.
If every file is registered and not locked by anyone, this checks out
a writable and locked file of each ready for editing.
If every file is checked out and locked by the calling user, this
first checks to see if each file has changed since checkout. If not,
it performs a revert on that file.
If every file has been changed, this pops up a buffer for entry
of a log message; when the message has been entered, it checks in the
resulting changes along with the log message as change commentary. If
the variable `vc-keep-workfiles' is non-nil (which is its default), a
read-only copy of each changed file is left in place afterwards.
If the affected file is registered and locked by someone else, you are
given the option to steal the lock(s).
For merging systems:
If every file is not already registered, this registers each one for version
control. This does an add, but not a commit.
If every file is added but not committed, each one is committed.
If every working file is changed, but the corresponding repository file is
unchanged, this pops up a buffer for entry of a log message; when the
message has been entered, it checks in the resulting changes along
with the logmessage as change commentary. A writable file is retained.
If the repository file is changed, you are asked if you want to
merge in the changes into your working copies."
(interactive "P")
(let* ((files (vc-deduce-fileset))
(backend (vc-backend (car files)))
(state (vc-state (car files)))
(model (vc-checkout-model (car files)))
version)
;; Verify that the fileset is homogenous
(dolist (file (cdr files))
(if (not (eq (vc-state file) state))
(error "Fileset is in a mixed-up state"))
(if (not (eq (vc-checkout-model file) model))
(error "Fileset has mixed checkout models")))
;; Check for buffers in the fileset not matching the on-disk contents.
(dolist (file files)
(let ((visited (get-file-buffer file)))
(when visited
(if vc-dired-mode
(switch-to-buffer-other-window visited)
(set-buffer visited))
;; Check relation of buffer and file, and make sure
;; user knows what he's doing. First, finding the file
;; will check whether the file on disk is newer.
;; Ignore buffer-read-only during this test, and
;; preserve find-file-literally.
(let ((buffer-read-only (not (file-writable-p file))))
(find-file-noselect file nil find-file-literally))
(if (not (verify-visited-file-modtime (current-buffer)))
(if (yes-or-no-p (format "Replace %s on disk with buffer contents? " file))
(write-file buffer-file-name)
(error "Aborted"))
;; Now, check if we have unsaved changes.
(vc-buffer-sync t)
(if (buffer-modified-p)
(or (y-or-n-p (message "Use %s on disk, keeping modified buffer? " file))
(error "Aborted")))))))
;; Do the right thing
(cond
;; Files aren't registered
((not state)
(mapc 'vc-register files))
;; Files are up-to-date, or need a merge and user specified a version
((or (eq state 'up-to-date) (and verbose (eq state 'needs-patch)))
(cond
(verbose
;; go to a different version
(setq version (read-string "Branch, version, or backend to move to: "))
(let ((vsym (intern-soft (upcase version))))
(if (member vsym vc-handled-backends)
(mapc (lambda (file) vc-transfer-file file vsym) files)
(mapc (lambda (file)
(vc-checkout file (eq model 'implicit) version))))))
((not (eq model 'implicit))
;; check the files out
(mapc (lambda (file) (vc-checkout file t)) files))
(t
;; do nothing
(message "Fileset is up-to-date"))))
;; Files have local changes
((eq state 'edited)
(let ((ready-for-commit files))
;; If files are edited but read-only, give user a chance to correct
(dolist (file files)
(if (not (file-writable-p file))
(progn
;; Make the file+buffer read-write.
(unless (y-or-no-p (format "%s is edited but read-only; make it writable and continue?" file))
(error "Aborted"))
(set-file-modes file (logior (file-modes file) 128))
(let ((visited (get-file-buffer file)))
(if visited
(save-excursion
(set-buffer visited)
(toggle-read-only -1)))))))
;; Allow user to revert files with no changes
(save-excursion
(let ((revertlist '()))
(dolist (file files)
(let ((visited (get-file-buffer file)))
;; For files with locking, if the file does not contain
;; any changes, just let go of the lock, i.e. revert.
(if (and (not (eq model 'implicit))
(vc-workfile-unchanged-p file)
;; If buffer is modified, that means the user just
;; said no to saving it; in that case, don't revert,
;; because the user might intend to save after
;; finishing the log entry and committing.
(not (and visited (buffer-modified-p))))
(progn
(vc-revert-file file)
(delete file ready-for-commit)))))))
;; Remaining files need to be committed
(if (not ready-for-commit)
(message "No files remain to be committed")
(if (not verbose)
(vc-checkin ready-for-commit)
(progn
(setq version (read-string "New version or backend: "))
(let ((vsym (intern (upcase version))))
(if (member vsym vc-handled-backends)
(vc-transfer-file file vsym)
(vc-checkin ready-for-commit version))))))))
;; locked by somebody else
((stringp state)
(let ((version
(if verbose
(read-string "Version to steal: ")
(vc-workfile-version file))))
(mapc (lambda (file) (vc-steal-lock file version) state) files)))
;; needs-patch
((eq state 'needs-patch)
(dolist (file files)
(if (yes-or-no-p (format
"%s is not up-to-date. Get latest version? "
(file-name-nondirectory file)))
(vc-checkout file (eq model 'implicit) t)
(if (and (not (eq model 'implicit))
(yes-or-no-p "Lock this version? "))
(vc-checkout file t)))))
;; needs-merge
((eq state 'needs-merge)
(dolist (file files)
(if (yes-or-no-p (format
"%s is not up-to-date. Merge in changes now? "
(file-name-nondirectory file)))
(vc-maybe-resolve-conflicts file (vc-call merge-news file)))))
;; unlocked-changes
((eq state 'unlocked-changes)
(dolist (file files)
(if (not (equal buffer-file-name file))
(find-file-other-window file))
(if (save-window-excursion
(vc-diff-internal
(vc-backend file) nil (list file)
(vc-workfile-version file) nil)
(goto-char (point-min))
(let ((inhibit-read-only t))
(insert
(format "Changes to %s since last lock:\n\n" file)))
(not (beep))
(yes-or-no-p (concat "File has unlocked changes. "
"Claim lock retaining changes? ")))
(progn (vc-call steal-lock file)
(clear-visited-file-modtime)
;; Must clear any headers here because they wouldn't
;; show that the file is locked now.
(vc-clear-headers file)
(write-file buffer-file-name)
(vc-mode-line file))
(if (not (yes-or-no-p
"Revert to checked-in version, instead? "))
(error "Checkout aborted")
(vc-revert-buffer-internal t t)
(vc-checkout file t))))))))
(defvar vc-dired-window-configuration)
(defun vc-create-repo (backend)
"Create an empty repository in the current directory."
(interactive
(list
(intern
(upcase
(completing-read
"Create repository for: "
(mapcar (lambda (b) (list (downcase (symbol-name b)))) vc-handled-backends)
nil t)))))
(vc-call-backend backend 'create-repo))
;;;###autoload
(defun vc-register (&optional set-version comment)
"Register the current file into a version control system.
With prefix argument SET-VERSION, allow user to specify initial version
level. If COMMENT is present, use that as an initial comment.
The version control system to use is found by cycling through the list
`vc-handled-backends'. The first backend in that list which declares
itself responsible for the file (usually because other files in that
directory are already registered under that backend) will be used to
register the file. If no backend declares itself responsible, the
first backend that could register the file is used."
(interactive "P")
(unless buffer-file-name (error "No visited file"))
(when (vc-backend buffer-file-name)
(if (vc-registered buffer-file-name)
(error "This file is already registered")
(unless (y-or-n-p "Previous master file has vanished. Make a new one? ")
(error "Aborted"))))
;; Watch out for new buffers of size 0: the corresponding file
;; does not exist yet, even though buffer-modified-p is nil.
(if (and (not (buffer-modified-p))
(zerop (buffer-size))
(not (file-exists-p buffer-file-name)))
(set-buffer-modified-p t))
(vc-buffer-sync)
(vc-start-entry (list buffer-file-name)
(if set-version
(read-string (format "Initial version level for %s: "
(buffer-name)))
(vc-call-backend (vc-responsible-backend buffer-file-name)
'init-version))
(or comment (not vc-initial-comment))
nil
"Enter initial comment."
(lambda (files rev comment)
(dolist (file files)
(message "Registering %s... " file)
(let ((backend (vc-responsible-backend file t)))
(vc-file-clearprops file)
(vc-call-backend backend 'register (list file) rev comment)
(vc-file-setprop file 'vc-backend backend)
(unless vc-make-backup-files
(make-local-variable 'backup-inhibited)
(setq backup-inhibited t)))
(message "Registering %s... done" file)))))
(defun vc-register-with (backend)
"Register the current file with a specified back end."
(interactive "SBackend: ")
(if (not (member backend vc-handled-backends))
(error "Unknown back end."))
(let ((vc-handled-backends (list backend)))
(call-interactively 'vc-register)))
(defun vc-resynch-window (file &optional keep noquery)
"If FILE is in the current buffer, either revert or unvisit it.
The choice between revert (to see expanded keywords) and unvisit depends on
`vc-keep-workfiles'. NOQUERY if non-nil inhibits confirmation for
reverting. NOQUERY should be t *only* if it is known the only
difference between the buffer and the file is due to version control
rather than user editing!"
(and (string= buffer-file-name file)
(if keep
(progn
(vc-revert-buffer-internal t noquery)
;; TODO: Adjusting view mode might no longer be necessary
;; after RMS change to files.el of 1999-08-08. Investigate
;; this when we install the new VC.
(and view-read-only
(if (file-writable-p file)
(and view-mode
(let ((view-old-buffer-read-only nil))
(view-mode-exit)))
(and (not view-mode)
(not (eq (get major-mode 'mode-class) 'special))
(view-mode-enter))))
(vc-mode-line buffer-file-name))
(kill-buffer (current-buffer)))))
(defun vc-resynch-buffer (file &optional keep noquery)
"If FILE is currently visited, resynch its buffer."
(if (string= buffer-file-name file)
(vc-resynch-window file keep noquery)
(let ((buffer (get-file-buffer file)))
(if buffer
(with-current-buffer buffer
(vc-resynch-window file keep noquery)))))
(vc-dired-resynch-file file))
(defun vc-start-entry (files rev comment initial-contents msg action &optional after-hook)
"Accept a comment for an operation on FILES revision REV.
If COMMENT is nil, pop up a VC-log buffer, emit MSG, and set the
action on close to ACTION. If COMMENT is a string and
INITIAL-CONTENTS is non-nil, then COMMENT is used as the initial
contents of the log entry buffer. If COMMENT is a string and
INITIAL-CONTENTS is nil, do action immediately as if the user had
entered COMMENT. If COMMENT is t, also do action immediately with an
empty comment. Remember the file's buffer in `vc-parent-buffer'
\(current one if no file). AFTER-HOOK specifies the local value
for vc-log-operation-hook."
(let ((parent
(if (and files (equal (length files) 1))
(get-file-buffer (car files))
(current-buffer))))
(if vc-before-checkin-hook
(if files
(with-current-buffer parent
(run-hooks 'vc-before-checkin-hook))
(run-hooks 'vc-before-checkin-hook)))
(if (and comment (not initial-contents))
(set-buffer (get-buffer-create "*VC-log*"))
(pop-to-buffer (get-buffer-create "*VC-log*")))
(set (make-local-variable 'vc-parent-buffer) parent)
(set (make-local-variable 'vc-parent-buffer-name)
(concat " from " (buffer-name vc-parent-buffer)))
;;(if file (vc-mode-line file))
(vc-log-edit files)
(make-local-variable 'vc-log-after-operation-hook)
(if after-hook
(setq vc-log-after-operation-hook after-hook))
(setq vc-log-operation action)
(setq vc-log-version rev)
(when comment
(erase-buffer)
(when (stringp comment) (insert comment)))
(if (or (not comment) initial-contents)
(message "%s Type C-c C-c when done" msg)
(vc-finish-logentry (eq comment t)))))
(defun vc-checkout (file &optional writable rev)
"Retrieve a copy of the revision REV of FILE.
If WRITABLE is non-nil, make sure the retrieved file is writable.
REV defaults to the latest revision.
After check-out, runs the normal hook `vc-checkout-hook'."
(and writable
(not rev)
(vc-call make-version-backups-p file)
(vc-up-to-date-p file)
(vc-make-version-backup file))
(with-vc-properties
(list file)
(condition-case err
(vc-call checkout file writable rev)
(file-error
;; Maybe the backend is not installed ;-(
(when writable
(let ((buf (get-file-buffer file)))
(when buf (with-current-buffer buf (toggle-read-only -1)))))
(signal (car err) (cdr err))))
`((vc-state . ,(if (or (eq (vc-checkout-model file) 'implicit)
(not writable))
(if (vc-call latest-on-branch-p file)
'up-to-date
'needs-patch)
'edited))
(vc-checkout-time . ,(nth 5 (file-attributes file)))))
(vc-resynch-buffer file t t)
(run-hooks 'vc-checkout-hook))
(defun vc-steal-lock (file rev owner)
"Steal the lock on FILE."
(let (file-description)
(if rev
(setq file-description (format "%s:%s" file rev))
(setq file-description file))
(if (not (yes-or-no-p (format "Steal the lock on %s from %s? "
file-description owner)))
(error "Steal canceled"))
(message "Stealing lock on %s..." file)
(with-vc-properties
(list file)
(vc-call steal-lock file rev)
`((vc-state . edited)))
(vc-resynch-buffer file t t)
(message "Stealing lock on %s...done" file)
;; Write mail after actually stealing, because if the stealing
;; goes wrong, we don't want to send any mail.
(compose-mail owner (format "Stolen lock on %s" file-description))
(setq default-directory (expand-file-name "~/"))
(goto-char (point-max))
(insert
(format "I stole the lock on %s, " file-description)
(current-time-string)
".\n")
(message "Please explain why you stole the lock. Type C-c C-c when done.")))
(defun vc-checkin (files &optional rev comment initial-contents)
"Check in FILES.
The optional argument REV may be a string specifying the new version
level (if nil increment the current level). COMMENT is a comment
string; if omitted, a buffer is popped up to accept a comment. If
INITIAL-CONTENTS is non-nil, then COMMENT is used as the initial contents
of the log entry buffer.
If `vc-keep-workfiles' is nil, FILE is deleted afterwards, provided
that the version control system supports this mode of operation.
Runs the normal hook `vc-checkin-hook'."
(vc-start-entry
files rev comment initial-contents
"Enter a change comment."
(lambda (files rev comment)
(message "Checking in %s..." (vc-delistify files))
;; "This log message intentionally left almost blank".
;; RCS 5.7 gripes about white-space-only comments too.
(or (and comment (string-match "[^\t\n ]" comment))
(setq comment "*** empty log message ***"))
(with-vc-properties
files
;; We used to change buffers to get local value of vc-checkin-switches,
;; but 'the' local buffer is not a well-defined concept for filesets.
(progn
(vc-call checkin files rev comment)
(mapc 'vc-delete-automatic-version-backups files))
`((vc-state . up-to-date)
(vc-checkout-time . ,(nth 5 (file-attributes file)))
(vc-workfile-version . nil)))
(message "Checking in %s...done" (vc-delistify files)))
'vc-checkin-hook))
(defun vc-finish-logentry (&optional nocomment)
"Complete the operation implied by the current log entry.
Use the contents of the current buffer as a check-in or registration
comment. If the optional arg NOCOMMENT is non-nil, then don't check
the buffer contents as a comment."
(interactive)
;; Check and record the comment, if any.
(unless nocomment
;; Comment too long?
(vc-call-backend (or (and vc-log-fileset (vc-backend (car vc-log-fileset)))
(vc-responsible-backend default-directory))
'logentry-check)
(run-hooks 'vc-logentry-check-hook))
;; Sync parent buffer in case the user modified it while editing the comment.
;; But not if it is a vc-dired buffer.
(with-current-buffer vc-parent-buffer
(or vc-dired-mode (vc-buffer-sync)))
(if (not vc-log-operation)
(error "No log operation is pending"))
;; save the parameters held in buffer-local variables
(let ((log-operation vc-log-operation)
(log-fileset vc-log-fileset)
(log-version vc-log-version)
(log-entry (buffer-string))
(after-hook vc-log-after-operation-hook)
(tmp-vc-parent-buffer vc-parent-buffer))
(pop-to-buffer vc-parent-buffer)
;; OK, do it to it
(save-excursion
(funcall log-operation
log-fileset
log-version
log-entry))
;; Remove checkin window (after the checkin so that if that fails
;; we don't zap the *VC-log* buffer and the typing therein).
(let ((logbuf (get-buffer "*VC-log*")))
(cond ((and logbuf vc-delete-logbuf-window)
(delete-windows-on logbuf (selected-frame))
;; Kill buffer and delete any other dedicated windows/frames.
(kill-buffer logbuf))
(logbuf (pop-to-buffer "*VC-log*")
(bury-buffer)
(pop-to-buffer tmp-vc-parent-buffer))))
;; Now make sure we see the expanded headers
(if log-fileset
(mapc
(lambda (file) (vc-resynch-buffer file vc-keep-workfiles t))
log-fileset))
(if vc-dired-mode
(dired-move-to-filename))
(run-hooks after-hook 'vc-finish-logentry-hook)))
;;; Additional entry points for examining version histories
(defun vc-coding-system-for-diff (file)
"Return the coding system for reading diff output for FILE."
(or coding-system-for-read
;; if we already have this file open,
;; use the buffer's coding system
(let ((buf (find-buffer-visiting file)))
(if buf (with-current-buffer buf
buffer-file-coding-system)))
;; otherwise, try to find one based on the file name
(car (find-operation-coding-system 'insert-file-contents file))
;; and a final fallback
'undecided))
(defun vc-switches (backend op)
(let ((switches
(or (if backend
(let ((sym (vc-make-backend-sym
backend (intern (concat (symbol-name op)
"-switches")))))
(if (boundp sym) (symbol-value sym))))
(let ((sym (intern (format "vc-%s-switches" (symbol-name op)))))
(if (boundp sym) (symbol-value sym)))
(cond
((eq op 'diff) diff-switches)))))
(if (stringp switches) (list switches)
;; If not a list, return nil.
;; This is so we can set vc-diff-switches to t to override
;; any switches in diff-switches.
(if (listp switches) switches))))
;; Old def for compatibility with Emacs-21.[123].
(defmacro vc-diff-switches-list (backend) `(vc-switches ',backend 'diff))
(make-obsolete 'vc-diff-switches-list 'vc-switches "22.1")
(defun vc-diff-sentinel (verbose rev1-name rev2-name)
;; Did changes get generated into the buffer?
(if (not (zerop (buffer-size (get-buffer "*vc-diff*"))))
(progn
(pop-to-buffer "*vc-diff*")
;; Gnus-5.8.5 sets up an autoload for diff-mode, even if it's
;; not available. Work around that.
(if (require 'diff-mode nil t) (diff-mode))
(goto-char (point-max))
(if verbose
(insert (format "\n\nDiffs between %s and %s end here." rev1-name rev2-name)))
(goto-char (point-min))
(if verbose
(insert (format "Diffs between %s and %s:\n\n" rev1-name rev2-name)))
(shrink-window-if-larger-than-buffer)
t)
(progn
(message "No changes between %s and %s" rev1-name rev2-name)
nil)))
(defun vc-diff-internal (backend async files rev1 rev2 &optional verbose)
"Report diffs between two revisions of a fileset.
Diff output goes to the *vc-diff* buffer. The function
returns t if the buffer had changes, nil otherwise."
(let* ((filenames (vc-delistify files))
(rev1-name (or rev1 "focus version"))
(rev2-name (or rev2 "workfile"))
;; Set coding system based on the first file. It's a kluge,
;; but the only way to set it for each file included would
;; be to call the back end separarely for each file.
(coding-system-for-read
(if files (vc-coding-system-for-diff (car files)) 'undecided)))
(vc-setup-buffer "*vc-diff*")
(message "Finding changes in..." filenames)
;; Many backends don't handle well the case of a file that has been
;; added but not yet committed to the repo (notably CVS and Subversion).
;; Do that work here so the backends don't have to futz with it.
(let ((filtered '()))
(dolist (file files)
(cond ((and (not (file-directory-p file)) (string= (vc-workfile-version file) "0"))
(progn
;; This file is added but not yet committed;
;; there is no master file to diff against.
(if (or rev1 rev2)
(error "No revisions of %s exist" file)
;; We regard this as "changed".
;; Diff it against /dev/null.
(apply 'vc-do-command "*vc-diff*"
1 "diff" file
(append (vc-switches nil 'diff) '("/dev/null"))))))
(t
(add-to-list 'filtered file t))))
(let ((vc-disable-async-diff (not async)))
(vc-call-backend backend 'diff filtered rev1 rev2 "*vc-diff*")))
(set-buffer "*vc-diff*")
;; This odd-looking code is because in the non-async case we
;; actually want to pass the return value from vc-diff-sentinel
;; back to the caller.
(if async
(vc-exec-after `(vc-diff-sentinel verbose rev1-name rev2-name))
(vc-diff-sentinel verbose rev1-name rev2-name))))
;;;###autoload
(defun vc-history-diff (rev1 rev2)
"Report diffs between revisions of files in the repository history."
(interactive "sOlder revision: \nsNewer revision: ")
(let* ((files (vc-deduce-fileset t))
(first (car files))
(backend
(cond ((file-directory-p first)
(vc-responsible-backend first))
(t
(vc-backend first)))))
(if (string= rev1 "") (setq rev1 nil))
(if (string= rev2 "") (setq rev2 nil))
(if (and (not rev1) rev2)
(error "Not a valid revision range."))
(vc-diff-internal backend t files rev1 rev2 (interactive-p))))
;;;###autoload
(defun vc-diff (historic)
"Display diffs between file versions.
Normally this compares the current file and buffer with the most
recent checked in version of that file. This uses no arguments. With
a prefix argument HISTORIC, it reads the file name to use and two
version designators specifying which versions to compare."
(interactive "P")
(if historic
(call-interactively 'vc-history-diff)
(let* ((files (vc-deduce-fileset t))
(first (car files))
(backend
(cond ((file-directory-p first)
(vc-responsible-backend first))
(t
(vc-backend first)))))
(vc-diff-internal backend t files nil nil (interactive-p)))))
;;;###autoload
(defun vc-version-other-window (rev)
"Visit version REV of the current file in another window.
If the current file is named `F', the version is named `F.~REV~'.
If `F.~REV~' already exists, use it instead of checking it out again."
(interactive "sVersion to visit (default is focus version): ")
(vc-ensure-vc-buffer)
(let* ((file buffer-file-name)
(version (if (string-equal rev "")
(vc-workfile-version file)
rev)))
(switch-to-buffer-other-window (vc-find-version file version))))
(defun vc-find-version (file version)
"Read VERSION of FILE into a buffer and return the buffer."
(let ((automatic-backup (vc-version-backup-file-name file version))
(filebuf (or (get-file-buffer file) (current-buffer)))
(filename (vc-version-backup-file-name file version 'manual)))
(unless (file-exists-p filename)
(if (file-exists-p automatic-backup)
(rename-file automatic-backup filename nil)
(message "Checking out %s..." filename)
(with-current-buffer filebuf
(let ((failed t))
(unwind-protect
(let ((coding-system-for-read 'no-conversion)
(coding-system-for-write 'no-conversion))
(with-temp-file filename
(let ((outbuf (current-buffer)))
;; Change buffer to get local value of
;; vc-checkout-switches.
(with-current-buffer filebuf
(vc-call find-version file version outbuf))))
(setq failed nil))
(if (and failed (file-exists-p filename))
(delete-file filename))))
(vc-mode-line file))
(message "Checking out %s...done" filename)))
(find-file-noselect filename)))
;; Header-insertion code
;;;###autoload
(defun vc-insert-headers ()
"Insert headers into a file for use with a version control system.
Headers desired are inserted at point, and are pulled from
the variable `vc-BACKEND-header'."
(interactive)
(vc-ensure-vc-buffer)
(save-excursion
(save-restriction
(widen)
(if (or (not (vc-check-headers))
(y-or-n-p "Version headers already exist. Insert another set? "))
(let* ((delims (cdr (assq major-mode vc-comment-alist)))
(comment-start-vc (or (car delims) comment-start "#"))
(comment-end-vc (or (car (cdr delims)) comment-end ""))
(hdsym (vc-make-backend-sym (vc-backend buffer-file-name)
'header))
(hdstrings (and (boundp hdsym) (symbol-value hdsym))))
(dolist (s hdstrings)
(insert comment-start-vc "\t" s "\t"
comment-end-vc "\n"))
(if vc-static-header-alist
(dolist (f vc-static-header-alist)
(if (string-match (car f) buffer-file-name)
(insert (format (cdr f) (car hdstrings)))))))))))
(defun vc-clear-headers (&optional file)
"Clear all version headers in the current buffer (or FILE).
The headers are reset to their non-expanded form."
(let* ((filename (or file buffer-file-name))
(visited (find-buffer-visiting filename))
(backend (vc-backend filename)))
(when (vc-find-backend-function backend 'clear-headers)
(if visited
(let ((context (vc-buffer-context)))
;; save-excursion may be able to relocate point and mark
;; properly. If it fails, vc-restore-buffer-context
;; will give it a second try.
(save-excursion
(vc-call-backend backend 'clear-headers))
(vc-restore-buffer-context context))
(set-buffer (find-file-noselect filename))
(vc-call-backend backend 'clear-headers)
(kill-buffer filename)))))
;;;###autoload
(defun vc-merge ()
"Merge changes between two versions into the current buffer's file.
This asks for two versions to merge from in the minibuffer. If the
first version is a branch number, then merge all changes from that
branch. If the first version is empty, merge news, i.e. recent changes
from the current branch.
See Info node `Merging'."
(interactive)
(vc-ensure-vc-buffer)
(vc-buffer-sync)
(let* ((file buffer-file-name)
(backend (vc-backend file))
(state (vc-state file))
first-version second-version status)
(cond
((stringp state)
(error "File is locked by %s" state))
((not (vc-editable-p file))
(if (y-or-n-p
"File must be checked out for merging. Check out now? ")
(vc-checkout file t)
(error "Merge aborted"))))
(setq first-version
(read-string (concat "Branch or version to merge from "
"(default news on current branch): ")))
(if (string= first-version "")
(if (not (vc-find-backend-function backend 'merge-news))
(error "Sorry, merging news is not implemented for %s" backend)
(setq status (vc-call merge-news file)))
(if (not (vc-find-backend-function backend 'merge))
(error "Sorry, merging is not implemented for %s" backend)
(if (not (vc-branch-p first-version))
(setq second-version
(read-string "Second version: "
(concat (vc-branch-part first-version) ".")))
;; We want to merge an entire branch. Set versions
;; accordingly, so that vc-BACKEND-merge understands us.
(setq second-version first-version)
;; first-version must be the starting point of the branch
(setq first-version (vc-branch-part first-version)))
(setq status (vc-call merge file first-version second-version))))
(vc-maybe-resolve-conflicts file status "WORKFILE" "MERGE SOURCE")))
(defun vc-maybe-resolve-conflicts (file status &optional name-A name-B)
(vc-resynch-buffer file t (not (buffer-modified-p)))
(if (zerop status) (message "Merge successful")
(smerge-mode 1)
(message "File contains conflicts.")))
;;;###autoload
(defalias 'vc-resolve-conflicts 'smerge-ediff)
;; The VC directory major mode. Coopt Dired for this.
;; All VC commands get mapped into logical equivalents.
(defvar vc-dired-switches)
(defvar vc-dired-terse-mode)
(defvar vc-dired-mode-map
(let ((map (make-sparse-keymap))
(vmap (make-sparse-keymap)))
(define-key map "\C-xv" vmap)
(define-key map "v" vmap)
(set-keymap-parent vmap vc-prefix-map)
(define-key vmap "t" 'vc-dired-toggle-terse-mode)
map))
(define-derived-mode vc-dired-mode dired-mode "Dired under VC"
"The major mode used in VC directory buffers.
It works like Dired, but lists only files under version control, with
the current VC state of each file being indicated in the place of the
file's link count, owner, group and size. Subdirectories are also
listed, and you may insert them into the buffer as desired, like in
Dired.
All Dired commands operate normally, with the exception of `v', which
is redefined as the version control prefix, so that you can type
`vl', `v=' etc. to invoke `vc-print-log', `vc-diff', and the like on
the file named in the current Dired buffer line. `vv' invokes
`vc-next-action' on this file, or on all files currently marked.
There is a special command, `*l', to mark all files currently locked."
;; define-derived-mode does it for us in Emacs-21, but not in Emacs-20.
;; We do it here because dired might not be loaded yet
;; when vc-dired-mode-map is initialized.
(set-keymap-parent vc-dired-mode-map dired-mode-map)
(add-hook 'dired-after-readin-hook 'vc-dired-hook nil t)
;; The following is slightly modified from files.el,
;; because file lines look a bit different in vc-dired-mode
;; (the column before the date does not end in a digit).
;; albinus: It should be done in the original declaration. Problem
;; is the optional empty state-info; otherwise ")" would be good
;; enough as delimeter.
(set (make-local-variable 'directory-listing-before-filename-regexp)
(let* ((l "\\([A-Za-z]\\|[^\0-\177]\\)")
;; In some locales, month abbreviations are as short as 2 letters,
;; and they can be followed by ".".
(month (concat l l "+\\.?"))
(s " ")
(yyyy "[0-9][0-9][0-9][0-9]")
(dd "[ 0-3][0-9]")
(HH:MM "[ 0-2][0-9]:[0-5][0-9]")
(seconds "[0-6][0-9]\\([.,][0-9]+\\)?")
(zone "[-+][0-2][0-9][0-5][0-9]")
(iso-mm-dd "[01][0-9]-[0-3][0-9]")
(iso-time (concat HH:MM "\\(:" seconds "\\( ?" zone "\\)?\\)?"))
(iso (concat "\\(\\(" yyyy "-\\)?" iso-mm-dd "[ T]" iso-time
"\\|" yyyy "-" iso-mm-dd "\\)"))
(western (concat "\\(" month s "+" dd "\\|" dd "\\.?" s month "\\)"
s "+"
"\\(" HH:MM "\\|" yyyy "\\)"))
(western-comma (concat month s "+" dd "," s "+" yyyy))
;; Japanese MS-Windows ls-lisp has one-digit months, and
;; omits the Kanji characters after month and day-of-month.
(mm "[ 0-1]?[0-9]")
(japanese
(concat mm l "?" s dd l "?" s "+"
"\\(" HH:MM "\\|" yyyy l "?" "\\)")))
;; the .* below ensures that we find the last match on a line
(concat ".*" s
"\\(" western "\\|" western-comma "\\|" japanese "\\|" iso "\\)"
s "+")))
(and (boundp 'vc-dired-switches)
vc-dired-switches
(set (make-local-variable 'dired-actual-switches)
vc-dired-switches))
(set (make-local-variable 'vc-dired-terse-mode) vc-dired-terse-display)
(setq vc-dired-mode t))
(defun vc-dired-toggle-terse-mode ()
"Toggle terse display in VC Dired."
(interactive)
(if (not vc-dired-mode)
nil
(setq vc-dired-terse-mode (not vc-dired-terse-mode))
(if vc-dired-terse-mode
(vc-dired-hook)
(revert-buffer))))
(defun vc-dired-mark-locked ()
"Mark all files currently locked."
(interactive)
(dired-mark-if (let ((f (dired-get-filename nil t)))
(and f
(not (file-directory-p f))
(not (vc-up-to-date-p f))))
"locked file"))
(define-key vc-dired-mode-map "*l" 'vc-dired-mark-locked)
(defun vc-dired-reformat-line (vc-info)
"Reformat a directory-listing line.
Replace various columns with version control information, VC-INFO.
This code, like dired, assumes UNIX -l format."
(beginning-of-line)
(when (re-search-forward
;; Match link count, owner, group, size. Group may be missing,
;; and only the size is present in OS/2 -l format.
"^..[drwxlts-]+ \\( *[0-9]+\\( [^ ]+ +\\([^ ]+ +\\)?[0-9]+\\)?\\) "
(line-end-position) t)
(replace-match (substring (concat vc-info " ") 0 10)
t t nil 1)))
(defun vc-dired-hook ()
"Reformat the listing according to version control.
Called by dired after any portion of a vc-dired buffer has been read in."
(message "Getting version information... ")
(let (subdir filename (buffer-read-only nil))
(goto-char (point-min))
(while (not (eobp))
(cond
;; subdir header line
((setq subdir (dired-get-subdir))
;; if the backend supports it, get the state
;; of all files in this directory at once
(let ((backend (vc-responsible-backend subdir)))
(if (vc-find-backend-function backend 'dir-state)
(vc-call-backend backend 'dir-state subdir)))
(forward-line 1)
;; erase (but don't remove) the "total" line
(delete-region (point) (line-end-position))
(beginning-of-line)
(forward-line 1))
;; file line
((setq filename (dired-get-filename nil t))
(cond
;; subdir
((file-directory-p filename)
(cond
((member (file-name-nondirectory filename)
vc-directory-exclusion-list)
(let ((pos (point)))
(dired-kill-tree filename)
(goto-char pos)
(dired-kill-line)))
(vc-dired-terse-mode
;; Don't show directories in terse mode. Don't use
;; dired-kill-line to remove it, because in recursive listings,
;; that would remove the directory contents as well.
(delete-region (line-beginning-position)
(progn (forward-line 1) (point))))
((string-match "\\`\\.\\.?\\'" (file-name-nondirectory filename))
(dired-kill-line))
(t
(vc-dired-reformat-line nil)
(forward-line 1))))
;; ordinary file
((and (vc-backend filename)
(not (and vc-dired-terse-mode
(vc-up-to-date-p filename))))
(vc-dired-reformat-line (vc-call dired-state-info filename))
(forward-line 1))
(t
(dired-kill-line))))
;; any other line
(t (forward-line 1))))
(vc-dired-purge))
(message "Getting version information... done")
(save-restriction
(widen)
(cond ((eq (count-lines (point-min) (point-max)) 1)
(goto-char (point-min))
(message "No files locked under %s" default-directory)))))
(defun vc-dired-purge ()
"Remove empty subdirs."
(goto-char (point-min))
(while (dired-get-subdir)
(forward-line 2)
(if (dired-get-filename nil t)
(if (not (dired-next-subdir 1 t))
(goto-char (point-max)))
(forward-line -2)
(if (not (string= (dired-current-directory) default-directory))
(dired-do-kill-lines t "")
;; We cannot remove the top level directory.
;; Just make it look a little nicer.
(forward-line 1)
(or (eobp) (kill-line))
(if (not (dired-next-subdir 1 t))
(goto-char (point-max))))))
(goto-char (point-min)))
(defun vc-dired-buffers-for-dir (dir)
"Return a list of all vc-dired buffers that currently display DIR."
(let (result)
;; Check whether dired is loaded.
(when (fboundp 'dired-buffers-for-dir)
(mapcar (lambda (buffer)
(with-current-buffer buffer
(if vc-dired-mode
(setq result (append result (list buffer))))))
(dired-buffers-for-dir dir)))
result))
(defun vc-dired-resynch-file (file)
"Update the entries for FILE in any VC Dired buffers that list it."
(let ((buffers (vc-dired-buffers-for-dir (file-name-directory file))))
(when buffers
(mapcar (lambda (buffer)
(with-current-buffer buffer
(if (dired-goto-file file)
;; bind vc-dired-terse-mode to nil so that
;; files won't vanish when they are checked in
(let ((vc-dired-terse-mode nil))
(dired-do-redisplay 1)))))
buffers))))
;;;###autoload
(defun vc-directory (dir read-switches)
"Create a buffer in VC Dired Mode for directory DIR.
See Info node `VC Dired Mode'.
With prefix arg READ-SWITCHES, specify a value to override
`dired-listing-switches' when generating the listing."
(interactive "DDired under VC (directory): \nP")
(let ((vc-dired-switches (concat vc-dired-listing-switches
(if vc-dired-recurse "R" ""))))
(if (eq (string-match tramp-file-name-regexp dir) 0)
(error "Sorry, vc-directory does not work over Tramp"))
(if read-switches
(setq vc-dired-switches
(read-string "Dired listing switches: "
vc-dired-switches)))
(require 'dired)
(require 'dired-aux)
(switch-to-buffer
(dired-internal-noselect (expand-file-name (file-name-as-directory dir))
vc-dired-switches
'vc-dired-mode))))
;; Named-configuration entry points
(defun vc-snapshot-precondition (dir)
"Scan the tree below DIR, looking for files not up-to-date.
If any file is not up-to-date, return the name of the first such file.
\(This means, neither snapshot creation nor retrieval is allowed.\)
If one or more of the files are currently visited, return `visited'.
Otherwise, return nil."
(let ((status nil))
(catch 'vc-locked-example
(vc-file-tree-walk
dir
(lambda (f)
(if (not (vc-up-to-date-p f)) (throw 'vc-locked-example f)
(if (get-file-buffer f) (setq status 'visited)))))
status)))
;;;###autoload
(defun vc-create-snapshot (dir name branchp)
"Descending recursively from DIR, make a snapshot called NAME.
For each registered file, the version level of its latest version
becomes part of the named configuration. If the prefix argument
BRANCHP is given, the snapshot is made as a new branch and the files
are checked out in that new branch."
(interactive
(list (read-file-name "Directory: " default-directory default-directory t)
(read-string "New snapshot name: ")
current-prefix-arg))
(message "Making %s... " (if branchp "branch" "snapshot"))
(if (file-directory-p dir) (setq dir (file-name-as-directory dir)))
(vc-call-backend (vc-responsible-backend dir)
'create-snapshot dir name branchp)
(message "Making %s... done" (if branchp "branch" "snapshot")))
;;;###autoload
(defun vc-retrieve-snapshot (dir name)
"Descending recursively from DIR, retrieve the snapshot called NAME.
If NAME is empty, it refers to the latest versions.
If locking is used for the files in DIR, then there must not be any
locked files at or below DIR (but if NAME is empty, locked files are
allowed and simply skipped)."
(interactive
(list (read-file-name "Directory: " default-directory default-directory t)
(read-string "Snapshot name to retrieve (default latest versions): ")))
(let ((update (yes-or-no-p "Update any affected buffers? "))
(msg (if (or (not name) (string= name ""))
(format "Updating %s... " (abbreviate-file-name dir))
(format "Retrieving snapshot into %s... "
(abbreviate-file-name dir)))))
(message "%s" msg)
(vc-call-backend (vc-responsible-backend dir)
'retrieve-snapshot dir name update)
(message "%s" (concat msg "done"))))
;; Miscellaneous other entry points
;;;###autoload
(defun vc-print-log (&optional focus-rev)
"List the change log of the current fileset in a window.
If FOCUS-REV is non-nil, leave the point at that revision."
(interactive)
(let* ((files (vc-deduce-fileset))
(backend (vc-backend (car files)))
(focus-rev (or focus-rev (vc-workfile-version (car files)))))
;; Don't switch to the output buffer before running the command,
;; so that any buffer-local settings in the vc-controlled
;; buffer can be accessed by the command.
(vc-call-backend backend 'print-log files "*vc-change-log*")
(pop-to-buffer "*vc-change-log*")
(vc-exec-after
`(let ((inhibit-read-only t))
(log-view-mode)
(goto-char (point-max)) (forward-line -1)
(while (looking-at "=*\n")
(delete-char (- (match-end 0) (match-beginning 0)))
(forward-line -1))
(goto-char (point-min))
(if (looking-at "[\b\t\n\v\f\r ]+")
(delete-char (- (match-end 0) (match-beginning 0))))
(shrink-window-if-larger-than-buffer)
;; move point to the log entry for the focus revision
(vc-call-backend ',backend 'show-log-entry ',focus-rev)
(set-buffer-modified-p nil)))))
;;;###autoload
(defun vc-revert ()
"Revert working copies of the selected fileset to their repository contents.
This asks for confirmation if the buffer contents are not identical
to the repository version (except for keyword expansion)."
(interactive)
(let* ((files (vc-deduce-fileset))
(backend (vc-backend (car files))))
;; If any of the files is visited by the current buffer, make
;; sure buffer is saved. If the user says `no', abort since
;; we cannot show the changes and ask for confirmation to
;; discard them.
(if (or (not files) (memq (buffer-file-name) files))
(vc-buffer-sync nil))
(dolist (file files)
(if (buffer-modified-p (get-file-buffer file))
(error "Please kill or save all modified buffers before reverting."))
(if (vc-up-to-date-p file)
(unless (yes-or-no-p (format "%s seems up-to-date. Revert anyway? " file))
(error "Revert canceled"))))
(if (vc-diff-internal backend vc-allow-async-revert files nil nil)
(progn
(unless (yes-or-no-p (format "Discard changes in %s? " (vc-delistify files)))
(error "Revert canceled"))
(delete-windows-on "*vc-diff*")
(kill-buffer "*vc-diff*")))
(dolist (file files)
(progn
(message "Reverting %s..." (vc-delistify files))
(vc-revert-file file)
(message "Reverting %s...done" (vc-delistify files))))))
;;;###autoload
(defun vc-rollback ()
"Roll back (remove) the most recent changeset committed to the repository.
This may be either a file-level or a repository-level operation,
depending on the underlying version-control system."
(interactive)
(let* ((files (vc-deduce-fileset))
(backend (vc-backend (car files)))
(granularity (vc-call-backend backend 'revision-granularity)))
(unless (vc-find-backend-function backend 'rollback)
(error "Rollback is not supported in %s" backend))
(if (and (not (eq granularity 'repository)) (/= (length files) 1))
(error "Rollback requires a singleton fileset or repository versioning"))
(if (not (vc-call latest-on-branch-p (car files)))
(error "Rollback is only possible at the tip revision."))
;; If any of the files is visited by the current buffer, make
;; sure buffer is saved. If the user says `no', abort since
;; we cannot show the changes and ask for confirmation to
;; discard them.
(if (or (not files) (memq (buffer-file-name) files))
(vc-buffer-sync nil))
(dolist (file files)
(if (buffer-modified-p (get-file-buffer file))
(error "Please kill or save all modified buffers before rollback."))
(if (not (vc-up-to-date-p file))
(error "Please revert all modified workfiles before rollback.")))
;; Accumulate changes associated with the fileset
(vc-setup-buffer "*vc-diff*")
(not-modified)
(message "Finding changes...")
(let* ((tip (vc-workfile-version (car files)))
(previous (vc-call previous-version (car files) tip)))
(vc-diff-internal backend nil files previous tip))
;; Display changes
(unless (yes-or-no-p "Discard these revisions? ")
(error "Rollback canceled"))
(delete-windows-on "*vc-diff*")
(kill-buffer"*vc-diff*")
;; Do the actual reversions
(message "Rolling back %s..." (vc-delistify files))
(with-vc-properties
files
(vc-call-backend backend 'rollback files)
`((vc-state . ,'up-to-date)
(vc-checkout-time . , (nth 5 (file-attributes file)))
(vc-workfile-version . nil)))
(mapc (lambda (f) (vc-resynch-buffer f t t)) files)
(message "Rolling back %s...done" (vc-delistify files))))
;;;###autoload
(defun vc-update ()
"Update the current fileset's files to their tip versions.
For each one that contains no changes, and is not locked, then this simply
replaces the work file with the latest version on its branch. If the file
contains changes, and the backend supports merging news, then any recent
changes from the current branch are merged into the working file."
(interactive)
(dolist (file (vc-deduce-fileset))
(if (buffer-modified-p (get-file-buffer file))
(error "Please kill or save all modified buffers before updating."))
(if (vc-up-to-date-p file)
(vc-checkout file nil "")
(if (eq (vc-checkout-model file) 'locking)
(if (eq (vc-state file) 'edited)
(error
(substitute-command-keys
"File is locked--type \\[vc-revert] to discard changes"))
(error
(substitute-command-keys
"Unexpected file state (%s)--type \\[vc-next-action] to correct")
(vc-state file)))
(if (not (vc-find-backend-function (vc-backend file) 'merge-news))
(error "Sorry, merging news is not implemented for %s"
(vc-backend file))
(vc-call merge-news file)
(vc-resynch-buffer file t t))))))
(defun vc-version-backup-file (file &optional rev)
"Return name of backup file for revision REV of FILE.
If version backups should be used for FILE, and there exists
such a backup for REV or the current focus version of file,
return its name; otherwise return nil."
(when (vc-call make-version-backups-p file)
(let ((backup-file (vc-version-backup-file-name file rev)))
(if (file-exists-p backup-file)
backup-file
;; there is no automatic backup, but maybe the user made one manually
(setq backup-file (vc-version-backup-file-name file rev 'manual))
(if (file-exists-p backup-file)
backup-file)))))
(defun vc-revert-file (file)
"Revert FILE back to the repository version it was based on."
(with-vc-properties
(list file)
(let ((backup-file (vc-version-backup-file file)))
(when backup-file
(copy-file backup-file file 'ok-if-already-exists 'keep-date)
(vc-delete-automatic-version-backups file))
(vc-call revert file backup-file))
`((vc-state . up-to-date)
(vc-checkout-time . ,(nth 5 (file-attributes file)))))
(vc-resynch-buffer file t t))
;;;###autoload
(defun vc-switch-backend (file backend)
"Make BACKEND the current version control system for FILE.
FILE must already be registered in BACKEND. The change is not
permanent, only for the current session. This function only changes
VC's perspective on FILE, it does not register or unregister it.
By default, this command cycles through the registered backends.
To get a prompt, use a prefix argument."
(interactive
(list
(or buffer-file-name
(error "There is no version-controlled file in this buffer"))
(let ((backend (vc-backend buffer-file-name))
(backends nil))
(unless backend
(error "File %s is not under version control" buffer-file-name))
;; Find the registered backends.
(dolist (backend vc-handled-backends)
(when (vc-call-backend backend 'registered buffer-file-name)
(push backend backends)))
;; Find the next backend.
(let ((def (car (delq backend (append (memq backend backends) backends))))
(others (delete backend backends)))
(cond
((null others) (error "No other backend to switch to"))
(current-prefix-arg
(intern
(upcase
(completing-read
(format "Switch to backend [%s]: " def)
(mapcar (lambda (b) (list (downcase (symbol-name b)))) backends)
nil t nil nil (downcase (symbol-name def))))))
(t def))))))
(unless (eq backend (vc-backend file))
(vc-file-clearprops file)
(vc-file-setprop file 'vc-backend backend)
;; Force recomputation of the state
(unless (vc-call-backend backend 'registered file)
(vc-file-clearprops file)
(error "%s is not registered in %s" file backend))
(vc-mode-line file)))
;;;###autoload
(defun vc-transfer-file (file new-backend)
"Transfer FILE to another version control system NEW-BACKEND.
If NEW-BACKEND has a higher precedence than FILE's current backend
\(i.e. it comes earlier in `vc-handled-backends'), then register FILE in
NEW-BACKEND, using the version number from the current backend as the
base level. If NEW-BACKEND has a lower precedence than the current
backend, then commit all changes that were made under the current
backend to NEW-BACKEND, and unregister FILE from the current backend.
\(If FILE is not yet registered under NEW-BACKEND, register it.)"
(let* ((old-backend (vc-backend file))
(edited (memq (vc-state file) '(edited needs-merge)))
(registered (vc-call-backend new-backend 'registered file))
(move
(and registered ; Never move if not registered in new-backend yet.
;; move if new-backend comes later in vc-handled-backends
(or (memq new-backend (memq old-backend vc-handled-backends))
(y-or-n-p "Final transfer? "))))
(comment nil))
(if (eq old-backend new-backend)
(error "%s is the current backend of %s" new-backend file))
(if registered
(set-file-modes file (logior (file-modes file) 128))
;; `registered' might have switched under us.
(vc-switch-backend file old-backend)
(let* ((rev (vc-workfile-version file))
(modified-file (and edited (make-temp-file file)))
(unmodified-file (and modified-file (vc-version-backup-file file))))
;; Go back to the base unmodified file.
(unwind-protect
(progn
(when modified-file
(copy-file file modified-file 'ok-if-already-exists)
;; If we have a local copy of the unmodified file, handle that
;; here and not in vc-revert-file because we don't want to
;; delete that copy -- it is still useful for OLD-BACKEND.
(if unmodified-file
(copy-file unmodified-file file
'ok-if-already-exists 'keep-date)
(if (y-or-n-p "Get base version from master? ")
(vc-revert-file file))))
(vc-call-backend new-backend 'receive-file file rev))
(when modified-file
(vc-switch-backend file new-backend)
(unless (eq (vc-checkout-model file) 'implicit)
(vc-checkout file t nil))
(rename-file modified-file file 'ok-if-already-exists)
(vc-file-setprop file 'vc-checkout-time nil)))))
(when move
(vc-switch-backend file old-backend)
(setq comment (vc-call comment-history file))
(vc-call unregister file))
(vc-switch-backend file new-backend)
(when (or move edited)
(vc-file-setprop file 'vc-state 'edited)
(vc-mode-line file)
(vc-checkin file nil comment (stringp comment)))))
(defun vc-rename-master (oldmaster newfile templates)
"Rename OLDMASTER to be the master file for NEWFILE based on TEMPLATES."
(let* ((dir (file-name-directory (expand-file-name oldmaster)))
(newdir (or (file-name-directory newfile) ""))
(newbase (file-name-nondirectory newfile))
(masters
;; List of potential master files for `newfile'
(mapcar
(lambda (s) (vc-possible-master s newdir newbase))
templates)))
(if (or (file-symlink-p oldmaster)
(file-symlink-p (file-name-directory oldmaster)))
(error "This is unsafe in the presence of symbolic links"))
(rename-file
oldmaster
(catch 'found
;; If possible, keep the master file in the same directory.
(dolist (f masters)
(if (and f (string= (file-name-directory (expand-file-name f)) dir))
(throw 'found f)))
;; If not, just use the first possible place.
(dolist (f masters)
(and f (or (not (setq dir (file-name-directory f)))
(file-directory-p dir))
(throw 'found f)))
(error "New file lacks a version control directory")))))
(defun vc-delete-file (file)
"Delete file and mark it as such in the version control system."
(interactive "fVC delete file: ")
(let ((buf (get-file-buffer file))
(backend (vc-backend file)))
(unless backend
(error "File %s is not under version control"
(file-name-nondirectory file)))
(unless (vc-find-backend-function backend 'delete-file)
(error "Deleting files under %s is not supported in VC" backend))
(if (and buf (buffer-modified-p buf))
(error "Please save files before deleting them"))
(unless (y-or-n-p (format "Really want to delete %s? "
(file-name-nondirectory file)))
(error "Abort!"))
(unless (or (file-directory-p file) (null make-backup-files))
(with-current-buffer (or buf (find-file-noselect file))
(let ((backup-inhibited nil))
(backup-buffer))))
(vc-call delete-file file)
;; If the backend hasn't deleted the file itself, let's do it for him.
(if (file-exists-p file) (delete-file file))))
;;;###autoload
(defun vc-rename-file (old new)
"Rename file OLD to NEW, and rename its master file likewise."
(interactive "fVC rename file: \nFRename to: ")
(let ((oldbuf (get-file-buffer old)))
(if (and oldbuf (buffer-modified-p oldbuf))
(error "Please save files before moving them"))
(if (get-file-buffer new)
(error "Already editing new file name"))
(if (file-exists-p new)
(error "New file already exists"))
(let ((state (vc-state old)))
(unless (memq state '(up-to-date edited))
(error "Please %s files before moving them"
(if (stringp state) "check in" "update"))))
(vc-call rename-file old new)
(vc-file-clearprops old)
;; Move the actual file (unless the backend did it already)
(if (file-exists-p old) (rename-file old new))
;; ?? Renaming a file might change its contents due to keyword expansion.
;; We should really check out a new copy if the old copy was precisely equal
;; to some checked in version. However, testing for this is tricky....
(if oldbuf
(with-current-buffer oldbuf
(let ((buffer-read-only buffer-read-only))
(set-visited-file-name new))
(vc-backend new)
(vc-mode-line new)
(set-buffer-modified-p nil)))))
;;;###autoload
(defun vc-update-change-log (&rest args)
"Find change log file and add entries from recent version control logs.
Normally, find log entries for all registered files in the default
directory.
With prefix arg of \\[universal-argument], only find log entries for the current buffer's file.
With any numeric prefix arg, find log entries for all currently visited
files that are under version control. This puts all the entries in the
log for the default directory, which may not be appropriate.
From a program, any ARGS are assumed to be filenames for which
log entries should be gathered."
(interactive
(cond ((consp current-prefix-arg) ;C-u
(list buffer-file-name))
(current-prefix-arg ;Numeric argument.
(let ((files nil)
(buffers (buffer-list))
file)
(while buffers
(setq file (buffer-file-name (car buffers)))
(and file (vc-backend file)
(setq files (cons file files)))
(setq buffers (cdr buffers)))
files))
(t
;; Don't supply any filenames to backend; this means
;; it should find all relevant files relative to
;; the default-directory.
nil)))
(dolist (file (or args (list default-directory)))
(if (eq (string-match tramp-file-name-regexp file) 0)
(error "Sorry, vc-update-change-log does not work over Tramp")))
(vc-call-backend (vc-responsible-backend default-directory)
'update-changelog args))
;;; The default back end. Assumes RCS-like version numbering.
(defun vc-default-revision-granularity ()
(error "Your backend will not work with this version of VC mode."))
;; functions that operate on RCS revision numbers. This code should
;; also be moved into the backends. It stays for now, however, since
;; it is used in code below.
;;;###autoload
(defun vc-trunk-p (rev)
"Return t if REV is a revision on the trunk."
(not (eq nil (string-match "\\`[0-9]+\\.[0-9]+\\'" rev))))
(defun vc-branch-p (rev)
"Return t if REV is a branch revision."
(not (eq nil (string-match "\\`[0-9]+\\(\\.[0-9]+\\.[0-9]+\\)*\\'" rev))))
;;;###autoload
(defun vc-branch-part (rev)
"Return the branch part of a revision number REV."
(let ((index (string-match "\\.[0-9]+\\'" rev)))
(if index
(substring rev 0 index))))
(defun vc-minor-part (rev)
"Return the minor version number of a revision number REV."
(string-match "[0-9]+\\'" rev)
(substring rev (match-beginning 0) (match-end 0)))
(defun vc-default-previous-version (backend file rev)
"Return the version number immediately preceding REV for FILE,
or nil if there is no previous version. This default
implementation works for MAJOR.MINOR-style version numbers as
used by RCS and CVS."
(let ((branch (vc-branch-part rev))
(minor-num (string-to-number (vc-minor-part rev))))
(when branch
(if (> minor-num 1)
;; version does probably not start a branch or release
(concat branch "." (number-to-string (1- minor-num)))
(if (vc-trunk-p rev)
;; we are at the beginning of the trunk --
;; don't know anything to return here
nil
;; we are at the beginning of a branch --
;; return version of starting point
(vc-branch-part branch))))))
(defun vc-default-next-version (backend file rev)
"Return the version number immediately following REV for FILE,
or nil if there is no next version. This default implementation
works for MAJOR.MINOR-style version numbers as used by RCS
and CVS."
(when (not (string= rev (vc-workfile-version file)))
(let ((branch (vc-branch-part rev))
(minor-num (string-to-number (vc-minor-part rev))))
(concat branch "." (number-to-string (1+ minor-num))))))
(defun vc-default-responsible-p (backend file)
"Indicate whether BACKEND is reponsible for FILE.
The default is to return nil always."
nil)
(defun vc-default-could-register (backend file)
"Return non-nil if BACKEND could be used to register FILE.
The default implementation returns t for all files."
t)
(defun vc-default-latest-on-branch-p (backend file)
"Return non-nil if FILE is the latest on its branch.
This default implementation always returns non-nil, which means that
editing non-current versions is not supported by default."
t)
(defun vc-default-init-version (backend) vc-default-init-version)
(defun vc-default-update-changelog (backend files)
"Default implementation of update-changelog.
Uses `rcs2log' which only works for RCS and CVS."
;; FIXME: We (c|sh)ould add support for cvs2cl
(let ((odefault default-directory)
(changelog (find-change-log))
;; Presumably not portable to non-Unixy systems, along with rcs2log:
(tempfile (make-temp-file
(expand-file-name "vc"
(or small-temporary-file-directory
temporary-file-directory))))
(login-name (or user-login-name
(format "uid%d" (number-to-string (user-uid)))))
(full-name (or add-log-full-name
(user-full-name)
(user-login-name)
(format "uid%d" (number-to-string (user-uid)))))
(mailing-address (or add-log-mailing-address
user-mail-address)))
(find-file-other-window changelog)
(barf-if-buffer-read-only)
(vc-buffer-sync)
(undo-boundary)
(goto-char (point-min))
(push-mark)
(message "Computing change log entries...")
(message "Computing change log entries... %s"
(unwind-protect
(progn
(setq default-directory odefault)
(if (eq 0 (apply 'call-process
(expand-file-name "rcs2log"
exec-directory)
nil (list t tempfile) nil
"-c" changelog
"-u" (concat login-name
"\t" full-name
"\t" mailing-address)
(mapcar
(lambda (f)
(file-relative-name
(if (file-name-absolute-p f)
f
(concat odefault f))))
files)))
"done"
(pop-to-buffer (get-buffer-create "*vc*"))
(erase-buffer)
(insert-file-contents tempfile)
"failed"))
(setq default-directory (file-name-directory changelog))
(delete-file tempfile)))))
(defun vc-default-find-version (backend file rev buffer)
"Provide the new `find-version' op based on the old `checkout' op.
This is only for compatibility with old backends. They should be updated
to provide the `find-version' operation instead."
(let ((tmpfile (make-temp-file (expand-file-name file))))
(unwind-protect
(progn
(vc-call-backend backend 'checkout file nil rev tmpfile)
(with-current-buffer buffer
(insert-file-contents-literally tmpfile)))
(delete-file tmpfile))))
(defun vc-default-dired-state-info (backend file)
(let* ((state (vc-state file))
(statestring
(cond
((stringp state) (concat "(" state ")"))
((eq state 'edited) (concat "(" (vc-user-login-name file) ")"))
((eq state 'needs-merge) "(merge)")
((eq state 'needs-patch) "(patch)")
((eq state 'unlocked-changes) "(stale)")))
(buffer
(get-file-buffer file))
(modflag
(if (and buffer (buffer-modified-p buffer)) "+" "")))
(concat statestring modflag)))
(defun vc-default-rename-file (backend old new)
(condition-case nil
(add-name-to-file old new)
(error (rename-file old new)))
(vc-delete-file old)
(with-current-buffer (find-file-noselect new)
(vc-register)))
(defalias 'vc-default-logentry-check 'ignore)
(defun vc-default-check-headers (backend)
"Default implementation of check-headers; always returns nil."
nil)
(defun vc-default-show-log-entry (backend rev)
(with-no-warnings
(log-view-goto-rev rev)))
(defun vc-default-comment-history (backend file)
"Return a string with all log entries stored in BACKEND for FILE."
(if (vc-find-backend-function backend 'print-log)
(with-current-buffer "*vc*"
(vc-call print-log file)
(vc-call wash-log)
(buffer-string))))
(defun vc-default-unregister (backend file)
"Default implementation of `vc-unregister', signals an error."
(error "Unregistering files is not supported for %s" backend))
(defun vc-default-receive-file (backend file rev)
"Let BACKEND receive FILE from another version control system."
(vc-call-backend backend 'register file rev ""))
(defun vc-default-create-snapshot (backend dir name branchp)
(when branchp
(error "VC backend %s does not support module branches" backend))
(let ((result (vc-snapshot-precondition dir)))
(if (stringp result)
(error "File %s is not up-to-date" result)
(vc-file-tree-walk
dir
(lambda (f)
(vc-call assign-name f name))))))
(defun vc-default-retrieve-snapshot (backend dir name update)
(if (string= name "")
(progn
(vc-file-tree-walk
dir
(lambda (f) (and
(vc-up-to-date-p f)
(vc-error-occurred
(vc-call checkout f nil "")
(if update (vc-resynch-buffer f t t)))))))
(let ((result (vc-snapshot-precondition dir)))
(if (stringp result)
(error "File %s is locked" result)
(setq update (and (eq result 'visited) update))
(vc-file-tree-walk
dir
(lambda (f) (vc-error-occurred
(vc-call checkout f nil name)
(if update (vc-resynch-buffer f t t)))))))))
(defun vc-default-revert (backend file contents-done)
(unless contents-done
(let ((rev (vc-workfile-version file))
(file-buffer (or (get-file-buffer file) (current-buffer))))
(message "Checking out %s..." file)
(let ((failed t)
(backup-name (car (find-backup-file-name file))))
(when backup-name
(copy-file file backup-name 'ok-if-already-exists 'keep-date)
(unless (file-writable-p file)
(set-file-modes file (logior (file-modes file) 128))))
(unwind-protect
(let ((coding-system-for-read 'no-conversion)
(coding-system-for-write 'no-conversion))
(with-temp-file file
(let ((outbuf (current-buffer)))
;; Change buffer to get local value of vc-checkout-switches.
(with-current-buffer file-buffer
(let ((default-directory (file-name-directory file)))
(vc-call find-version file rev outbuf)))))
(setq failed nil))
(when backup-name
(if failed
(rename-file backup-name file 'ok-if-already-exists)
(and (not vc-make-backup-files) (delete-file backup-name))))))
(message "Checking out %s...done" file))))
(defun vc-check-headers ()
"Check if the current file has any headers in it."
(interactive)
(vc-call-backend (vc-backend buffer-file-name) 'check-headers))
;;; Annotate functionality
;; Declare globally instead of additional parameter to
;; temp-buffer-show-function (not possible to pass more than one
;; parameter). The use of annotate-ratio is deprecated in favor of
;; annotate-mode, which replaces it with the more sensible "span-to
;; days", along with autoscaling support.
(defvar vc-annotate-ratio nil "Global variable.")
;; internal buffer-local variables
(defvar vc-annotate-backend nil)
(defvar vc-annotate-parent-file nil)
(defvar vc-annotate-parent-rev nil)
(defvar vc-annotate-parent-display-mode nil)
(defconst vc-annotate-font-lock-keywords
;; The fontification is done by vc-annotate-lines instead of font-lock.
'((vc-annotate-lines)))
(define-derived-mode vc-annotate-mode fundamental-mode "Annotate"
"Major mode for output buffers of the `vc-annotate' command.
You can use the mode-specific menu to alter the time-span of the used
colors. See variable `vc-annotate-menu-elements' for customizing the
menu items."
(set (make-local-variable 'truncate-lines) t)
(set (make-local-variable 'font-lock-defaults)
'(vc-annotate-font-lock-keywords t))
(view-mode 1))
(defun vc-annotate-display-default (ratio)
"Display the output of \\[vc-annotate] using the default color range.
The color range is given by `vc-annotate-color-map', scaled by RATIO.
The current time is used as the offset."
(interactive (progn (kill-local-variable 'vc-annotate-color-map) '(1.0)))
(message "Redisplaying annotation...")
(vc-annotate-display ratio)
(message "Redisplaying annotation...done"))
(defun vc-annotate-oldest-in-map (color-map)
"Return the oldest time in the COLOR-MAP."
;; Since entries should be sorted, we can just use the last one.
(caar (last color-map)))
(defun vc-annotate-display-autoscale (&optional full)
"Highlight the output of \\[vc-annotate] using an autoscaled color map.
Autoscaling means that the map is scaled from the current time to the
oldest annotation in the buffer, or, with prefix argument FULL, to
cover the range from the oldest annotation to the newest."
(interactive "P")
(let ((newest 0.0)
(oldest 999999.) ;Any CVS users at the founding of Rome?
(current (vc-annotate-convert-time (current-time)))
date)
(message "Redisplaying annotation...")
;; Run through this file and find the oldest and newest dates annotated.
(save-excursion
(goto-char (point-min))
(while (setq date (prog1 (vc-call-backend vc-annotate-backend
'annotate-time)
(forward-line 1)))
(if (> date newest)
(setq newest date))
(if (< date oldest)
(setq oldest date))))
(vc-annotate-display
(/ (- (if full newest current) oldest)
(vc-annotate-oldest-in-map vc-annotate-color-map))
(if full newest))
(message "Redisplaying annotation...done \(%s\)"
(if full
(format "Spanned from %.1f to %.1f days old"
(- current oldest)
(- current newest))
(format "Spanned to %.1f days old" (- current oldest))))))
;; Menu -- Using easymenu.el
(easy-menu-define vc-annotate-mode-menu vc-annotate-mode-map
"VC Annotate Display Menu"
`("VC-Annotate"
["By Color Map Range" (unless (null vc-annotate-display-mode)
(setq vc-annotate-display-mode nil)
(vc-annotate-display-select))
:style toggle :selected (null vc-annotate-display-mode)]
,@(let ((oldest-in-map (vc-annotate-oldest-in-map vc-annotate-color-map)))
(mapcar (lambda (element)
(let ((days (* element oldest-in-map)))
`[,(format "Span %.1f days" days)
(vc-annotate-display-select nil ,days)
:style toggle :selected
(eql vc-annotate-display-mode ,days) ]))
vc-annotate-menu-elements))
["Span ..."
(vc-annotate-display-select
nil (float (string-to-number (read-string "Span how many days? "))))]
"--"
["Span to Oldest"
(unless (eq vc-annotate-display-mode 'scale)
(vc-annotate-display-select nil 'scale))
:style toggle :selected
(eq vc-annotate-display-mode 'scale)]
["Span Oldest->Newest"
(unless (eq vc-annotate-display-mode 'fullscale)
(vc-annotate-display-select nil 'fullscale))
:style toggle :selected
(eq vc-annotate-display-mode 'fullscale)]
"--"
["Annotate previous revision" vc-annotate-prev-version]
["Annotate next revision" vc-annotate-next-version]
["Annotate revision at line" vc-annotate-revision-at-line]
["Annotate revision previous to line" vc-annotate-revision-previous-to-line]
["Annotate latest revision" vc-annotate-workfile-version]
["Show log of revision at line" vc-annotate-show-log-revision-at-line]
["Show diff of revision at line" vc-annotate-show-diff-revision-at-line]))
(defun vc-annotate-display-select (&optional buffer mode)
"Highlight the output of \\[vc-annotate].
By default, the current buffer is highlighted, unless overridden by
BUFFER. `vc-annotate-display-mode' specifies the highlighting mode to
use; you may override this using the second optional arg MODE."
(interactive)
(if mode (setq vc-annotate-display-mode mode))
(pop-to-buffer (or buffer (current-buffer)))
(cond ((null vc-annotate-display-mode)
;; The ratio is global, thus relative to the global color-map.
(kill-local-variable 'vc-annotate-color-map)
(vc-annotate-display-default (or vc-annotate-ratio 1.0)))
;; One of the auto-scaling modes
((eq vc-annotate-display-mode 'scale)
(vc-annotate-display-autoscale))
((eq vc-annotate-display-mode 'fullscale)
(vc-annotate-display-autoscale t))
((numberp vc-annotate-display-mode) ; A fixed number of days lookback
(vc-annotate-display-default
(/ vc-annotate-display-mode
(vc-annotate-oldest-in-map vc-annotate-color-map))))
(t (error "No such display mode: %s"
vc-annotate-display-mode))))
;;;###autoload
(defun vc-annotate (file rev &optional display-mode buf)
"Display the edit history of the current file using colors.
This command creates a buffer that shows, for each line of the current
file, when it was last edited and by whom. Additionally, colors are
used to show the age of each line--blue means oldest, red means
youngest, and intermediate colors indicate intermediate ages. By
default, the time scale stretches back one year into the past;
everything that is older than that is shown in blue.
With a prefix argument, this command asks two questions in the
minibuffer. First, you may enter a version number; then the buffer
displays and annotates that version instead of the current version
\(type RET in the minibuffer to leave that default unchanged). Then,
you are prompted for the time span in days which the color range
should cover. For example, a time span of 20 days means that changes
over the past 20 days are shown in red to blue, according to their
age, and everything that is older than that is shown in blue.
Customization variables:
`vc-annotate-menu-elements' customizes the menu elements of the
mode-specific menu. `vc-annotate-color-map' and
`vc-annotate-very-old-color' defines the mapping of time to
colors. `vc-annotate-background' specifies the background color."
(interactive
(save-current-buffer
(vc-ensure-vc-buffer)
(list buffer-file-name
(let ((def (vc-workfile-version buffer-file-name)))
(if (null current-prefix-arg) def
(read-string
(format "Annotate from version (default %s): " def)
nil nil def)))
(if (null current-prefix-arg)
vc-annotate-display-mode
(float (string-to-number
(read-string "Annotate span days (default 20): "
nil nil "20")))))))
(vc-ensure-vc-buffer)
(setq vc-annotate-display-mode display-mode) ;Not sure why. --Stef
(let* ((temp-buffer-name (format "*Annotate %s (rev %s)*" (buffer-name) rev))
(temp-buffer-show-function 'vc-annotate-display-select)
;; If BUF is specified, we presume the caller maintains current line,
;; so we don't need to do it here. This implementation may give
;; strange results occasionally in the case of REV != WORKFILE-REV.
(current-line (unless buf (line-number-at-pos))))
(message "Annotating...")
;; If BUF is specified it tells in which buffer we should put the
;; annotations. This is used when switching annotations to another
;; revision, so we should update the buffer's name.
(if buf (with-current-buffer buf
(rename-buffer temp-buffer-name t)
;; In case it had to be uniquified.
(setq temp-buffer-name (buffer-name))))
(with-output-to-temp-buffer temp-buffer-name
(vc-call annotate-command file (get-buffer temp-buffer-name) rev)
;; we must setup the mode first, and then set our local
;; variables before the show-function is called at the exit of
;; with-output-to-temp-buffer
(with-current-buffer temp-buffer-name
(if (not (equal major-mode 'vc-annotate-mode))
(vc-annotate-mode))
(set (make-local-variable 'vc-annotate-backend) (vc-backend file))
(set (make-local-variable 'vc-annotate-parent-file) file)
(set (make-local-variable 'vc-annotate-parent-rev) rev)
(set (make-local-variable 'vc-annotate-parent-display-mode)
display-mode)))
(when current-line
(goto-line current-line temp-buffer-name))
(message "Annotating... done")))
(defun vc-annotate-prev-version (prefix)
"Visit the annotation of the version previous to this one.
With a numeric prefix argument, annotate the version that many
versions previous."
(interactive "p")
(vc-annotate-warp-version (- 0 prefix)))
(defun vc-annotate-next-version (prefix)
"Visit the annotation of the version after this one.
With a numeric prefix argument, annotate the version that many
versions after."
(interactive "p")
(vc-annotate-warp-version prefix))
(defun vc-annotate-workfile-version ()
"Visit the annotation of the focus version of this file."
(interactive)
(if (not (equal major-mode 'vc-annotate-mode))
(message "Cannot be invoked outside of a vc annotate buffer")
(let ((warp-rev (vc-workfile-version vc-annotate-parent-file)))
(if (equal warp-rev vc-annotate-parent-rev)
(message "Already at version %s" warp-rev)
(vc-annotate-warp-version warp-rev)))))
(defun vc-annotate-extract-revision-at-line ()
"Extract the revision number of the current line."
;; This function must be invoked from a buffer in vc-annotate-mode
(vc-call-backend vc-annotate-backend 'annotate-extract-revision-at-line))
(defun vc-annotate-revision-at-line ()
"Visit the annotation of the version identified in the current line."
(interactive)
(if (not (equal major-mode 'vc-annotate-mode))
(message "Cannot be invoked outside of a vc annotate buffer")
(let ((rev-at-line (vc-annotate-extract-revision-at-line)))
(if (not rev-at-line)
(message "Cannot extract revision number from the current line")
(if (equal rev-at-line vc-annotate-parent-rev)
(message "Already at version %s" rev-at-line)
(vc-annotate-warp-version rev-at-line))))))
(defun vc-annotate-revision-previous-to-line ()
"Visit the annotation of the version before the version at line."
(interactive)
(if (not (equal major-mode 'vc-annotate-mode))
(message "Cannot be invoked outside of a vc annotate buffer")
(let ((rev-at-line (vc-annotate-extract-revision-at-line))
(prev-rev nil))
(if (not rev-at-line)
(message "Cannot extract revision number from the current line")
(setq prev-rev
(vc-call previous-version vc-annotate-parent-file rev-at-line))
(vc-annotate-warp-version prev-rev)))))
(defun vc-annotate-show-log-revision-at-line ()
"Visit the log of the version at line."
(interactive)
(if (not (equal major-mode 'vc-annotate-mode))
(message "Cannot be invoked outside of a vc annotate buffer")
(let ((rev-at-line (vc-annotate-extract-revision-at-line)))
(if (not rev-at-line)
(message "Cannot extract revision number from the current line")
(vc-print-log rev-at-line)))))
(defun vc-annotate-show-diff-revision-at-line ()
"Visit the diff of the version at line from its previous version."
(interactive)
(if (not (equal major-mode 'vc-annotate-mode))
(message "Cannot be invoked outside of a vc annotate buffer")
(let ((rev-at-line (vc-annotate-extract-revision-at-line))
(prev-rev nil))
(if (not rev-at-line)
(message "Cannot extract revision number from the current line")
(setq prev-rev
(vc-call previous-version vc-annotate-parent-file rev-at-line))
(if (not prev-rev)
(message "Cannot diff from any version prior to %s" rev-at-line)
(save-window-excursion
(vc-diff-internal
(vc-backend vc-annotate-parent-file)
nil
(list vc-annotate-parent-file)
prev-rev rev-at-line))
(switch-to-buffer "*vc-diff*"))))))
(defun vc-annotate-warp-version (revspec)
"Annotate the version described by REVSPEC.
If REVSPEC is a positive integer, warp that many versions
forward, if possible, otherwise echo a warning message. If
REVSPEC is a negative integer, warp that many versions backward,
if possible, otherwise echo a warning message. If REVSPEC is a
string, then it describes a revision number, so warp to that
revision."
(if (not (equal major-mode 'vc-annotate-mode))
(message "Cannot be invoked outside of a vc annotate buffer")
(let* ((buf (current-buffer))
(oldline (line-number-at-pos))
(revspeccopy revspec)
(newrev nil))
(cond
((and (integerp revspec) (> revspec 0))
(setq newrev vc-annotate-parent-rev)
(while (and (> revspec 0) newrev)
(setq newrev (vc-call next-version
vc-annotate-parent-file newrev))
(setq revspec (1- revspec)))
(if (not newrev)
(message "Cannot increment %d versions from version %s"
revspeccopy vc-annotate-parent-rev)))
((and (integerp revspec) (< revspec 0))
(setq newrev vc-annotate-parent-rev)
(while (and (< revspec 0) newrev)
(setq newrev (vc-call previous-version
vc-annotate-parent-file newrev))
(setq revspec (1+ revspec)))
(if (not newrev)
(message "Cannot decrement %d versions from version %s"
(- 0 revspeccopy) vc-annotate-parent-rev)))
((stringp revspec) (setq newrev revspec))
(t (error "Invalid argument to vc-annotate-warp-version")))
(when newrev
(vc-annotate vc-annotate-parent-file newrev
vc-annotate-parent-display-mode
buf)
(goto-line (min oldline (progn (goto-char (point-max))
(previous-line)
(line-number-at-pos))) buf)))))
(defun vc-annotate-compcar (threshold a-list)
"Test successive cons cells of A-LIST against THRESHOLD.
Return the first cons cell with a car that is not less than THRESHOLD,
nil if no such cell exists."
(let ((i 1)
(tmp-cons (car a-list)))
(while (and tmp-cons (< (car tmp-cons) threshold))
(setq tmp-cons (car (nthcdr i a-list)))
(setq i (+ i 1)))
tmp-cons)) ; Return the appropriate value
(defun vc-annotate-convert-time (time)
"Convert a time value to a floating-point number of days.
The argument TIME is a list as returned by `current-time' or
`encode-time', only the first two elements of that list are considered."
(/ (+ (* (float (car time)) (lsh 1 16)) (cadr time)) 24 3600))
(defun vc-annotate-difference (&optional offset)
"Return the time span in days to the next annotation.
This calls the backend function annotate-time, and returns the
difference in days between the time returned and the current time,
or OFFSET if present."
(let ((next-time (vc-call-backend vc-annotate-backend 'annotate-time)))
(if next-time
(- (or offset
(vc-call-backend vc-annotate-backend 'annotate-current-time))
next-time))))
(defun vc-default-annotate-current-time (backend)
"Return the current time, encoded as fractional days."
(vc-annotate-convert-time (current-time)))
(defvar vc-annotate-offset nil)
(defun vc-annotate-display (ratio &optional offset)
"Highlight `vc-annotate' output in the current buffer.
RATIO, is the expansion that should be applied to `vc-annotate-color-map'.
The annotations are relative to the current time, unless overridden by OFFSET."
(if (/= ratio 1.0)
(set (make-local-variable 'vc-annotate-color-map)
(mapcar (lambda (elem) (cons (* (car elem) ratio) (cdr elem)))
vc-annotate-color-map)))
(set (make-local-variable 'vc-annotate-offset) offset)
(font-lock-mode 1))
(defun vc-annotate-lines (limit)
(let (difference)
(while (and (< (point) limit)
(setq difference (vc-annotate-difference vc-annotate-offset)))
(let* ((color (or (vc-annotate-compcar difference vc-annotate-color-map)
(cons nil vc-annotate-very-old-color)))
;; substring from index 1 to remove any leading `#' in the name
(face-name (concat "vc-annotate-face-"
(if (string-equal
(substring (cdr color) 0 1) "#")
(substring (cdr color) 1)
(cdr color))))
;; Make the face if not done.
(face (or (intern-soft face-name)
(let ((tmp-face (make-face (intern face-name))))
(set-face-foreground tmp-face (cdr color))
(if vc-annotate-background
(set-face-background tmp-face
vc-annotate-background))
tmp-face))) ; Return the face
(point (point)))
(forward-line 1)
(put-text-property point (point) 'face face)))
;; Pretend to font-lock there were no matches.
nil))
\f
;; Set up key bindings for use while editing log messages
(defun vc-log-edit (fileset)
"Set up `log-edit' for use with VC on FILE."
(setq default-directory
(with-current-buffer vc-parent-buffer default-directory))
(log-edit 'vc-finish-logentry nil `(lambda () ',fileset))
(set (make-local-variable 'vc-log-fileset) fileset)
(make-local-variable 'vc-log-version)
(set-buffer-modified-p nil)
(setq buffer-file-name nil))
;; These things should probably be generally available
(defun vc-file-tree-walk (dirname func &rest args)
"Walk recursively through DIRNAME.
Invoke FUNC f ARGS on each VC-managed file f underneath it."
(vc-file-tree-walk-internal (expand-file-name dirname) func args)
(message "Traversing directory %s...done" dirname))
(defun vc-file-tree-walk-internal (file func args)
(if (not (file-directory-p file))
(if (vc-backend file) (apply func file args))
(message "Traversing directory %s..." (abbreviate-file-name file))
(let ((dir (file-name-as-directory file)))
(mapcar
(lambda (f) (or
(string-equal f ".")
(string-equal f "..")
(member f vc-directory-exclusion-list)
(let ((dirf (expand-file-name f dir)))
(or
(file-symlink-p dirf);; Avoid possible loops
(vc-file-tree-walk-internal dirf func args)))))
(directory-files dir)))))
(provide 'vc)
;; DEVELOPER'S NOTES ON CONCURRENCY PROBLEMS IN THIS CODE
;;
;; These may be useful to anyone who has to debug or extend the package.
;; (Note that this information corresponds to versions 5.x. Some of it
;; might have been invalidated by the additions to support branching
;; and RCS keyword lookup. AS, 1995/03/24)
;;
;; A fundamental problem in VC is that there are time windows between
;; vc-next-action's computations of the file's version-control state and
;; the actions that change it. This is a window open to lossage in a
;; multi-user environment; someone else could nip in and change the state
;; of the master during it.
;;
;; The performance problem is that rlog/prs calls are very expensive; we want
;; to avoid them as much as possible.
;;
;; ANALYSIS:
;;
;; The performance problem, it turns out, simplifies in practice to the
;; problem of making vc-state fast. The two other functions that call
;; prs/rlog will not be so commonly used that the slowdown is a problem; one
;; makes snapshots, the other deletes the calling user's last change in the
;; master.
;;
;; The race condition implies that we have to either (a) lock the master
;; during the entire execution of vc-next-action, or (b) detect and
;; recover from errors resulting from dispatch on an out-of-date state.
;;
;; Alternative (a) appears to be infeasible. The problem is that we can't
;; guarantee that the lock will ever be removed. Suppose a user starts a
;; checkin, the change message buffer pops up, and the user, having wandered
;; off to do something else, simply forgets about it?
;;
;; Alternative (b), on the other hand, works well with a cheap way to speed up
;; vc-state. Usually, if a file is registered, we can read its locked/
;; unlocked state and its current owner from its permissions.
;;
;; This shortcut will fail if someone has manually changed the focus's
;; permissions; also if developers are munging the focus in several
;; directories, with symlinks to a master (in this latter case, the
;; permissions shortcut will fail to detect a lock asserted from another
;; directory).
;;
;; Note that these cases correspond exactly to the errors which could happen
;; because of a competing checkin/checkout race in between two instances of
;; vc-next-action.
;;
;; For VC's purposes, a focus/master pair may have the following states:
;;
;; A. Unregistered. There is a focus, there is no master.
;;
;; B. Registered and not locked by anyone.
;;
;; C. Locked by calling user and unchanged.
;;
;; D. Locked by the calling user and changed.
;;
;; E. Locked by someone other than the calling user.
;;
;; This makes for 25 states and 20 error conditions. Here's the matrix:
;;
;; VC's idea of state
;; |
;; V Actual state RCS action SCCS action Effect
;; A B C D E
;; A . 1 2 3 4 ci -u -t- admin -fb -i<file> initial admin
;; B 5 . 6 7 8 co -l get -e checkout
;; C 9 10 . 11 12 co -u unget; get revert
;; D 13 14 15 . 16 ci -u -m<comment> delta -y<comment>; get checkin
;; E 17 18 19 20 . rcs -u -M -l unget -n ; get -g steal lock
;;
;; All commands take the master file name as a last argument (not shown).
;;
;; In the discussion below, a "self-race" is a pathological situation in
;; which VC operations are being attempted simultaneously by two or more
;; Emacsen running under the same username.
;;
;; The vc-next-action code has the following windows:
;;
;; Window P:
;; Between the check for existence of a master file and the call to
;; admin/checkin in vc-buffer-admin (apparent state A). This window may
;; never close if the initial-comment feature is on.
;;
;; Window Q:
;; Between the call to vc-workfile-unchanged-p in and the immediately
;; following revert (apparent state C).
;;
;; Window R:
;; Between the call to vc-workfile-unchanged-p in and the following
;; checkin (apparent state D). This window may never close.
;;
;; Window S:
;; Between the unlock and the immediately following checkout during a
;; revert operation (apparent state C). Included in window Q.
;;
;; Window T:
;; Between vc-state and the following checkout (apparent state B).
;;
;; Window U:
;; Between vc-state and the following revert (apparent state C).
;; Includes windows Q and S.
;;
;; Window V:
;; Between vc-state and the following checkin (apparent state
;; D). This window may never be closed if the user fails to complete the
;; checkin message. Includes window R.
;;
;; Window W:
;; Between vc-state and the following steal-lock (apparent
;; state E). This window may never close if the user fails to complete
;; the steal-lock message. Includes window X.
;;
;; Window X:
;; Between the unlock and the immediately following re-lock during a
;; steal-lock operation (apparent state E). This window may never close
;; if the user fails to complete the steal-lock message.
;;
;; Errors:
;;
;; Apparent state A ---
;;
;; 1. File looked unregistered but is actually registered and not locked.
;;
;; Potential cause: someone else's admin during window P, with
;; caller's admin happening before their checkout.
;;
;; RCS: Prior to version 5.6.4, ci fails with message
;; "no lock set by <user>". From 5.6.4 onwards, VC uses the new
;; ci -i option and the message is "<file>,v: already exists".
;; SCCS: admin will fail with error (ad19).
;;
;; We can let these errors be passed up to the user.
;;
;; 2. File looked unregistered but is actually locked by caller, unchanged.
;;
;; Potential cause: self-race during window P.
;;
;; RCS: Prior to version 5.6.4, reverts the file to the last saved
;; version and unlocks it. From 5.6.4 onwards, VC uses the new
;; ci -i option, failing with message "<file>,v: already exists".
;; SCCS: will fail with error (ad19).
;;
;; Either of these consequences is acceptable.
;;
;; 3. File looked unregistered but is actually locked by caller, changed.
;;
;; Potential cause: self-race during window P.
;;
;; RCS: Prior to version 5.6.4, VC registers the caller's focus as
;; a delta with a null change comment (the -t- switch will be
;; ignored). From 5.6.4 onwards, VC uses the new ci -i option,
;; failing with message "<file>,v: already exists".
;; SCCS: will fail with error (ad19).
;;
;; 4. File looked unregistered but is locked by someone else.
;;;
;; Potential cause: someone else's admin during window P, with
;; caller's admin happening *after* their checkout.
;;
;; RCS: Prior to version 5.6.4, ci fails with a
;; "no lock set by <user>" message. From 5.6.4 onwards,
;; VC uses the new ci -i option, failing with message
;; "<file>,v: already exists".
;; SCCS: will fail with error (ad19).
;;
;; We can let these errors be passed up to the user.
;;
;; Apparent state B ---
;;
;; 5. File looked registered and not locked, but is actually unregistered.
;;
;; Potential cause: master file got nuked during window P.
;;
;; RCS: will fail with "RCS/<file>: No such file or directory"
;; SCCS: will fail with error ut4.
;;
;; We can let these errors be passed up to the user.
;;
;; 6. File looked registered and not locked, but is actually locked by the
;; calling user and unchanged.
;;
;; Potential cause: self-race during window T.
;;
;; RCS: in the same directory as the previous focus, co -l will fail
;; with "co error: writable foo exists; checkout aborted". In any other
;; directory, checkout will succeed.
;; SCCS: will fail with ge17.
;;
;; Either of these consequences is acceptable.
;;
;; 7. File looked registered and not locked, but is actually locked by the
;; calling user and changed.
;;
;; As case 6.
;;
;; 8. File looked registered and not locked, but is actually locked by another
;; user.
;;
;; Potential cause: someone else checks it out during window T.
;;
;; RCS: co error: revision 1.3 already locked by <user>
;; SCCS: fails with ge4 (in directory) or ut7 (outside it).
;;
;; We can let these errors be passed up to the user.
;;
;; Apparent state C ---
;;
;; 9. File looks locked by calling user and unchanged, but is unregistered.
;;
;; As case 5.
;;
;; 10. File looks locked by calling user and unchanged, but is actually not
;; locked.
;;
;; Potential cause: a self-race in window U, or by the revert's
;; landing during window X of some other user's steal-lock or window S
;; of another user's revert.
;;
;; RCS: succeeds, refreshing the file from the identical version in
;; the master.
;; SCCS: fails with error ut4 (p file nonexistent).
;;
;; Either of these consequences is acceptable.
;;
;; 11. File is locked by calling user. It looks unchanged, but is actually
;; changed.
;;
;; Potential cause: the file would have to be touched by a self-race
;; during window Q.
;;
;; The revert will succeed, removing whatever changes came with
;; the touch. It is theoretically possible that work could be lost.
;;
;; 12. File looks like it's locked by the calling user and unchanged, but
;; it's actually locked by someone else.
;;
;; Potential cause: a steal-lock in window V.
;;
;; RCS: co error: revision <rev> locked by <user>; use co -r or rcs -u
;; SCCS: fails with error un2
;;
;; We can pass these errors up to the user.
;;
;; Apparent state D ---
;;
;; 13. File looks like it's locked by the calling user and changed, but it's
;; actually unregistered.
;;
;; Potential cause: master file got nuked during window P.
;;
;; RCS: Prior to version 5.6.4, checks in the user's version as an
;; initial delta. From 5.6.4 onwards, VC uses the new ci -j
;; option, failing with message "no such file or directory".
;; SCCS: will fail with error ut4.
;;
;; This case is kind of nasty. Under RCS prior to version 5.6.4,
;; VC may fail to detect the loss of previous version information.
;;
;; 14. File looks like it's locked by the calling user and changed, but it's
;; actually unlocked.
;;
;; Potential cause: self-race in window V, or the checkin happening
;; during the window X of someone else's steal-lock or window S of
;; someone else's revert.
;;
;; RCS: ci will fail with "no lock set by <user>".
;; SCCS: delta will fail with error ut4.
;;
;; 15. File looks like it's locked by the calling user and changed, but it's
;; actually locked by the calling user and unchanged.
;;
;; Potential cause: another self-race --- a whole checkin/checkout
;; sequence by the calling user would have to land in window R.
;;
;; SCCS: checks in a redundant delta and leaves the file unlocked as usual.
;; RCS: reverts to the file state as of the second user's checkin, leaving
;; the file unlocked.
;;
;; It is theoretically possible that work could be lost under RCS.
;;
;; 16. File looks like it's locked by the calling user and changed, but it's
;; actually locked by a different user.
;;
;; RCS: ci error: no lock set by <user>
;; SCCS: unget will fail with error un2
;;
;; We can pass these errors up to the user.
;;
;; Apparent state E ---
;;
;; 17. File looks like it's locked by some other user, but it's actually
;; unregistered.
;;
;; As case 13.
;;
;; 18. File looks like it's locked by some other user, but it's actually
;; unlocked.
;;
;; Potential cause: someone released a lock during window W.
;;
;; RCS: The calling user will get the lock on the file.
;; SCCS: unget -n will fail with cm4.
;;
;; Either of these consequences will be OK.
;;
;; 19. File looks like it's locked by some other user, but it's actually
;; locked by the calling user and unchanged.
;;
;; Potential cause: the other user relinquishing a lock followed by
;; a self-race, both in window W.
;;
;; Under both RCS and SCCS, both unlock and lock will succeed, making
;; the sequence a no-op.
;;
;; 20. File looks like it's locked by some other user, but it's actually
;; locked by the calling user and changed.
;;
;; As case 19.
;;
;; PROBLEM CASES:
;;
;; In order of decreasing severity:
;;
;; Cases 11 and 15 are the only ones that potentially lose work.
;; They would require a self-race for this to happen.
;;
;; Case 13 in RCS loses information about previous deltas, retaining
;; only the information in the current focus. This can only happen
;; if the master file gets nuked in window P.
;;
;; Case 3 in RCS and case 15 under SCCS insert a redundant delta with
;; no change comment in the master. This would require a self-race in
;; window P or R respectively.
;;
;; Cases 2, 10, 19 and 20 do extra work, but make no changes.
;;
;; Unfortunately, it appears to me that no recovery is possible in these
;; cases. They don't yield error messages, so there's no way to tell that
;; a race condition has occurred.
;;
;; All other cases don't change either the focus or the master, and
;; trigger command errors which the user will see.
;;
;; Thus, there is no explicit recovery code.
;; arch-tag: ca82c1de-3091-4e26-af92-460abc6213a6
;;; vc.el ends here
[-- Attachment #3: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: New VC mode -- review request
2007-10-03 10:35 New VC mode -- review request Eric S. Raymond
@ 2007-10-03 14:31 ` Dan Nicolaescu
2007-10-03 17:00 ` Eric S. Raymond
` (2 more replies)
2007-10-04 2:02 ` Richard Stallman
1 sibling, 3 replies; 20+ messages in thread
From: Dan Nicolaescu @ 2007-10-03 14:31 UTC (permalink / raw)
To: esr; +Cc: emacs-devel
"Eric S. Raymond" <esr@thyrsus.com> writes:
> I am the original author of the VC mode shipped with Emacs, back in 1992-1993.
> Its design was well matched to the file-oriented version-control systems
> (VCSes) of its day, and it has proven a useful tool. But it has long been in
> need of a rewrite, for two reasons:
>
> (1) The code has accreted cruft over the years, and
>
> (2) the design is poorly matched to modern changeset-oriented VCSes,
> beginning with Subversion and including third-generation systems such
> as Mercurial and Bazaar.
Thank you for working doing this, such features are sorely needed now.
> Now I think it has come time for the front end to be merged. I have
> been using it in my everyday development work with Subversion for months.
> Stefan asked me to submit it to this list for final review, and I am
> doing so. Please find it attached.
The vc.el file in CVS trunk has changed since your last commit, some
new features have been added, bugs have been fixed. Could you please
merge your changes with the top of the trunk?
> Here are the user-visible changes you should expect relative to what's
> in the manual:
>
> * The following commands now operate on filesets rather than files.
>
> vc-next-action = C-x v v
> vc-diff = C-x v =
> vc-print-log = C-x v l
> vc-revert = C-x v u
This does not seem to work for me from vc-dired. I have 2 changed
files in a Mercurial. After marking both of them in vc-dired and
pressing
v u
I get this error "Please kill or save all modified buffers before
reverting".
None of the files is in an emacs buffer.
> vc-rollback = C-x v c
Do you have an implementation for this function for any backend? It
would be interesting to see it.
> Changes other than these are probably bugs and you should report them.
You introduced "focus version". This looks like a new term, could we
use something that is already in use in at least one version control
system?
> You need not restrict criticism to outright bugs; the user interface hasn't
> been reviewed or refreshed in a very long time before this, and it is
> possible we could be doing things more gracefully.
You have moved functions around in the file. This makes doing a diff
between the top of the trunk and your version harder than it needs to
be. Could you please restore the function order (at least for review
purposes) and repost?
In vc-deduce-fileset:
This:
(let ((regexp (dired-marker-regexp))
(marked '()))
(save-excursion
(goto-char (point-min))
(while (re-search-forward regexp nil t)
(if (setq filename (dired-get-filename nil t))
(setq marked (append marked (list filename))))))
Can be replaced with this:
(dired-map-over-marks (dired-get-filename) nil))
Also:
((and vc-parent-buffer (buffer-file-name vc-parent-buffer))
(progn
(if vc-dired-mode
^^^^^^^^^^^^^^
Can this ever be true, there's a previous
vc-dired-mode clause in the `cond'...
This code in vc-dired-hook:
;; ordinary file
((and (vc-backend filename)
(not (and vc-dired-terse-mode
(vc-up-to-date-p filename))))
(vc-dired-reformat-line (vc-call dired-state-info filename))
(forward-line 1))
Is the vc-backend call necessary? It ends up calling vc-registered and
that can be expensive for the backends that run a program to determine
the registered state. The -dir-state method computes the state for
most (all?) files...
I don't understand this code very well, but if it can be simplified,
it might result in a significant speedup for vc-dired.
It seems that you want to keep vc-dired. IMHO vc-dired is not very
good because
- it is slow because of running too many vc commands to find out the
status for each file.
- it does not show non-registered files, so one can't select them and
register them
- most of the dired commands are not useful in the VC context, they
are just clutter...
- and interface like PCL-CVS, psvn.el or git.el seems that is targeted only
for version control seems better.
But this is not necessarily related to your changes and should not
preclude you from checking in.
Do you have any plans for updating the branch infrastructure?
VC now uses the term "snapshot" for branches, most people have no idea
what that means...
Also for people that have not used RCS "locked" is not a familiar
term, would it be possible to minimize it's use?
I hope this helps.
Thanks!
--dan
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: New VC mode -- review request
2007-10-03 14:31 ` Dan Nicolaescu
@ 2007-10-03 17:00 ` Eric S. Raymond
2007-10-04 0:42 ` Dan Nicolaescu
2007-10-04 7:18 ` Thien-Thi Nguyen
2007-10-03 21:32 ` Alexandru Harsanyi
2007-10-04 20:32 ` David Kastrup
2 siblings, 2 replies; 20+ messages in thread
From: Eric S. Raymond @ 2007-10-03 17:00 UTC (permalink / raw)
To: Dan Nicolaescu; +Cc: emacs-devel
Dan Nicolaescu <dann@ics.uci.edu>:
> The vc.el file in CVS trunk has changed since your last commit, some
> new features have been added, bugs have been fixed. Could you please
> merge your changes with the top of the trunk?
I'll do that. I should get to it today.
> > Here are the user-visible changes you should expect relative to what's
> > in the manual:
> >
> > * The following commands now operate on filesets rather than files.
> >
> > vc-next-action = C-x v v
> > vc-diff = C-x v =
> > vc-print-log = C-x v l
> > vc-revert = C-x v u
>
> This does not seem to work for me from vc-dired. I have 2 changed
> files in a Mercurial. After marking both of them in vc-dired and
> pressing
> v u
> I get this error "Please kill or save all modified buffers before
> reverting".
> None of the files is in an emacs buffer.
Hm. I wonder if this is a problem with the hg back end -- I haven't
tested that. Can you duplicate this behavior with any other back end?
I'll stare at the code around that error message for a bit when I do
the merge with top of trunk.
> > vc-rollback = C-x v c
>
> Do you have an implementation for this function for any backend? It
> would be interesting to see it.
There is one for SCCS in old VC if you want to look at it. I think I
at one point implemented it for one other backend, but the code and
concept were so dodgy that I decided it was best shot through the
head.
Sorry, I don't remember which other back end I implemented it for. I
do know that most VCSes cannot support this operation at all, it's
really an SCCSism that got baked into old VC's design by historical
accident.
> > Changes other than these are probably bugs and you should report them.
>
> You introduced "focus version". This looks like a new term, could we
> use something that is already in use in at least one version control
> system?
I invented a new one because existing VCSs actually get along without
an unambiguous term for this, instead using various circumlocutions or
referring to it implicitly.
Where applicable, I have tended to prefer terminology from Subversion,
as it has the largest userbase of any VCS with changeset capability;
if Subversion had a good term for it, I'd use it.
> You have moved functions around in the file. This makes doing a diff
> between the top of the trunk and your version harder than it needs to
> be. Could you please restore the function order (at least for review
> purposes) and repost?
Obviously you think this would help you understand the changes better,
but I don't believe that. Supposing I reordered it, I believe the
diff would still be sufficiently large and noisy to be useless. Even
if it were not, the thought of (in effect) having to maintain two
versions of the code with different function ordering frightens me to
the bottom of my shoes. So...I'm afraid the answer is "no". I'd
like to be cooperative, but I believe this effort would be wasted.
> In vc-deduce-fileset:
> This:
> (let ((regexp (dired-marker-regexp))
> (marked '()))
> (save-excursion
> (goto-char (point-min))
> (while (re-search-forward regexp nil t)
> (if (setq filename (dired-get-filename nil t))
> (setq marked (append marked (list filename))))))
>
> Can be replaced with this:
> (dired-map-over-marks (dired-get-filename) nil))
Yes, that seems likely. I will test this, thanks.
> Also:
> ((and vc-parent-buffer (buffer-file-name vc-parent-buffer))
> (progn
> (if vc-dired-mode
> ^^^^^^^^^^^^^^
> Can this ever be true, there's a previous
> vc-dired-mode clause in the `cond'...
Good point. That code is a fossil remnant from a previous organization
of vc-deduce-fileset. Removed.
> This code in vc-dired-hook:
>
> ;; ordinary file
> ((and (vc-backend filename)
> (not (and vc-dired-terse-mode
> (vc-up-to-date-p filename))))
> (vc-dired-reformat-line (vc-call dired-state-info filename))
> (forward-line 1))
>
> Is the vc-backend call necessary? It ends up calling vc-registered and
> that can be expensive for the backends that run a program to determine
> the registered state. The -dir-state method computes the state for
> most (all?) files...
> I don't understand this code very well, but if it can be simplified,
> it might result in a significant speedup for vc-dired.
You're right, it might. I'm not going to change this immediately, it will take
a little thought and testing, but it's going on my to-do list.
(Note to other reviewers: please do not consider performance issues
*in new features* a blocker against merging new VC. What we're trying
to verify here is that new VC doesn't cause functional regressions
with respect to the single-file operations of old VC. Performance
and UI tuning of the fileset-oriented features can come afterwards.)
> It seems that you want to keep vc-dired. IMHO vc-dired is not very
> good because
> - it is slow because of running too many vc commands to find out the
> status for each file.
> - it does not show non-registered files, so one can't select them and
> register them
> - most of the dired commands are not useful in the VC context, they
> are just clutter...
> - and interface like PCL-CVS, psvn.el or git.el seems that is targeted only
> for version control seems better.
You may be right. But current new VC is deliberately conservative in
design -- I have tried to change the UI as little as is consistent
with supporting changesets.
This rewrite is all about making sure the changeset-aware
infrastructure is in place. I believe it's important to stick to
doing one new thing at once; after merge will the time to experimwnt
with a revamped UI on a solid functional foundation.
> But this is not necessarily related to your changes and should not
> preclude you from checking in.
Agreed.
> Do you have any plans for updating the branch infrastructure?
> VC now uses the term "snapshot" for branches, most people have no idea
> what that means...
Agreed. But worrying about this is for after the merge.
> Also for people that have not used RCS "locked" is not a familiar
> term, would it be possible to minimize it's use?
I'll do a pass over the documentation strings this afternoon with
this in mind. But, again, this is really an issue for after
the merge.
> I hope this helps.
Yes, it does.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: New VC mode -- review request
2007-10-03 14:31 ` Dan Nicolaescu
2007-10-03 17:00 ` Eric S. Raymond
@ 2007-10-03 21:32 ` Alexandru Harsanyi
2007-10-04 2:24 ` Dan Nicolaescu
2007-10-04 17:27 ` Richard Stallman
2007-10-04 20:32 ` David Kastrup
2 siblings, 2 replies; 20+ messages in thread
From: Alexandru Harsanyi @ 2007-10-03 21:32 UTC (permalink / raw)
To: Emacs Devel
On 3 Oct 2007, at 10:31 PM, Dan Nicolaescu wrote:
>
>> vc-rollback = C-x v c
>
> Do you have an implementation for this function for any backend? It
> would be interesting to see it.
>
The ClearCase backend implements it. See http://vc-
clearcase.sourceforge.net
Cheers,
Alex.
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: New VC mode -- review request
2007-10-03 17:00 ` Eric S. Raymond
@ 2007-10-04 0:42 ` Dan Nicolaescu
2007-10-04 2:02 ` Eric S. Raymond
2007-10-04 7:18 ` Thien-Thi Nguyen
1 sibling, 1 reply; 20+ messages in thread
From: Dan Nicolaescu @ 2007-10-04 0:42 UTC (permalink / raw)
To: esr; +Cc: emacs-devel
"Eric S. Raymond" <esr@thyrsus.com> writes:
> Dan Nicolaescu <dann@ics.uci.edu>:
> > > Here are the user-visible changes you should expect relative to what's
> > > in the manual:
> > >
> > > * The following commands now operate on filesets rather than files.
> > >
> > > vc-next-action = C-x v v
> > > vc-diff = C-x v =
> > > vc-print-log = C-x v l
> > > vc-revert = C-x v u
> >
> > This does not seem to work for me from vc-dired. I have 2 changed
> > files in a Mercurial. After marking both of them in vc-dired and
> > pressing
> > v u
> > I get this error "Please kill or save all modified buffers before
> > reverting".
> > None of the files is in an emacs buffer.
>
> Hm. I wonder if this is a problem with the hg back end -- I haven't
> tested that. Can you duplicate this behavior with any other back end?
> I'll stare at the code around that error message for a bit when I do
> the merge with top of trunk.
The same thing happens with RCS.
> > > vc-rollback = C-x v c
> >
> > Do you have an implementation for this function for any backend? It
> > would be interesting to see it.
>
> There is one for SCCS in old VC if you want to look at it. I think I
> at one point implemented it for one other backend, but the code and
> concept were so dodgy that I decided it was best shot through the
> head.
>
> Sorry, I don't remember which other back end I implemented it for. I
> do know that most VCSes cannot support this operation at all, it's
> really an SCCSism that got baked into old VC's design by historical
> accident.
OK, thanks, I was trying to see if it would be interesting to try to
support such on operation on modern VCSes...
> > This code in vc-dired-hook:
> >
> > ;; ordinary file
> > ((and (vc-backend filename)
> > (not (and vc-dired-terse-mode
> > (vc-up-to-date-p filename))))
> > (vc-dired-reformat-line (vc-call dired-state-info filename))
> > (forward-line 1))
> >
> > Is the vc-backend call necessary? It ends up calling vc-registered and
> > that can be expensive for the backends that run a program to determine
> > the registered state. The -dir-state method computes the state for
> > most (all?) files...
> > I don't understand this code very well, but if it can be simplified,
> > it might result in a significant speedup for vc-dired.
>
> You're right, it might. I'm not going to change this immediately, it will take
> a little thought and testing, but it's going on my to-do list.
Note to other reviewers: the code above is not new, so doing this
should not affect getting the fileset changes in.
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: New VC mode -- review request
2007-10-03 10:35 New VC mode -- review request Eric S. Raymond
2007-10-03 14:31 ` Dan Nicolaescu
@ 2007-10-04 2:02 ` Richard Stallman
2007-10-04 2:22 ` Eric S. Raymond
1 sibling, 1 reply; 20+ messages in thread
From: Richard Stallman @ 2007-10-04 2:02 UTC (permalink / raw)
To: esr; +Cc: emacs-devel
Due to a CVS command error on my part, the new back-end code and a
version of the front end with old control behavior but using the new
back ends got checked into CVS HEAD rather than a branch. Fortunately,
the new back-end code functioned without a hitch and Stefan decided
reverting it was not necessary,
Your changes worked, but you didn't give them proper change log
entries. Other people had to write the change log for them.
Before installing these changes, please post the change log for them
here, so we can work on them to make them suitable.
Also, would you please write the changes to the Emacs Manual?
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: New VC mode -- review request
2007-10-04 0:42 ` Dan Nicolaescu
@ 2007-10-04 2:02 ` Eric S. Raymond
2007-10-04 2:14 ` Dan Nicolaescu
0 siblings, 1 reply; 20+ messages in thread
From: Eric S. Raymond @ 2007-10-04 2:02 UTC (permalink / raw)
To: Dan Nicolaescu; +Cc: emacs-devel
Dan Nicolaescu <dann@ics.uci.edu>:
> > Hm. I wonder if this is a problem with the hg back end -- I haven't
> > tested that. Can you duplicate this behavior with any other back end?
> > I'll stare at the code around that error message for a bit when I do
> > the merge with top of trunk.
>
> The same thing happens with RCS.
Very odd. I can't reproduce this. Perhaps I'm not understanding the recipe.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: New VC mode -- review request
2007-10-04 2:02 ` Eric S. Raymond
@ 2007-10-04 2:14 ` Dan Nicolaescu
2007-10-09 14:55 ` Eric S. Raymond
0 siblings, 1 reply; 20+ messages in thread
From: Dan Nicolaescu @ 2007-10-04 2:14 UTC (permalink / raw)
To: esr; +Cc: emacs-devel
"Eric S. Raymond" <esr@thyrsus.com> writes:
> Dan Nicolaescu <dann@ics.uci.edu>:
> > > Hm. I wonder if this is a problem with the hg back end -- I haven't
> > > tested that. Can you duplicate this behavior with any other back end?
> > > I'll stare at the code around that error message for a bit when I do
> > > the merge with top of trunk.
> >
> > The same thing happens with RCS.
>
> Very odd. I can't reproduce this. Perhaps I'm not understanding the recipe.
mkdir /tmp/test
mkdir /tmp/test/RCS
cd /tmp/test
cp ~/.emacs 1.el
cp ~/.emacs 2.el
emacs -q 1.el 2.el
C-x v i C-x v v for each of the 2 files. After that they should be
writable. Quit emacs.
echo foo >> 1.el
echo foo >> 2.el
emacs -q -l vc.el
(where vc.el is your vc.el)
C-x v d /tmp/test RET
Mark the 2 files.
v u
and now that gets an error.
BTW, I just found another issue:
with the same setup as above, do:
cp ~/.emacs /tmp/test/3.el
emacs -q -l vc.el /tmp/test/3.el
C-x v v
fails with: "No fileset is available here."
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: New VC mode -- review request
2007-10-04 2:02 ` Richard Stallman
@ 2007-10-04 2:22 ` Eric S. Raymond
2007-10-05 16:12 ` Richard Stallman
0 siblings, 1 reply; 20+ messages in thread
From: Eric S. Raymond @ 2007-10-04 2:22 UTC (permalink / raw)
To: Richard Stallman; +Cc: emacs-devel
Richard Stallman <rms@gnu.org>:
> Before installing these changes, please post the change log for them
> here, so we can work on them to make them suitable.
I haven't the faintest idea how to do this. Your change-log format is
good for describing small incremental changes at the granularity of
individual functions, but not for major rewrites where abstractions
touch many functions at once. It's not that I'm unwilling to try to
write something useful, I can't imagine how to within this format.
> Also, would you please write the changes to the Emacs Manual?
I've already done that. They're ready to be merged along with the
vc.el code.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: New VC mode -- review request
2007-10-03 21:32 ` Alexandru Harsanyi
@ 2007-10-04 2:24 ` Dan Nicolaescu
2007-10-04 9:46 ` Alexandru Harsanyi
2007-10-04 9:51 ` Eli Zaretskii
2007-10-04 17:27 ` Richard Stallman
1 sibling, 2 replies; 20+ messages in thread
From: Dan Nicolaescu @ 2007-10-04 2:24 UTC (permalink / raw)
To: Emacs Devel
Alexandru Harsanyi <harsanyi@mac.com> writes:
> On 3 Oct 2007, at 10:31 PM, Dan Nicolaescu wrote:
>
> >
> >> vc-rollback = C-x v c
> >
> > Do you have an implementation for this function for any backend? It
> > would be interesting to see it.
> >
>
> The ClearCase backend implements it. See http://vc-
> clearcase.sourceforge.net
Thanks, but unfortunately I don't know much about ClearCase, so I
won't be able to use that code to judge what can other backend do
about this...
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: New VC mode -- review request
2007-10-03 17:00 ` Eric S. Raymond
2007-10-04 0:42 ` Dan Nicolaescu
@ 2007-10-04 7:18 ` Thien-Thi Nguyen
1 sibling, 0 replies; 20+ messages in thread
From: Thien-Thi Nguyen @ 2007-10-04 7:18 UTC (permalink / raw)
To: esr; +Cc: Dan Nicolaescu, emacs-devel
() "Eric S. Raymond" <esr@thyrsus.com>
() Wed, 3 Oct 2007 13:00:48 -0400
Dan Nicolaescu <dann@ics.uci.edu>:
> > vc-rollback = C-x v c
>
> Do you have an implementation for this function for any
> backend? It would be interesting to see it.
There is one for SCCS in old VC if you want to look at it. I
think I at one point implemented it for one other backend, but
the code and concept were so dodgy that I decided it was best
shot through the head.
here is the implementation i use for cvs:
(defun ttn-cvs-cancel-version (file editable)
"Undo the most recent checkin of FILE then do \"cvs update\".
EDITABLE non-nil means do \"cvs edit\" afterwards."
(unless (and (stringp vc-mode)
(string= " CVS-" (substring vc-mode 0 5)))
(error "File locally modified, aborting"))
(let ((rev (substring vc-mode 5)))
(vc-cvs-command nil 0 file "admin" (concat "-o" rev))
(vc-cvs-command nil 0 file "update")
(when editable
(vc-cvs-command nil 0 file "edit"))))
(defun ttn-cvs-rollback (files)
;; Usage: (defalias 'vc-cvs-rollback 'ttn-cvs-rollback)
"Undo the most recent checkin of FILE then do \"cvs update\"."
(ttn-cvs-cancel-version (car files) nil))
although rollback and cancel-version, before that, are shunned, i
find them useful for lone-programmer (ttn-only) situations where
admin/recovery overhead for mistakes is tolerable. i think we
should provide them but continue to urge their avoidance for
shared-repo situations, however. the "we don't provide it because
you shouldn't do that" tone has always bothered me gutterally.
thi
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: New VC mode -- review request
2007-10-04 2:24 ` Dan Nicolaescu
@ 2007-10-04 9:46 ` Alexandru Harsanyi
2007-10-04 9:51 ` Eli Zaretskii
1 sibling, 0 replies; 20+ messages in thread
From: Alexandru Harsanyi @ 2007-10-04 9:46 UTC (permalink / raw)
To: Emacs Devel
On 4 Oct 2007, at 10:24 AM, Dan Nicolaescu wrote:
> Alexandru Harsanyi <harsanyi@mac.com> writes:
>
>> On 3 Oct 2007, at 10:31 PM, Dan Nicolaescu wrote:
>>
>>>
>>>> vc-rollback = C-x v c
>>>
>>> Do you have an implementation for this function for any backend? It
>>> would be interesting to see it.
>>>
>>
>> The ClearCase backend implements it. See http://vc-
>> clearcase.sourceforge.net
>
> Thanks, but unfortunately I don't know much about ClearCase, so I
> won't be able to use that code to judge what can other backend do
> about this...
>
Well, ClearCase supports removing any file revision, so rollback is
implemented by asking ClearCase to remove the current revision.
Maybe rollback can be implemented in a generic way by applying the
reverse patch between the current and previous revisions of the file
and than committing that change. This will not remove any revision
from the repository but will have the effect on the file contents as
a rollback.
Cheers,
Alex.
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: New VC mode -- review request
2007-10-04 2:24 ` Dan Nicolaescu
2007-10-04 9:46 ` Alexandru Harsanyi
@ 2007-10-04 9:51 ` Eli Zaretskii
1 sibling, 0 replies; 20+ messages in thread
From: Eli Zaretskii @ 2007-10-04 9:51 UTC (permalink / raw)
To: Dan Nicolaescu; +Cc: emacs-devel
> From: Dan Nicolaescu <dann@ics.uci.edu>
> Date: Wed, 03 Oct 2007 19:24:30 -0700
>
> Alexandru Harsanyi <harsanyi@mac.com> writes:
>
> > On 3 Oct 2007, at 10:31 PM, Dan Nicolaescu wrote:
> >
> > >
> > >> vc-rollback = C-x v c
> > >
> > > Do you have an implementation for this function for any backend? It
> > > would be interesting to see it.
> > >
> >
> > The ClearCase backend implements it. See http://vc-
> > clearcase.sourceforge.net
>
> Thanks, but unfortunately I don't know much about ClearCase, so I
> won't be able to use that code to judge what can other backend do
> about this...
Look at the doc string of vc-clearcase-cancel-version and the
commentary there: I think it explains what is being done clearly
enough for anyone to understand what is going on.
Btw, I see vc-rcs-rollback in vc-rcs.el, which is another example of
this method.
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: New VC mode -- review request
2007-10-03 21:32 ` Alexandru Harsanyi
2007-10-04 2:24 ` Dan Nicolaescu
@ 2007-10-04 17:27 ` Richard Stallman
1 sibling, 0 replies; 20+ messages in thread
From: Richard Stallman @ 2007-10-04 17:27 UTC (permalink / raw)
To: Alexandru Harsanyi; +Cc: emacs-devel
The ClearCase backend implements it. See http://vc-
clearcase.sourceforge.net
We do not support ClearCase.
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: New VC mode -- review request
2007-10-03 14:31 ` Dan Nicolaescu
2007-10-03 17:00 ` Eric S. Raymond
2007-10-03 21:32 ` Alexandru Harsanyi
@ 2007-10-04 20:32 ` David Kastrup
2 siblings, 0 replies; 20+ messages in thread
From: David Kastrup @ 2007-10-04 20:32 UTC (permalink / raw)
To: Dan Nicolaescu; +Cc: esr, emacs-devel
Dan Nicolaescu <dann@ics.uci.edu> writes:
> > vc-rollback = C-x v c
>
> Do you have an implementation for this function for any backend? It
> would be interesting to see it.
Well, git certainly would qualify for rolling backward, sideways and
over. It has a wagonload of ways to rewrite history.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: New VC mode -- review request
@ 2007-10-05 12:15 Paolo Bonzini
0 siblings, 0 replies; 20+ messages in thread
From: Paolo Bonzini @ 2007-10-05 12:15 UTC (permalink / raw)
To: dann, emacs-devel
> > > > > vc-rollback = C-x v c
> > > >
> > > > Do you have an implementation for this function for any backend? It
> > > > would be interesting to see it.
> > >
> > >
> > > Sorry, I don't remember which other back end I implemented it for. I
> > > do know that most VCSes cannot support this operation at all
>
> OK, thanks, I was trying to see if it would be interesting to try to
> support such on operation on modern VCSes...
git supports it via "git reset --hard HEAD^". You can actually rollback
to any revision using "git reset --hard <revision>".
Paolo
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: New VC mode -- review request
2007-10-04 2:22 ` Eric S. Raymond
@ 2007-10-05 16:12 ` Richard Stallman
0 siblings, 0 replies; 20+ messages in thread
From: Richard Stallman @ 2007-10-05 16:12 UTC (permalink / raw)
To: esr; +Cc: emacs-devel
> Before installing these changes, please post the change log for them
> here, so we can work on them to make them suitable.
I haven't the faintest idea how to do this. Your change-log format is
good for describing small incremental changes at the granularity of
individual functions, but not for major rewrites where abstractions
touch many functions at once. It's not that I'm unwilling to try to
write something useful, I can't imagine how to within this format.
Please list the functions that you have changed.
For those that were totally rewritten, just say "totally rewritten".
For those that have smaller changes, describe the changes.
If explanations of program logic are useful, please put them in
comments in the source. (Perhaps you have already done this.)
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: New VC mode -- review request
2007-10-04 2:14 ` Dan Nicolaescu
@ 2007-10-09 14:55 ` Eric S. Raymond
2007-10-09 15:33 ` Dan Nicolaescu
0 siblings, 1 reply; 20+ messages in thread
From: Eric S. Raymond @ 2007-10-09 14:55 UTC (permalink / raw)
To: Dan Nicolaescu; +Cc: emacs-devel
Dan Nicolaescu <dann@ics.uci.edu>:
> mkdir /tmp/test
> mkdir /tmp/test/RCS
> cd /tmp/test
> cp ~/.emacs 1.el
> cp ~/.emacs 2.el
>
> emacs -q 1.el 2.el
>
> C-x v i C-x v v for each of the 2 files. After that they should be
> writable. Quit emacs.
>
> echo foo >> 1.el
> echo foo >> 2.el
>
> emacs -q -l vc.el
> (where vc.el is your vc.el)
>
> C-x v d /tmp/test RET
> Mark the 2 files.
> v u
>
>
> and now that gets an error.
Got it. Turns out buffer-modified-p doesn't behave as I expected on
the nil value returned from get-file-buffer on a nonexistent file.
The fix is trivial.
> BTW, I just found another issue:
> with the same setup as above, do:
> cp ~/.emacs /tmp/test/3.el
>
> emacs -q -l vc.el /tmp/test/3.el
>
> C-x v v
> fails with: "No fileset is available here."
That's correct, because the visited file isn't under version control.
There's a design argument that maybe something different ought to happen here,
but that's an after-the-merge issue.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: New VC mode -- review request
2007-10-09 14:55 ` Eric S. Raymond
@ 2007-10-09 15:33 ` Dan Nicolaescu
2007-10-09 17:21 ` Eric S. Raymond
0 siblings, 1 reply; 20+ messages in thread
From: Dan Nicolaescu @ 2007-10-09 15:33 UTC (permalink / raw)
To: esr; +Cc: emacs-devel
"Eric S. Raymond" <esr@thyrsus.com> writes:
> Dan Nicolaescu <dann@ics.uci.edu>:
> > BTW, I just found another issue:
> > with the same setup as above, do:
> > cp ~/.emacs /tmp/test/3.el
> >
> > emacs -q -l vc.el /tmp/test/3.el
> >
> > C-x v v
> > fails with: "No fileset is available here."
>
> That's correct, because the visited file isn't under version control.
That would be a change in long standing behavior, and it is
inconsistent with with to docstring for vc-next-action: " If every
file is not already registered, this registers each one for version
control. This does an add, but not a commit."
IMO this behavior is one of the strengths of vc: C-x v v always does TRT.
> There's a design argument that maybe something different ought to happen here,
> but that's an after-the-merge issue.
Sure, just let's make sure it does not get forgotten.
Another post merge issue:
The code that deals with registering in vc-next-action:
;; Files aren't registered
((not state)
(mapc 'vc-register files))
Maybe vc-register could work on a list of files? vc-BACKEND-register
already does that..
^ permalink raw reply [flat|nested] 20+ messages in thread
* Re: New VC mode -- review request
2007-10-09 15:33 ` Dan Nicolaescu
@ 2007-10-09 17:21 ` Eric S. Raymond
0 siblings, 0 replies; 20+ messages in thread
From: Eric S. Raymond @ 2007-10-09 17:21 UTC (permalink / raw)
To: Dan Nicolaescu; +Cc: emacs-devel
Dan Nicolaescu <dann@ics.uci.edu>:
> > That's correct, because the visited file isn't under version control.
>
> That would be a change in long standing behavior, and it is
> inconsistent with with to docstring for vc-next-action: " If every
> file is not already registered, this registers each one for version
> control. This does an add, but not a commit."
> IMO this behavior is one of the strengths of vc: C-x v v always does TRT.
Actually, I agree with you -- that's how I originally wrote C-x v v, and
with that DTRT intention. But somebody broke that feature of vc-next-action
years ago, and I've been trying to be very conservative about not
bundling into new VC behavioral changes that weren't directly related
to the fileset stuff.
> Sure, just let's make sure it does not get forgotten.
Since it's the way I originally wanted the mode to work, it won't be :-)
> Another post merge issue:
> The code that deals with registering in vc-next-action:
> ;; Files aren't registered
> ((not state)
> (mapc 'vc-register files))
>
> Maybe vc-register could work on a list of files? vc-BACKEND-register
> already does that..
Noted. I'll start keeping a to-do list.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
^ permalink raw reply [flat|nested] 20+ messages in thread
end of thread, other threads:[~2007-10-09 17:21 UTC | newest]
Thread overview: 20+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-10-03 10:35 New VC mode -- review request Eric S. Raymond
2007-10-03 14:31 ` Dan Nicolaescu
2007-10-03 17:00 ` Eric S. Raymond
2007-10-04 0:42 ` Dan Nicolaescu
2007-10-04 2:02 ` Eric S. Raymond
2007-10-04 2:14 ` Dan Nicolaescu
2007-10-09 14:55 ` Eric S. Raymond
2007-10-09 15:33 ` Dan Nicolaescu
2007-10-09 17:21 ` Eric S. Raymond
2007-10-04 7:18 ` Thien-Thi Nguyen
2007-10-03 21:32 ` Alexandru Harsanyi
2007-10-04 2:24 ` Dan Nicolaescu
2007-10-04 9:46 ` Alexandru Harsanyi
2007-10-04 9:51 ` Eli Zaretskii
2007-10-04 17:27 ` Richard Stallman
2007-10-04 20:32 ` David Kastrup
2007-10-04 2:02 ` Richard Stallman
2007-10-04 2:22 ` Eric S. Raymond
2007-10-05 16:12 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2007-10-05 12:15 Paolo Bonzini
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).