ryuslash/vc-p4
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
Fork of Jonathan Kamens', Magnus Henoch's and Ben Key's p4-vc.el
105 commits 1 branch 0 tags 310 KiB
Emacs Lisp 99.1%
Makefile 0.9%
Find a file
Tom Willemse 461b1357f9 Rename ‘vc-p4-find-version’ to ‘vc-p4-find-revision’ 
It seems that nothing uses ‘vc-p4-find-version’, or ‘vc-find-version’, and it’s
not mentioned as a function to implement in vc.el. There is a ‘find-revision’
mentioned with the same signature though.
2021-02-27 15:25:22 -08:00
.gitignore Ignore any directory starting with vc-p4- 2019-03-06 00:10:13 -08:00
.gitlab-ci.yml Rename deploy -> pages 2020-05-13 22:08:21 -07:00
CHANGELOG.org Add ‘vc-p4-dir-extra-headers’ 2021-01-28 18:54:27 -08:00
Makefile Bump version 2020-05-27 22:13:18 -07:00
p4-lowlevel.el Fix some warnings 2021-02-27 15:12:12 -08:00
README.org Add README 2021-01-23 11:12:17 -08:00
vc-p4.el Rename ‘vc-p4-find-version’ to ‘vc-p4-find-revision’ 2021-02-27 15:25:22 -08:00

README.org

vc-p4

This package provides VC integration with the Perforce version control system.

This package is quite old and was written for Emacs 23 I think. I'm trying to pull it into the next generation by making it work on Emacs 26.3 at the moment.

Road to v1

Before I can say that I can release version 1.0.0 of this project, I feel that these features need to be present (this list is subject to change):

  • Create new changelists.
  • Modify existing changelists.
  • Delete existing changelists.
  • Move files between changelists.
  • View changelist info in vc-dir.
  • View repository information in vc-dir. (Things like the Client name, current workspace, etc.)
  • Switch workspaces.

Some of these features may already be present and working and I just haven't discovered them yet, but until I feel confident that it can be done and is part of my workflow, I'm keeping it on the list.

Change log

See the change log.

Usage

Customization options:

vc-p4-client
The client to use to try to connect to Perforce. If you have multiple workspaces in Perforce you can set this as a directory-local variable to make sure you're connecting to the right Perforce workspace.