Each operating system and shell uses its own syntax for setting environment variables. This table shows how the P4CLIENT environment variable would be set in each OS and shell..
| OS & Shell | Environment Variable Example |
|---|---|
| UNIX: ksh, sh, bash | export P4CLIENT=value |
| UNIX: csh | setenv P4CLIENT value |
| VMS | def/j P4CLIENT "value" |
| Mac MPW | set -e P4CLIENT value |
| Windows 95/NT |
On NT, registry variables are recommended in place of environment variables. Registry variables can be set in the user-specific part of the registry through the p4 client program with:
p4 set P4VAR=valuePlease see p4 set for more information. Environment variables can be set with: set P4CLIENT=valueWhen used, environment variables settings will override the values of the corresponding registry variables. |
The variables described on the next pages are listed alphabetically by categories. The category names and meanings are:
Crucial: The variable will almost definitely need to be set on the client; the default values will rarely be sufficient.
Useful: Setting this variable can provide additional functionality to the user, but is not crucial to Perforce's workings.
Esoteric: The default value of this variable should be sufficient; it will rarely need to be changed.
Server: the variable is set by the Perforce system administrator on the Perforce server. Some of these variables are used by the client as well; in these cases, the variable is categorized twice.
|
Crucial Client Variables |
Useful Client Variables |
Esoteric Client Variables |
Server Variables |
|---|---|---|---|
| P4CLIENT | P4CONFIG | P4PAGER | P4JOURNAL |
| P4PORT | P4DIFF | PWD | P4LOG |
| P4PASSWD | P4EDITOR | TMP, TEMP | P4PORT |
| P4USER | P4MERGE | P4ROOT |