1# Key bindings
  2
  3Zed has a very customizable key binding system—you can tweak everything to work exactly how your fingers expect!
  4
  5## Predefined keymaps
  6
  7If you're used to a specific editor's defaults, you can set a `base_keymap` in your [settings file](./configuring-zed.md).
  8We currently support:
  9
 10- VS Code (default)
 11- Atom
 12- Emacs (Beta)
 13- JetBrains
 14- Sublime Text
 15- TextMate
 16- Cursor
 17- None (disables _all_ key bindings)
 18
 19This setting can also be changed via the command palette through the `zed: toggle base keymap selector` action.
 20
 21You can also enable `vim_mode` or `helix_mode`, which add modal bindings.
 22For more information, see the documentation for [Vim mode](./vim.md) and [Helix mode](./helix.md).
 23
 24## User keymaps
 25
 26Where Zed looks for your keymap:
 27
 28- macOS/Linux: `~/.config/zed/keymap.json`
 29- Windows: `~\AppData\Roaming\Zed/keymap.json`
 30
 31You can open the keymap with the {#action zed::OpenKeymapFile} action from the command palette, or edit it in Zed's Keymap Editor, accessible via the {#action zed::OpenKeymap} action or the {#kb zed::OpenKeymap} keybinding.
 32
 33The `keymap.json` file contains a JSON array of objects with `"bindings"`. If no `"context"` is set, the bindings are always active. If it is set, the binding is only active when the [context matches](#contexts).
 34
 35Within each binding section, a [key sequence](#keybinding-syntax) is mapped to [an action](#actions). If conflicts are detected, they are resolved as [described below](#precedence).
 36
 37If you are using a non-QWERTY, Latin-character keyboard, you may want to set `use_key_equivalents` to `true`. See [Non-QWERTY keyboards](#non-qwerty-keyboards) for more information.
 38
 39For example:
 40
 41```json [keymap]
 42[
 43  {
 44    "bindings": {
 45      "ctrl-right": "editor::SelectLargerSyntaxNode",
 46      "ctrl-left": "editor::SelectSmallerSyntaxNode"
 47    }
 48  },
 49  {
 50    "context": "ProjectPanel && not_editing",
 51    "bindings": {
 52      "o": "project_panel::Open"
 53    }
 54  }
 55]
 56```
 57
 58You can see all of Zed's default bindings in the default keymaps for:
 59
 60- [macOS](https://github.com/zed-industries/zed/blob/main/assets/keymaps/default-macos.json)
 61- [Windows](https://github.com/zed-industries/zed/blob/main/assets/keymaps/default-windows.json)
 62- [Linux](https://github.com/zed-industries/zed/blob/main/assets/keymaps/default-linux.json).
 63
 64If you want to debug problems with custom keymaps, you can use `dev: Open Key Context View` from the command palette. Please file [an issue](https://github.com/zed-industries/zed) if you run into something you think should work but isn't.
 65
 66### Keybinding syntax
 67
 68Zed has the ability to match against not just a single keypress, but a sequence of keys typed in order. Each key in the `"bindings"` map is a sequence of keypresses separated with a space.
 69
 70Each keypress is a sequence of modifiers followed by a key. The modifiers are:
 71
 72- `ctrl-` The control key
 73- `cmd-`, `win-` or `super-` for the platform modifier (Command on macOS, Windows key on Windows, and the Super key on Linux).
 74- `alt-` for alt (option on macOS)
 75- `shift-` The shift key
 76- `fn-` The function key
 77- `secondary-` Equivalent to `cmd` when Zed is running on macOS and `ctrl` when on Windows and Linux
 78
 79The keys can be any single Unicode codepoint that your keyboard generates (for example `a`, `0`, `£` or `ç`), or any named key (`tab`, `f1`, `shift`, or `cmd`). If you are using a non-Latin layout (e.g. Cyrillic), you can bind either to the Cyrillic character or the Latin character that key generates with `cmd` pressed.
 80
 81A few examples:
 82
 83```json [settings]
 84 "bindings": {
 85   "cmd-k cmd-s": "zed::OpenKeymap", // matches ⌘-k then ⌘-s
 86   "space e": "editor::Complete", // type space then e
 87   "ç": "editor::Complete", // matches ⌥-c
 88   "shift shift": "file_finder::Toggle", // matches pressing and releasing shift twice
 89 }
 90```
 91
 92The `shift-` modifier can only be used in combination with a letter to indicate the uppercase version. For example, `shift-g` matches typing `G`. Although on many keyboards shift is used to type punctuation characters like `(`, the keypress is not considered to be modified, and so `shift-(` does not match.
 93
 94The `alt-` modifier can be used on many layouts to generate a different key. For example, on a macOS US keyboard, the combination `alt-c` types `ç`. You can match against either in your keymap file, though by convention, Zed spells this combination as `alt-c`.
 95
 96It is possible to match against typing a modifier key on its own. For example, `shift shift` can be used to implement JetBrains' 'Search Everywhere' shortcut. In this case, the binding happens on key release instead of on keypress.
 97
 98### Contexts
 99
100If a binding group has a `"context"` key, it will be matched against the currently active contexts in Zed.
101
102Zed's contexts make up a tree, with the root being `Workspace`. Workspaces contain Panes and Panels, and Panes contain Editors, etc. The easiest way to see what contexts are active at a given moment is the key context view, which you can get to with the `dev: open key context view` command in the command palette.
103
104For example:
105
106```
107# in an editor, it might look like this:
108Workspace os=macos keyboard_layout=com.apple.keylayout.QWERTY
109  Pane
110    Editor mode=full extension=md vim_mode=insert
111
112# in the project panel
113Workspace os=macos
114  Dock
115    ProjectPanel not_editing
116```
117
118Context expressions can contain the following syntax:
119
120- `X && Y`, `X || Y` to and/or two conditions
121- `!X` to check that a condition is false
122- `(X)` for grouping
123- `X > Y` to match if an ancestor in the tree matches X and this layer matches Y.
124
125For example:
126
127- `"context": "Editor"` - matches any editor (including inline inputs)
128- `"context": "Editor && mode=full"` - matches the main editors used for editing code
129- `"context": "!Editor && !Terminal"` - matches anywhere except where an Editor or Terminal is focused
130- `"context": "os=macos > Editor"` - matches any editor on macOS.
131
132It's worth noting that attributes are only available on the node they are defined on. This means that if you want to (for example) only enable a keybinding when the debugger is stopped in vim normal mode, you need to do `debugger_stopped > vim_mode == normal`.
133
134> Note: Before Zed v0.197.x, the `!` operator only looked at one node at a time, and `>` meant "parent" not "ancestor". This meant that `!Editor` would match the context `Workspace > Pane > Editor`, because (confusingly) the Pane matches `!Editor`, and that `os=macos > Editor` did not match the context `Workspace > Pane > Editor` because of the intermediate `Pane` node.
135
136If you're using Vim mode, we have information on how [vim modes influence the context](./vim.md#contexts). Helix mode is built on top of Vim mode and uses the same contexts.
137
138### Actions
139
140Almost all of Zed's functionality is exposed as actions.
141Although there is no explicitly documented list, you can find most of them by searching in the command palette, by looking in the default keymaps for [macOS](https://github.com/zed-industries/zed/blob/main/assets/keymaps/default-macos.json), [Windows](https://github.com/zed-industries/zed/blob/main/assets/keymaps/default-windows.json) or [Linux](https://github.com/zed-industries/zed/blob/main/assets/keymaps/default-linux.json), or by using Zed's autocomplete in your keymap file.
142
143Most actions do not require any arguments, and so you can bind them as strings: `"ctrl-a": "language_selector::Toggle"`. Some require a single argument and must be bound as an array: `"cmd-1": ["workspace::ActivatePane", 0]`. Some actions require multiple arguments and are bound as an array of a string and an object: `"ctrl-a": ["pane::DeploySearch", { "replace_enabled": true }]`.
144
145### Precedence
146
147When multiple keybindings have the same keystroke and are active at the same time, precedence is resolved in two ways:
148
149- Bindings that match on lower nodes in the context tree win. This means that if you have a binding with a context of `Editor`, it will take precedence over a binding with a context of `Workspace`. Bindings with no context match at the lowest level in the tree.
150- If there are multiple bindings that match at the same level in the tree, then the binding defined later takes precedence. As user keybindings are loaded after system keybindings, this allows user bindings to take precedence over built-in keybindings.
151
152The other kind of conflict that arises is when you have two bindings, one of which is a prefix of the other. For example, if you have `"ctrl-w":"editor::DeleteToNextWordEnd"` and `"ctrl-w left":"editor::DeleteToEndOfLine"`.
153
154When this happens, and both bindings are active in the current context, Zed will wait for 1 second after you type `ctrl-w` to see if you're about to type `left`. If you don't type anything, or if you type a different key, then `DeleteToNextWordEnd` will be triggered. If you do, then `DeleteToEndOfLine` will be triggered.
155
156### Non-QWERTY keyboards
157
158Zed's support for non-QWERTY keyboards is still a work in progress.
159
160If your keyboard can type the full ASCII range (DVORAK, COLEMAK, etc.), then shortcuts should work as you expect.
161
162Otherwise, read on...
163
164#### macOS
165
166On Cyrillic, Hebrew, Armenian, and other keyboards that are mostly non-ASCII, macOS automatically maps keys to the ASCII range when `cmd` is held. Zed takes this a step further, and it can always match key-presses against either the ASCII layout or the real layout, regardless of modifiers and the `use_key_equivalents` setting. For example, in Thai, pressing `ctrl-ๆ` will match bindings associated with `ctrl-q` or `ctrl-ๆ`.
167
168On keyboards that support extended Latin alphabets (French AZERTY, German QWERTZ, etc.), it is often not possible to type the entire ASCII range without `option`. This introduces an ambiguity: `option-2` produces `@`. To ensure that all the built-in keyboard shortcuts can still be typed on these keyboards, we move key bindings around. For example, shortcuts bound to `@` on QWERTY are moved to `"` on a Spanish layout. This mapping is based on the macOS system defaults and can be seen by running `dev: open key context view` from the command palette.
169
170If you are defining shortcuts in your personal keymap, you can opt into the key equivalent mapping by setting `use_key_equivalents` to `true` in your keymap:
171
172```json [keymap]
173[
174  {
175    "use_key_equivalents": true,
176    "bindings": {
177      "ctrl->": "editor::Indent" // parsed as ctrl-: when a German QWERTZ keyboard is active
178    }
179  }
180]
181```
182
183### Linux
184
185Since v0.196.0, on Linux, if the key that you type doesn't produce an ASCII character, then we use the QWERTY-layout equivalent key for keyboard shortcuts. This means that many shortcuts can be typed on many layouts.
186
187We do not yet move shortcuts around to ensure that all the built-in shortcuts can be typed on every layout, so if there are some ASCII characters that cannot be typed, and your keyboard layout has different ASCII characters on the same keys as would be needed to type them, you may need to add custom key bindings to make this work. We do intend to fix this at some point, and help is very much appreciated!
188
189## Tips and tricks
190
191### Disabling a binding
192
193If you'd like a given binding to do nothing in a given context, you can use
194`null` as the action. This is useful if you hit the key binding by accident and
195want to disable it, or if you want to type the character that would be typed by
196the sequence, or if you want to disable multikey bindings starting with that key.
197
198```json [keymap]
199[
200  {
201    "context": "Workspace",
202    "bindings": {
203      "cmd-r": null // cmd-r will do nothing when the Workspace context is active
204    }
205  }
206]
207```
208
209A `null` binding follows the same precedence rules as normal actions, so it disables all bindings that would match further up in the tree too. If you'd like a binding that matches further up in the tree to take precedence over a lower binding, you need to rebind it to the action you want in the context you want.
210
211This is useful for preventing Zed from falling back to a default key binding when the action you specified is conditional and propagates. For example, `buffer_search::DeployReplace` only triggers when the search bar is not in view. If the search bar is in view, it would propagate and trigger the default action set for that key binding, such as opening the right dock. To prevent this from happening:
212
213```json [keymap]
214[
215  {
216    "context": "Workspace",
217    "bindings": {
218      "cmd-r": null // cmd-r will do nothing when the search bar is in view
219    }
220  },
221  {
222    "context": "Workspace",
223    "bindings": {
224      "cmd-r": "buffer_search::DeployReplace" // cmd-r will deploy replace when the search bar is not in view
225    }
226  }
227]
228```
229
230### Remapping keys
231
232A common request is to be able to map from a single keystroke to a sequence. You can do this with the `workspace::SendKeystrokes` action.
233
234```json [keymap]
235[
236  {
237    "bindings": {
238      // Move down four times
239      "alt-down": ["workspace::SendKeystrokes", "down down down down"],
240      // Expand the selection (editor::SelectLargerSyntaxNode);
241      // copy to the clipboard; and then undo the selection expansion.
242      "cmd-alt-c": [
243        "workspace::SendKeystrokes",
244        "ctrl-shift-right ctrl-shift-right ctrl-shift-right cmd-c ctrl-shift-left ctrl-shift-left ctrl-shift-left"
245      ]
246    }
247  },
248  {
249    "context": "Editor && vim_mode == insert",
250    "bindings": {
251      "j k": ["workspace::SendKeystrokes", "escape"]
252    }
253  }
254]
255```
256
257There are some limitations to this, notably:
258
259- Any asynchronous operation will not happen until after all your key bindings have been dispatched. For example, this means that while you can use a binding to open a file (as in the `cmd-alt-r` example), you cannot send further keystrokes and hope to have them interpreted by the new view.
260- Other examples of asynchronous things are: opening the command palette, communicating with a language server, changing the language of a buffer, anything that hits the network.
261- There is a limit of 100 simulated keys at a time.
262
263The argument to `SendKeystrokes` is a space-separated list of keystrokes (using the same syntax as above). Due to the way that keystrokes are parsed, any segment that is not recognized as a keypress will be sent verbatim to the currently focused input field.
264
265If the argument to `SendKeystrokes` contains the binding used to trigger it, it will use the next-highest-precedence definition of that binding. This allows you to extend the default behavior of a key binding.
266
267### Forward keys to terminal
268
269If you're on Linux or Windows, you might find yourself wanting to forward key combinations to the built-in terminal instead of them being handled by Zed.
270
271For example, `ctrl-n` creates a new tab in Zed on Linux. If you want to send `ctrl-n` to the built-in terminal when it's focused, add the following to your keymap:
272
273```json [settings]
274{
275  "context": "Terminal",
276  "bindings": {
277    "ctrl-n": ["terminal::SendKeystroke", "ctrl-n"]
278  }
279}
280```
281
282### Task Key bindings
283
284You can also bind keys to launch Zed Tasks defined in your `tasks.json`.
285See the [tasks documentation](tasks.md#custom-keybindings-for-tasks) for more.