Slick V3.3 Documentation and Conventions, Accessing Documentation, Documentation Conventions

Accessing Documentation

Documentation and Conventions

Accessing Documentation

Documentation is located in the SlickEdit® Core installation directory at

<PathToSlickEditCore>/eclipse/plugins/com.slickedit.core_VERSION/docs. The docs directory contains PDFs of the following items:

•The User Guide - This guide provides comprehensive information about using SlickEdit Core.

•The Slick-C®Macro Programming Guide - This guide contains details about how to write macros using the Slick-C macro programming language.

•Emulation charts for the following editors: BBEdit, Brief, CodeWarrior™ , CodeWright® , CUA (default), Epsilon, GNU Emacs, ISPF, SlickEdit (Text Mode edition), Vim, Visual C++ ® 6, Visual Studio® , and Xcode® .

In addition to the documentation, SlickEdit Core provides a built-in Help system. The contents of the Help system is the same as the contents of the User Guide.

Documentation Feedback

We welcome your comments and suggestions regarding our documentation. Please send feedback to <docs@slickedit.com>.

Documentation Conventions

The subsequent topics describe conventions that are used in the SlickEdit® Core documentation.

Default Emulation/Key Binding Mode

CUA is the default editor emulation mode. Therefore, key bindings and shortcuts listed in the documenta- tion follow the CUA emulation.

Platform-Specific Notes

Platform-specific notes for for Microsoft Windows and Linux® are listed throughout the documentation where applicable.

Menus and Dialogs

Instructions for navigating to items accessed from the main menu are written in the form:

MainMenuItem > SubMenuItem

For example, the text "click Window → Preferences" indicates that you should first select Window from

4