Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to login/connect with ST3 Perforce Plugin #5

Open
pcockwell opened this issue Oct 26, 2013 · 1 comment
Open

Unable to login/connect with ST3 Perforce Plugin #5

pcockwell opened this issue Oct 26, 2013 · 1 comment

Comments

@pcockwell
Copy link

Here's a Stack Overflow question containing some details on my issue:
http://stackoverflow.com/questions/19599942/sublime-text-3-perforce-plugin

In short,

  • I'm using linux mint
  • I've installed p4v, p4 and ST3.
  • I've created a P4CONFIG (named .p4settings and set the P4CONFIG environment variable to '.p4settings') in the workspace folder that contains the P4PORT, P4CLIENT and P4USER variables and their appropriate values.
  • I can connect to the perforce server using the p4 command
  • I've added the Perforce.sublime-settings files to my ~/.config/sublime-text-3/Packages/User folder that contains the other ST3 plugin settings.
  • The settings include "perforce_auto_checkout_on_save": true.
  • I've gone to terminal in the relevant folder I am trying to edit and ran the p4 info command and it seems to recognize the server and workspace I am trying to access.

Still can't log in using the ST3 Perforce: Login command, and as a result, when I save, it doesn't check out the files. There is no output in the console when I attempt to log in. No errors, and no warning/descriptive output.

@ericmartel
Copy link
Owner

Hi Patrick,

This plugin is pretty primitive and will rely what "p4 info" provides. I didn't implement the Login but I could look into it. Do you have any console output when trying to save the file? Like "File is not under the client root."?

This plugin was unfortunately never "design", it's just feature creep after feature creep. I'm in the process of writing a new one with much better error / state reporting, but it's pretty long unfortunately.

If you want, email me at emartel@gmail.com with your p4 info output, the path of the file you're working on, etc, I might be able to figure out what's going on

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants