Configuration Directories and Files

User Configuration Directory

Your SlickEdit® Core configuration directory contains configuration files representing the changes you have made through setting editor options, and it preserves the state of SlickEdit Core by using the state file, Table of User Configuration Files.

You should make periodic backups of your SlickEdit Core configuration directory. If you experience a problem in the editor, you can often solve it by using a saved config directory.

Configuration changes are saved when you exit the editor. Note that SlickEdit Core cannot save configuration changes when another instance is running. If you attempt to close an instance that contains configuration changes, while another instance is running, a Save failed message is displayed, then a prompt asks whether or not to exit anyway.

Directory Location

By default, the configuration directory is located in My Documents/My SlickEdit Core Config/<Version> on Windows, and $HOME/.secore/<Version> on Linux. You can view the path to the config directory by clicking Help → About SlickEdit Core.

Changing the Configuration Directory

If you would like to use a different directory for your config files, you can pass the –vsconfig argument to Eclipse. This works the same as passing any argument to eclipse.exe (or eclipse on Linux). For example: C:\Path_To_Eclipse\eclipse.exe –vsconfig=C:\My_Config.

Resetting the Configuration Directory

For troubleshooting purposes, it is sometimes helpful to reset the configuration directory to the defaults. SlickEdit Product Support may also ask you to use a default configuration to help debug problems. To reset to the default configuration:

Exit any instances of Eclipse with SlickEdit® Core that are running.
Make a backup of the user config directory and store the backup in a safe location.
Delete the contents of the versioned config directory but NOT the directory itself.
Start Eclipse with SlickEdit Core.

After completing these steps, SlickEdit Core opens with the default configuration settings. Note that you will be prompted for all of the initial setup information just as if you were running SlickEdit Core for the first time.

Note

If, instead of deleting the contents of the directory, you delete the directory itself, SlickEdit Core will attempt to migrate your settings from a previous version.

Table of User Configuration Files

The table below provides a list of the user configuration files.

User Config File	Description
`*.als`	A text file that contains user-defined language-specific aliases.
`alias.slk`	A text file that contains user-defined global aliases (directory aliases).
`ftp.ini` (UNIX: `uftp.ini`)	A text file that contains user-defined FTP configurations.
`project.vpe` (UNIX: `uproject.vpe`)	A text file that contains user-defined language-specific projects.
`ubox.ini`	A text file that contains user-defined box and line comment styles.
`uformat.ini`	A text file that contains user-defined beautifier schemes.
`uprint.ini`	A text file that contains user-defined printing schemes.
`uscheme.ini`	A text file that contains user-defined color schemes.
`user.vlx`	A text file that contains color coding changes (keywords, etc.). This file is updated when you close the Color Coding dialog box.
`usercpp.h`	A text file that contains defines (default preprocessing) for Context Tagging® of C++ and C code.
`uservc.slk`	A text file that contains user-defined version control systems.
`usrprjtemplates.vpt`	A text file that contains user-defined project packages.
`vrestore.slk`	A text file that contains auto-restore information. The workspace files also contain auto-restore information, but only for the files/windows previously open.
`vslick.ini`	A text file that contains a few miscellaneous options. The user-configured backup directory is stored here. In addition, some customizable environment variables for path searching for macros, bitmaps, and binary files are stored here as well.
`vslick.sta` (UNIX: `vslick.stu`)	A binary file that contains dialog boxes, menus, macro pcode, key bindings, and all other configuration data not stored in one of the other configuration files. Both user and system configuration information is stored here.
`vusrdefs.e` (UNIX: `vunxdefs.e`)	A Slick-C® text file that contains the emulation setting, key bindings, color settings, language setup information, and some other miscellaneous options.
`vusrobjs.e` (UNIX: `vunxobjs.e`)	A text file that contains user-defined dialog boxes and menus in Slick-C syntax.
`vusrs.e` (UNIX: `vunxs.e`)	A text file that contains system modified dialog boxes and menus. These changes are NOT automatically transferred unless the version encoding matches. For example, `vusrs10e.e`.

System Configuration Files

System configuration files are located in the SlickEdit® Core installation directory.

Typically, these files are only modified by SlickEdit Inc. or OEM customers. OEM customers might want to modify one of these files to ship a customized version of SlickEdit Core.

Table of System Configuration Files

The table below provides a list of the system configuration files.

System Config File	Description
`alias.slk`	A text file that contains default global aliases (for example, directory aliases).
`box.ini`	A text file that contains default box and line comment styles. This file is NOT modified by the dialogs and is not preserved when a new editor is installed.
`format.ini`	A text file that contains default beautifier schemes.
`print.ini`	A text file that contains default printing schemes. This file is NOT modified by the dialogs and is not preserved when a new editor is installed.
`prjtemplates.vpt`	A text file that contains default project packages. This file is NOT modified by the dialogs and is not preserved when a new editor is installed.
`syscpp.h` (UNIX: `usyscpp.h`)	A text file that contains system-defined default preprocessing for Context Tagging® of C++ and C code.
`vcsystem.slk` (UNIX: `uvcsys.slk`)	A text file that contains default version control systems. This file is NOT modified by the dialogs and is not preserved when a new editor is installed.
`vslick.ini`	A text file that contains a few miscellaneous options. Some customizable environment variables for path searching for macros, bitmaps, and binary files are stored here as well. This file is NOT modified by the dialogs and is not preserved when a new editor is installed.
`vslick.sta` (UNIX: `vslick.stu`)	A binary file that contains default dialog boxes, menus, macro pcode, key bindings, and all other configuration data not stored in one of the other configuration files.
`vslick.vlx`	A text file that contains default color coding lexer definitions.
`vsscheme.ini`	A text file that contains default color schemes. This file is NOT modified by the dialogs and is not preserved when a new editor is installed.