Fork of Jonathan Kamens', Magnus Henoch's and Ben Key's p4-vc.el
Tom Willemse
39efc77e07
- The arguments ‘comment’ and ‘rev’ have been switched. I don’t know if this used to be different from how it is now, but ‘rev’ comes last now and is optional. - The ‘vc-p4-client’ needs to be collected from the first file in the list of files to check in because ‘vc-p4-checkin’ is called from a different buffer that isn’t in the same directory. - ‘vc-p4-client’ also needs to be stored under a different name so that when it changes to the ‘*p4-lowlevel-changes*’ buffer it doesn’t clear the value. - Instead of inserting the specified comment directly, send it through ‘log-edit-extract-headers’ which removes the "Summary: " header that ‘vc-log-edit’ adds. - Indent rigidly to ‘tab-width’ instead of 8. Indenting to 8 added too many tabs to the description and caused all lines to be prefixed by a tab. |
||
---|---|---|
.gitignore | ||
.gitlab-ci.yml | ||
CHANGELOG.org | ||
Makefile | ||
p4-lowlevel.el | ||
README.org | ||
vc-p4.el |
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.