Command Line History
The command line maintains a command history, allowing you to quickly reuse previously entered com-
mands. Once the command line is open, use the arrow keys to scroll up and down in the command his-
tory.
Command Line Completions
As you type a command, a list of matching completions is displayed, including any command line argu-
ments used in a previous command. Use
Tab
or the
Down
arrow to move to the next command in the list,
and
Shift
+
Tab
or the
Up
arrow to move to the previous command. Press the
Enter
key to select the cur-
rent command.
Some commands, like
set_var
, prompt for arguments. SlickEdit
®
Core maintains a history of arguments
used for each command. Use the same completion and history mechanism as described above for com-
mands to complete arguments. Typically, the most recent argument you typed is automatically displayed.
Tip
Command completions are useful for discovering other useful operations. For instance, to find all
operations that begin with "find", type
find
in the command line, and a list of those commands is
displayed. Some search commands do not begin with "find", like
gui_find
, so you may not dis-
cover all related commands this way. To find all commands containing the word "find," use the
Key Bindings dialog (click
Window
→
Preferences
, expand
SlickEdit
and click
General
in the
tree, then double-click the
Key Bindings
setting; alternatively, use the
gui_keybindings
com-
mand). See
Key and Mouse Bindings
for more information.
For information about other items that can be automatically completed, see
Completions
.
Disabling Command Line Completions
To disable command line completions, from the main menu, click
Window
→
Preferences
, expand
SlickEdit
and click
General
in the tree, then double-click the
General
setting. On the General Options
dialog, select the
General Tab
. Uncheck the option
List command line completions
. Note that this op-
tion does not apply to the Vim command line.
Using Shortcuts Inside the Command Line
The command line is a text box control just like the text boxes that appear in various dialog boxes. For a
list of key shortcuts that can be used inside the command line and other text boxes within SlickEdit
®
Core,
see
Key Shortcuts in Text Boxes
.
Using the Command Line to View Key Binding Associations
Command Line Completions
31
Summary of Contents for Corev3.3 for Eclipse
Page 1: ...Think Slick Corev3 3 for Eclipse...
Page 2: ......
Page 3: ...SlickEdit Core v3 3 for Eclipse...
Page 5: ......
Page 6: ......
Page 14: ...xii...
Page 20: ...xviii...
Page 22: ...xx...
Page 23: ...Chapter 1 Introduction 1...
Page 41: ...Chapter 3 User Interface 19...
Page 61: ...Chapter 4 User Preferences 39...
Page 80: ...BODY BODY HTML HTMLEOF Restoring Settings on Startup 58...
Page 82: ...60...
Page 83: ...Chapter 5 Context Tagging 61...
Page 97: ...Chapter 6 Editing Features 75...
Page 124: ...Code Templates 102...
Page 238: ...Figure 6 49 Test Parsing Configuration Example 1 C Refactoring 216...
Page 241: ...Figure 6 51 Test Parsing Configuration Example 3 Reviewing Refactoring Changes 219...
Page 250: ...228...
Page 251: ...Chapter 7 Language Specific Editing 229...
Page 328: ...306...
Page 329: ...Chapter 8 Tools and Utilities 307...
Page 350: ...328...
Page 351: ...Chapter 9 Macros and Macro Programming 329...
Page 360: ...338...
Page 361: ...Chapter 10 SlickEdit Core Dialogs 339...
Page 375: ...Find and Replace View 353...
Page 491: ...Chapter 11 Appendix 469...
Page 567: ......
Page 568: ......