[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
vc-state always calls heuristic function
From: |
klaus.berndl |
Subject: |
vc-state always calls heuristic function |
Date: |
Tue, 23 Nov 2004 17:57:01 +0100 |
This is the current implementation of the vc-state-function:
(defun vc-state (file)
"Return the version control state of FILE.
..."
;; FIXME: New (sub)states needed (?):
;; - `added' (i.e. `edited' but with no base version yet,
;; typically represented by vc-workfile-version = "0")
;; - `conflict' (i.e. `edited' with conflict markers)
;; - `removed'
;; - `copied' and `moved' (might be handled by `removed' and `added')
(or (vc-file-getprop file 'vc-state)
(if (vc-backend file)
(vc-file-setprop file 'vc-state
(vc-call state-heuristic file)))))
You see, that always the heuristic method of a backend is used
[(vc-call state-heuristic file)] - even if a backend offers also
a "real" statechecker. E.g. vc-cvs.el offers `vc-cvs-state' and
`vc-cvs-state-heuristic'... But current implementation of `vc-state'
will never use `vc-cvs-state'! Why??
IMHO there should be a way so a user can customize if `vc-state' should
use the heuristic approach or the real state-check if a backend offers
both of them. What do you think?
Ciao,
Klaus
Klaus Berndl mailto: address@hidden
sd&m AG http://www.sdm.de
software design & management
Carl-Wery-Str. 42, 81739 Muenchen, Germany
Tel +49 89 63812-392, Fax -220
- vc-state always calls heuristic function,
klaus.berndl <=
- RE: vc-state always calls heuristic function, klaus.berndl, 2004/11/23
- RE: vc-state always calls heuristic function, klaus.berndl, 2004/11/24
- RE: vc-state always calls heuristic function, klaus.berndl, 2004/11/24
- RE: vc-state always calls heuristic function, klaus.berndl, 2004/11/24
- RE: vc-state always calls heuristic function, klaus.berndl, 2004/11/24