
The following is an example key-binding definition. See the command extension point documentation for more details on these advanced features. For example, you can define an accelerator that applies only to a German Linux GTK installation of Eclipse. You can also define a key binding that applies only to a particular locale or platform. You can find command IDs by browsing the plugin.xml file of the plug-in that defines that action.
The ID of the command that you are creating a binding for. The scheme, for the key binding, for example, the default key binding scheme or the Emacs key binding scheme. For example, the text editor defines a context that can override bindings from the global context. The context, or scope, for the key binding. When you define a key sequence, you generally specify four things: Keyboard shortcuts can also be created by defining a key sequence, using the .bindings extension point. The native configuration for Eclipse is Default.ĭefine a Keyboard Shortcut Through an Extension Point Similarly, Microsoft Visual Studio defines a set of shortcuts that emulates that IDE. Emacs is a set of keyboard shortcuts that emulates emacs. This page displays the currently active Scheme (key configuration) and the keyboard shortcuts it defines. To see the current key configuration and its keyboard shortcuts, choose the Eclipse > Preferences menu command to open the Eclipse workbench Preferences. This FAQ describes two different ways to define shortcut keys.ĭisplay and Edit the Current Keyboard Shortcuts
The user chooses the key configuration that emulates the shortcut keys of his or her favorite editor or IDE. Keyboard shortcuts are organized into independent sets called key configurations or schemes. A keyboard shortcut (key binding) defines a key that when pressed will execute an Eclipse command.