I agree the BBEdit documentation is inadequate at best.
Here's what you need to do:
1) Make sure that your bash $PATH variable includes a path to p4.
2) Define a key called $P4CONFIG in the ~/.MacOSX/environment.plist
file and set it to "p4config"
This link provides more details:
http://developer.apple.com/library/mac/#qa/qa1067/_index.html.
3) The p4config value is arbitrary... it's simply the name you'd like
to use for your "p4config" files.
4) In the root directory of each of your perforce workspaces, make a
file called p4config and add lines like this:
P4CLIENT=<clientSpec>
P4USER=<userName>
P4PORT=<p4Port>
Substitute values for your environment for the <> values above.
5) Logout, then login again.
6) Launch BBEdit and open one of the Perforce managed files in one of
the workspaces you configured.
7) The P4 menu should now be enabled and you should be able to
checkout, revert, diff, etc.
8) On occasion, the P4 menu is still grayed out, try clicking the
"make modifiable" (pencil) button. BBEdit should put up an alert
saying that the file is managed by Perforce.
9) You can also define P4CONFIG in your .bashrc or .bash_profile file
in your root (~) directory (set it to p4config). Create a new
terminal window, then cd to the root of one of your workspaces. You
should be able to enter p4 at the prompt and get a help prompt instead
of an error. You can use this technique to make sure you have your
p4config files setup properly before bringing BBEdit into the mixture.
--
You received this message because you are subscribed to the
"BBEdit Talk" discussion group on Google Groups.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
<http://groups.google.com/group/bbedit?hl=en>
If you have a feature request or would like to report a problem,
please email "[email protected]" rather than posting to the group.
Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
