Knowledgebase

Search:     Advanced search

Opening Working Directories in the File Manager

Article ID: 665  |  Last updated: 23 Dec, 2014

Note: This article only applies to Surround SCM 2008.1 and later.

You can right-click a file or repository in the Source Tree view in the Surround SCM Client and open the associated working directory. This can help save time locating files on the local computer. The directory automatically opens in Explorer on Windows and in the Finder on Mac OS X. On Linux, you need to configure the file manager to use.

Adding the command to shortcut menus

If you upgrade to Surround SCM 2008.1 or later, you need to add the command to open working directories to the repository and file list shortcut menus.

Note: If you perform a clean install, the command is available on the shortcut menus by default.

  1. Choose Tools > User Options then select Repository Menu from the Source Tree category.
  2. Select the command name in the Available menu items list and click the right arrow to move it to the Current menu items list.
    The command names are:
    Windows—Open Containing Folder
    Mac—Reveal in Finder
    Linux—Open Working Directory
  3. Select File List Menu from the Source Tree category.
  4. Repeat step 2.
  5. Click OK to save the changes.

Configuring a Linux file manager

If you use Linux, you need to configure the file manager used to open working directories.

  1. Choose Tools > User Options then select the File Manager category.
  2. Enter the File manager command used to open the file manager and any command line arguments, or click Browse to select the path.
    The %1 variable is replaced with the working directory path when you select the Open Working Directory command. The variable is automatically added to the command if you do not enter it.
  3. Click OK to save the changes.
Article ID: 665  |   Last updated: 23 Dec, 2014
Tags
Linux working directory Windows Explorer Finder file manager

Prev   Next
Upgrading from Surround SCM 2008.1.x     Shrinking the SQL Server Transaction Log Size