fix: vc-p4 doesn't recognize a file in its client because of case
When checking to see if a file is within a Perforce client, match the root directory and current directory as reported by Perforce and ignore case differences. Sometimes (at least on Windows) the current directory and the client root can point at the same directory, but because of the way Perforce creates directories and files the case might differ.
This commit is contained in:
parent
43c4b8fa56
commit
0637cddd58
1 changed files with 1 additions and 1 deletions
2
vc-p4.el
2
vc-p4.el
|
@ -930,7 +930,7 @@ If DIRNAME is not specified, uses `default-directory'."
|
||||||
(info (p4-lowlevel-info))
|
(info (p4-lowlevel-info))
|
||||||
(root (alist-get "Client root" info nil nil #'string=))
|
(root (alist-get "Client root" info nil nil #'string=))
|
||||||
(cwd (alist-get "Current directory" info nil nil #'string=)))
|
(cwd (alist-get "Current directory" info nil nil #'string=)))
|
||||||
(string-prefix-p root cwd)))
|
(string-prefix-p root cwd t)))
|
||||||
|
|
||||||
(defun vc-p4-has-unresolved-conflicts-p (file)
|
(defun vc-p4-has-unresolved-conflicts-p (file)
|
||||||
"Search through FILE's buffer for unresolved P4 conflicts.
|
"Search through FILE's buffer for unresolved P4 conflicts.
|
||||||
|
|
Loading…
Reference in a new issue