setup steps I'm missing?

[RwwL]

I'm sure this is just user error on my part, since I'm using Perforce for the first time (in a contracting situation) and haven't gotten familiar enough yet, but:

I installed this plugin in ST2/OSX via the Sublime package manager, and I've created an ST2 project based on the root folder of my Perforce-managed codebase, and auto-checkout doesn't seem to be working. I open, edit, and save files, and expect them to show up in my default changelist the next time I look at the P4 app. Do I need to do something more to tell the plugin where my client root is, or am I misunderstanding the feature, or something else that's pretty obvious to the author/maintainers? Thanks.

[ericmartel]

Hi Rob,

The plugin is pretty much based on the p4 command line tool. Make sure your p4 is reachable in your path and you can also hint p4 with your connection settings, declaring variable such as:

export P4CLIENT=yourclientspec
export P4PORT=serveraddress:portnumber
export P4USER=user
export P4PASSWD=password

in your ~/.bash_profile

Hope this helps!

[RwwL]

Hm, so if "which p4", "which p4v", and "which p4vc" all return "not found" in my console, I'm not sure how to make sure it's in my path. Did I just fail to install the command-line tool when I installed Perforce? I kind of assumed the GUI app was just using the command-line tool itself, though..

[ericmartel]

Oh no, p4v probably resides next to p4 so it's able to call it.

Take a look at this link and let me know if it helps you: http://www.ericmartel.com/2012/02/26/mac-osx-p4-command-line-and-sublime-text-2/

[RwwL]

I installed p4 in /usr/local/bin and made it executable, and added those hints to my bash profile, but I'm not sure if I need to do anything more, I see no messages related to this plugin in the ST2 console or status bar. I'm still unclear on basic details like how auto-checkout on save can be an available feature when Perforce makes files read-only until I check them out.

[ericmartel]

Hi Rob,

I'll take a look at it tonight when I get home, if p4 is reachable by ST, any file that's under your current clientspec (which can be seen using p4 info) or using a properly setup p4config file (http://www.perforce.com/perforce/doc.current/manuals/cmdref/P4CONFIG.html) should be checked out when you edit or save it, depending on your settings.

[ericmartel]

Sorry I've been busy with other things, were you able to fix your situation or you still need me to look into it?

Thanks

[RwwL]

I got stuck, the command line tool won't run for me yet. I use ZSH for my Terminal, so I added those hints to my ~/.bash_profile and ~/.zshrc, I can't seem to google up anything useful about this zsh "exec format error" I get when I try to run p4 info.

which p4
usr/local/bin/p4

ls -la /usr/local/bin/p4
-rwxr-xr-x@ 1 rob staff 671788 Mar 21 08:38 /usr/local/bin/p4

p4 info
zsh: exec format error: p4

[ericmartel]

Hi Rob,

Unfortunately I am not a Mac expert, I don't think I can help you with this
:(

On Mon, Mar 31, 2014 at 1:42 PM, Rob Lifford notifications@github.comwrote:

I got stuck, the command line tool won't run for me yet. I use ZSH for my
Terminal, so I added those hints to my ~/.bash_profile and ~/.zshrc, I
can't seem to google up anything useful about this zsh "exec format error"
I get when I try to run p4 info.

which p4 /usr/local/bin/p4

ls -la /usr/local/bin/p4
-rwxr-xr-x@ 1 rob staff 671788 Mar 21 08:38 /usr/local/bin/p4

p4 info
zsh: exec format error: p4

Reply to this email directly or view it on GitHubhttps://github.com//issues/32#issuecomment-39117985
.