The refresh command is used for the following purposes:
To switch between different client configurations.
For more information about getting a list of the available client configurations, see CLIENTS .
In case new files or folders have been created in the local file system but are not visible in the tool.
In case new files or folders have been created on the server (as a result of checkin or integrate commands from other users) and they are not visible in the tool because the tool has cached the content of a folder.
Syntax
Syntax |
REFRESH [clientName] |
Arguments |
|
[clientName] |
A client name. The shell will then get refreshed using the specified client def. If a client def with the given name does not exist then the default client def will be used. If the client name that was active before the refresh call is different from that specified, the current directory will be changed to the browse root. |
Description |
Refreshes the shell. |
Switching between Client Definitions
Two client definitions named def_1 and def_2 are available and def_1 is currently used.
To switch to client definition def_2 , execute:
refresh def_2
Refreshing the Result of the DIR Command
Execute the dir command in your current folder and see two files: a.java and b.java . You know that the file c.java has already been checked in by another colleague, but it does not appear in the result of the dir command, since the content of the current folder is cached.
To re-read the directory content, execute . refresh
Then execute dir .
The file c.java appears in the output of the dir command.