The Edit Current Client Spec command allows you to
edit your client specification. This will allow you to change
the way your client workspace appears.
Client Spec:
The name of your client spec. This is a read-only field.
The date and time at which the client spec was last updated.
This is a read-only field.
The date and time at which the client spec was last accessed.
This is a read-only field.
The Perforce user who created the client spec. This can be
changed to grant another user control over the client.
If set, use of the client spec is restricted to the machine
named in the Host: field. To use this client spec
from any machine, leave this field blank.
An optional description of the client.
The root directory of the client workspace. This directory is
specified in local syntax; that is, relative to the local filesystem
on which the files in the client workspace will reside. If you're
working under Windows and have files mapped to multiple drives
in the View: field, use the special client root null.
(Note: If you change the client root, you'll have to re-sync
your workspace and get rid of any files still existing under your
old client root.)
A Perforce client specification's behavior can be changed by
setting the following flags:
Will all files be writable on the client, or only files
that have been checked out?
The default value is off (noallwrite), so that
only files you've opened will be writable.
Will data sent between your client workspace and the Perforce server
be compressed?
The default value is off (nocompress).
Over a LAN or high-bandwidth connection, there's little benefit
to compressing this data, but if you're operating over a slow
link, turning this option on will help.
Lock (or write-protect) the client spec?
The default value is off (unlocked). Anyone can use
or edit the client specification. If you turn this on, only you
will be able to use the client or edit the specification.
Should a sync operation that deletes all files in
a directory also delete the directory?
The default value is off (normdir). Sync will
leave client directories in your client even if all files in the
directory have been removed. (If you turn this option on, empty
directories will be removed.)
Should a sync operation overwrite any writable opened files?
The default value is off (noclobber).
If you turn this option on, any writable opened files on your client
(either from using the allwrite option described above,
or by manually changing permissions from within your local operating
system), a sync command will be able overwrite any changes to
those files.
Should CR/LF translation be performed on text files being moved
between the Perforce depot and your client workspace?
The default value is on (crlf). Carriage return and
linefeed (CR/LF) translation will be performed.
(Note: If you change this setting, you'll have to re-sync your
client workspace in order to apply the new translation setting.
You must also use the "Same revision" checkbox when performing
the Sync to force the refreshing of the files.)
What should the modification time on a file in your workspace
be after a Sync command?
The default value is off (nomodtime).
The modification time of a file on your local operating system
will be set to the time when the file was synced to your
client workspace. Turning this option on will force Perforce
to reset each file's modification time to the time it was
submitted to the depot.
A mapping of files in the depot to files in the client workspace.
By editing the mapping in the View: form, you can choose
which files will be included in your client workspace, and where
they'll appear. The default view maps all files in the depot to
the client. If your depot is large, you'll almost certainly want
to restrict your client view to only the files in which you're
interested. Once you've changed your view, you'll have to use
the Sync command in order to refresh your client workspace
with the settings in your new view.
[Return to "How to Use P4Web"]