Download here.

Enjoy

PS – Thanks to Charles Bates for helping identify the Windows patch.

Bad News: I need to delay the release by a few days to finish some complicated graphical menu logic.  If you only ever edit 1 file in a gvim session, things work great.  But I tend to create multiple, concurrent buffers – each may be in or NOT in an accurev workspace.    Since the graphical window decorations, including menus, are global, this means that each buffer needs to handle the logic of showing or hiding the menus.   [for the record, I don't use gvim in practice... what mouse?... but I think it's very important to provide corresponding menu options for those users]

Great News: if you are impatient, send me an email (davidpthomas at gmail dot com) and I’ll give you a copy of the plugin.  Why wait?

The next release is eminent.

Version 1.1 will include on-demand enable/disable, highlighted annotate, launching stream browser, and more.

I anticipate releasing the final 1.1 plugin this week… stay tuned!

disconnected environment

• enable/disable plugin on startup via config
• enable/disable plugin at runtime via key binding

new commands

• annotate
• update with merges
• list workspace incl/excl rules

I have been working on them for the past few months on-and-off. I am hoping to have something consumable in May.

Download release 1.0 here.

This version of the plugin requires Vim 7.x and supports AccuRev 4.5.x / 4.6.x.

Happy New Year! – dave

• evil twin detection during add
• updated error handling for promote and defunct
• interrupt handling for login
• multi-buffer statusline update for group promote
• fixed abs path CWD problem/assumption in linux
• support for -o/-O vim flags for opening multiple files
• added statusline refresh when the GUI window gets focus

And finally, the last significant new feature before the official 1.0 release…

• custom syntax highlighting for output from update, history, status, search, properties, and info!

I’m looking forward to giving the AccuRev / Vim users something for the holidays!

Download release 1.0b here.

Here are some features that were developed in the beta release:

Auto-merge: ability to perform an automatic trivial merge for (overlap) files with ‘\m’. Though, for true conflicts, you’ll want to use the provided AccuRev merge tool (acdiffgui.exe) or your own favorite such as Guiffy, Araxis, TkDiff, etc.

Change package integration: will prompt user for issue# during promote if enabled.

Progress bar: display progress during all actions involving the AccuRev server.

Interrupt handling: recover from the user hitting CTRL-C anywhere in an operation’s execution path.

Two new commands: support for populating elements ‘\v’ and displaying element properties ‘\e’

Does beta mean unstable, undocumented, or missing features? No. When I release beta software, I’ve concluded that the pre-defined feature set is completed and that to the best of my ability, the feature set has been tested to my own gold standard. That being said, it is impossible to test every possible scenario on every possible Vim-supported platform. I co-developed this plugin on both an Ubuntu 6.10 (linux) and WinXP OS with Vim7.0+. I’ve added tons of error handling and recovery code — so I expect the beta version to be quite stable under most situations. If you encounter an error condition, please don’t hesitate to send me the details and I will investigate immediately.

Will there be a beta 2? Most likely not. I’m thoroughly satisfied with the existing feature set and testing over the past month. I’m going to let this bake for 4-6 weeks and anticipate cutting the official 1.0 just in time for the holidays. Most feedback will likely be around user messaging, default key mappings, and documentation — I will address all feedback immediately but don’t anticipate needing to cut another public beta for the small (but important!) enhancements.

Enjoy!

You can expect to see the beta this month!

Download release 1.0a here.

Why alpha? This is the first release after 3 months of development. Many of the features have been working properly for many weeks now but I still have one more feature to finish before I consider this plugin “1.0″. The existing features in this alpha release is considered “done” save for any fixes or minor enhancements from the public.

Will there be an alpha 2? No. Once I finish the remaining piece (unnamed), I will launch a single beta and then the final 1.0.

Will beta be different than alpha? Not by much. Enjoy the alpha as a sneak peek knowing that what you see will pretty much be the same come 1.0.

How can I help? Download the plugin. Follow the installation instructions. And play! Let me know what you think about the commands, usability, documentation, mappings, etc!