From: <klaus.berndl@sdm.de>
Subject: vc-state always calls heuristic function
Date: Tue, 23 Nov 2004 17:57:01 +0100 [thread overview]
Message-ID: <1B3ACCFD5694A94DBA4E231402B0E9ED57AE54@mucmail1.sdm.de> (raw)
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: klaus.berndl@sdm.de
sd&m AG http://www.sdm.de
software design & management
Carl-Wery-Str. 42, 81739 Muenchen, Germany
Tel +49 89 63812-392, Fax -220
next reply other threads:[~2004-11-23 16:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 16:57 klaus.berndl [this message]
2004-11-23 17:21 ` vc-state always calls heuristic function Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2004-11-23 17:31 klaus.berndl
2004-11-23 20:44 ` Stefan Monnier
2004-12-02 19:19 ` Kevin Rodgers
2004-11-24 8:39 klaus.berndl
2004-11-24 10:55 ` Andre Spiegel
2004-11-24 13:54 ` Stefan Monnier
2004-11-24 11:04 klaus.berndl
2004-11-24 12:00 ` Andre Spiegel
2004-11-24 11:08 klaus.berndl
2004-11-24 12:11 klaus.berndl
2004-11-24 14:44 klaus.berndl
2004-12-03 7:32 klaus.berndl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1B3ACCFD5694A94DBA4E231402B0E9ED57AE54@mucmail1.sdm.de \
--to=klaus.berndl@sdm.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.