More for my own reference than anything else, here is how you install the CVS bundle for TextMate using a subversion client.
1. If you don’t already have a subversion, try the precompiled version here.
2. Set the LC_CTYPE variable to use UTF-8
export LC_CTYPE=en_US.UTF-8
3. Make a bundles directory if you have not already installed others
mkdir -p /Library/Application\ Support/TextMate/Bundles
4. Change to your bundles directory
cd /Library/Application\ Support/TextMate/Bundles/
5. Install the CVS bundle using the svn client
/usr/local/bin/svn co http://macromates.com/svn/Bundles/trunk/Bundles/CVS.tmbundle
6. Relaunch TextMate and you should now see a CVS bundle!


Thanks for this – saved me trial and error!
No probs, here is another bundle for my own reference (again) if you find yourself stuck writing VB(script) as is the case for me and QTP… yuk
/usr/local/bin/svn co http://macromates.com/svn/Bundles/trunk/Bundles/ASP_vb_NET.tmbundle
The SVN repository has since been moved. Here’s the correct SVN checkout command:
svn co http://svn.textmate.org/trunk/Bundles/CVS.tmbundle
Or, if you want to use git:
git clone git://github.com/textmate/cvs.tmbundle.git CVS.tmbundle
BTW, most of the CVS commands are not working in TextMate (v1.5.8). The History -> Log and Revert commands worked, but others fail with errors like this (from a diff attempt):
TextMate.app/Contents/SharedSupport/Support/lib/ui.rb:310:in `to_plist’: An object in the argument tree could not be converted (ArgumentError)
or this (from a commit attempt):
TextMate.app/Contents/SharedSupport/Support/lib/Builder.rb:212:in `eval’: wrong argument type Proc (expected Binding) (TypeError)
Each failed command leaves an untitled window in its wake. Anyone else see these errors? Does anyone use CVS anymore? (raising hand, looking around hopefully…)
Hello Steve,
I’m having the same to_plist related ArgumentError error come up when I try to use the Subversion bundle in conjunction with Ruby 1.9 (it works fine with 1.8).
Apparently the to_plist() method is defined via TextMate’s plist.c (http://svn.textmate.org/trunk/Tools/plist/plist.c). My hunch is that the plist.c file will need to be updated to be compatible with Ruby 1.9.
The community behind the E Text Editor (Windows based TextMate port) have gotten around the problem of plist.c being OS X native by replacing it with a Ruby class (plist.rb), but the info I have on that is pretty old (http://www.e-texteditor.com/forum/viewtopic.php?t=524&sid=79b16cca4164373c44d48aa56682bdd4). Maybe the plist.rb class is more compatible with Ruby 1.9 than plist.c is, but I haven’t tried this yet.
My to_plist problems are related to an incompatibility between the TextMate OS X plist bundle and Ruby 1.9. Here is the fix I have used to solve the problem:
# Updating osx-plist for Ruby 1.9 compatibility
$> git clone git://github.com/kballard/osx-plist.git
$> cd osx-plist/ext/plist
$> ruby extconf.rb && make
$> cp plist.bundle /Applications/TextMate.app/Contents/SharedSupport/Support/lib/osx/
Thanks, James! It make Ack in Textmate bundle work (it was complaining about to_plist too).
Pingback: Ack in Project Textmate bundle fails with Ruby 1.9 « Keep Calm And Carry On