From: Hong Xu <hong@topbug.net>
To: 23436@debbugs.gnu.org
Cc: Hong Xu <hong@topbug.net>
Subject: bug#23436: [PATCH] Use the true name of a file to determine responsible vc.
Date: Tue, 3 May 2016 14:32:25 -0700 [thread overview]
Message-ID: <1462311145-5959-1-git-send-email-hong@topbug.net> (raw)
In many cases, e.g., a symbolic link to a directory inside a vc tracked
directory, vc-responsible-backend would fail to know the true backend.
---
There is probably a better fix than this... Feel free to do so.
---
lisp/vc/vc.el | 15 ++++++++-------
1 file changed, 8 insertions(+), 7 deletions(-)
diff --git a/lisp/vc/vc.el b/lisp/vc/vc.el
index 25b41e34e645..1b060b4d1374 100644
--- a/lisp/vc/vc.el
+++ b/lisp/vc/vc.el
@@ -960,14 +960,15 @@ If FILE is already registered, return the
backend of FILE. If FILE is not registered, then the
first backend in `vc-handled-backends' that declares itself
responsible for FILE is returned."
- (or (and (not (file-directory-p file)) (vc-backend file))
+ (let ((file-path (file-truename file)))
+ (or (and (not (file-directory-p file-path)) (vc-backend file-path))
(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 (vc-call-backend backend 'responsible-p file)
- (throw 'found backend))))
- (error "No VC backend is responsible for %s" file)))
+ ;; 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 (vc-call-backend backend 'responsible-p file-path)
+ (throw 'found backend))))
+ (error "No VC backend is responsible for %s" file-path))))
(defun vc-expand-dirs (file-or-dir-list backend)
"Expands directories in a file list specification.
--
2.8.2
next reply other threads:[~2016-05-03 21:32 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 21:32 Hong Xu [this message]
2016-10-19 19:19 ` bug#23436: [PATCH] Use the true name of a file to determine responsible vc Hong Xu
2016-10-19 19:33 ` bug#23436: [PATCH] Attemp to use the true name of a file to determine responsible vc if the genuine name does not work Hong Xu
2016-10-19 23:37 ` Dmitry Gutov
2016-10-19 23:49 ` Hong Xu
2016-10-19 23:58 ` Dmitry Gutov
2016-10-20 0:16 ` Hong Xu
2016-10-20 6:58 ` Eli Zaretskii
2016-10-20 7:21 ` Hong Xu
2016-10-20 8:23 ` Eli Zaretskii
2016-10-20 8:50 ` Dmitry Gutov
2016-10-20 9:46 ` Andreas Schwab
2016-10-20 10:02 ` Eli Zaretskii
2016-10-20 10:58 ` Eli Zaretskii
2016-10-20 9:47 ` Dmitry Gutov
2016-10-20 16:39 ` Hong Xu
2016-10-20 22:34 ` Dmitry Gutov
2016-10-20 23:04 ` Hong Xu
2016-10-24 23:41 ` Dmitry Gutov
2016-10-25 19:05 ` Hong Xu
2016-10-25 23:12 ` Dmitry Gutov
2016-10-30 0:42 ` Hong Xu
2016-10-30 16:21 ` Eli Zaretskii
2016-10-30 22:50 ` Hong Xu
2016-10-31 15:43 ` Eli Zaretskii
2016-10-31 19:38 ` Hong Xu
2016-11-01 18:47 ` Eli Zaretskii
2016-11-04 7:46 ` Hong Xu
2016-11-04 10:08 ` Eli Zaretskii
2016-10-31 11:34 ` Dmitry Gutov
2016-10-31 19:24 ` Hong Xu
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1462311145-5959-1-git-send-email-hong@topbug.net \
--to=hong@topbug.net \
--cc=23436@debbugs.gnu.org \
/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 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).