Changing Keyboard Shortcuts

💡

You can change the shortcuts for a few menu commands and other actions in Klive. This feature is experimental and may change in the future.

Update Shortcuts

You can change a few shortcut keys when using Klive IDE with the set in the interactive command panel:

set -u shortcuts.<actionId> "<keyId>"

Here, <actionId> is one of the following values (case-sensitive):

fullScreen. Toggle Full Screen
stepInto. Debug: Step Into
stepOver. Debug: Step Over
stepOut. Debug: Step Out

The <keyId> value must be a valid shortcut description using this syntax:

You can define custom shortcut keys using the following syntax, compatible with Windows, macOS, and Linux.

"modifier+key"

Use CmdOrCtrl to define Cmd on macOS and Ctrl on Windows/Linux. Modifiers and keys are case-insensitive.

Modifiers:

Modifier	Windows/Linux	MacOS
`CmdOrCtrl`	Ctrl	⌘ (Command)
`Ctrl`	Ctrl	⌃ (Control)
`Cmd`	N/A	⌘ (Command)
`Alt`	Alt	⌥ (Option)
`Option`	N/A	⌥ (Option)
`Shift`	Shift	⇧ (Shift)

Keys:

Letters: A to Z (e.g., "CmdOrCtrl+S" for Save)
Numbers: 0-9
Function Keys: F1 to F24
Special Keys:
- Enter, Backspace, Delete, Esc, Tab, Space
- Up, Down, Left, Right

💡

You must restart Klive to use to use the new accelerator keys. Though it may work with the new keys immediately in some environments, the proper reassignment requires a restart.

Reset Shortcuts

To reset a particular shortcut (let Klive forget about a previously set shortcut), run this command:

set -u shortcuts.<actionId>

Conflicts with Other Keys

The Monaco Editor (your code editor) may already use one of your new accelerator keys. If Klive experiences a conflict between a Monaco Editor key and your stepInto, stepOver, or stepOut keys, it will force your keys and oppress the initial Monaco functionality.

💡

Your OS may override the key combination that you define. In this case, the OS-assigned shortcut key function will prevail.

Diagnostics Changing default file extensions