But you need to convince Allan to give you write access. The best way to do that is probably to contribute a bunch of stuff to the Perforce bundle (or to other bundles as strikes your fancy) as patches or as a downloadable copy somewhere.
I finally made time to start turning my experimental changes into patches. I thought I'd start simple. Attached is a Help command I added. (I stole the method of embedding the Markdown text in the command text from the TODO bundle Help command.)
After I get confirmation that this patch is alright (or I learn what I did wrong), I'll start contributing more patches (to the bundle code itself).
-- Daryl
On 3/21/07, Chris Thomas chris@cjack.com wrote:
I didn't get any replies to my earlier emails, which makes me wonder if the Perforce bundle needs a maintainer.
I would think the relatively thin state of the Perforce bundle would be a better hint. :)
If so, I would like to volunteer.
Great! I've been hoping someone would step up. My workplace switched to Subversion, I've never used Perforce outside of work, and the amount of spare time I have is usually zero or negative.
But you need to convince Allan to give you write access. The best way to do that is probably to contribute a bunch of stuff to the Perforce bundle (or to other bundles as strikes your fancy) as patches or as a downloadable copy somewhere.
Chris
On Mar 21, 2007, at 4:16 PM, Daryl Spitzer wrote:
I solved my problem. It occurred to me that the Perforce bundle commands that use shell scripts have environment variables set in my .bash_profile, but the commands that use Ruby scripts don't. Adding P4PORT, P4USER and P4CLIENT shell variables in TextMate's Advanced preferences did the trick.
I didn't get any replies to my earlier emails, which makes me wonder if the Perforce bundle needs a maintainer. If so, I would like to volunteer.
-- Daryl
On 3/19/07, Daryl Spitzer daryl.spitzer@gmail.com wrote:
I just noticed that Perforce->Open for Editing works (but Perforce->Diff With Base still doesn't). I see in the Bundle Editor that Open for Editing is a simple shell script (that just does `p4 edit`) but Diff With Base is a Ruby script that requires 'p4_diff' and calls "Perforce::diff_active_file()". So the error message I get may be misleading.
I wonder if I need to install the Perforce Ruby API separately.
-- Daryl
On 3/19/07, Daryl Spitzer daryl.spitzer@gmail.com wrote:
I'm new to TextMate, but after reading James Gray's book, I'm
eager to
become a "power user"...
I installed the Perforce bundle (using the GetBundle bundle) and
just
tried it for the first time. I selected Perforce->Diff With Base
with
a file open that I've already ran `p4 edit` on in the command-line, and I get:
Perforce client error: Connect to server failed; check $P4PORT. TCP connect to perforce failed. perforce: host unknown.
I double-checked that $P4PORT is set properly, and I can run
Perforce
fine from Terminal (and from BBEdit). Do I need to do something
else
to setup the bundle? (Is there a way to find documentation for bundles that I haven't found yet?)
I also noticed that all the key equivalents in the Perforce
bundle are
"^$". Is this a sign of some kind of problem?
-- Daryl
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate