1# Vim Mode
2
3Zed includes a Vim emulation layer known as "vim mode". On this page, you will learn how to turn Zed's vim mode on or off, what tools and commands Zed provides to help you navigate and edit your code, and generally how to make the most of vim mode in Zed.
4
5You'll learn how to:
6
7- Understand the core differences between Zed's vim mode and traditional Vim
8- Enable or disable vim mode
9- Make the most of Zed-specific features within vim mode
10- Customize vim mode key bindings
11- Configure vim mode settings
12
13Whether you're new to vim mode or an experienced Vim user looking to optimize your Zed experience, this guide will help you harness the full power of modal editing in Zed.
14
15## Zed's vim mode design
16
17Vim mode tries to offer a familiar experience to Vim users: it replicates the behavior of motions and commands precisely when it makes sense and uses Zed-specific functionality to provide an editing experience that "just works" without requiring configuration on your part.
18
19This includes support for semantic navigation, multiple cursors, or other features usually provided by plugins like surrounding text.
20
21So, Zed's vim mode does not replicate Vim one-to-one, but it meshes Vim's modal design with Zed's modern features to provide a more fluid experience. It's also configurable, so you can add your own key bindings or override the defaults.
22
23### Core differences
24
25There are four types of features in vim mode that use Zed's core functionality, leading to some differences in behavior:
26
271. **Motions**: vim mode uses Zed's semantic parsing to tune the behavior of motions per language. For example, in Rust, jumping to matching bracket with `%` works with the pipe character `|`. In JavaScript, `w` considers `$` to be a word character.
282. **Visual block selections**: vim mode uses Zed's multiple cursor to emulate visual block selections, making block selections a lot more flexible. For example, anything you insert after a block selection updates on every line in real-time, and you can add or remove cursors anytime.
293. **Macros**: vim mode uses Zed's recording system for vim macros. So, you can capture and replay more complex actions, like autocompletion.
304. **Search and replace**: vim mode uses Zed's search system, so, the syntax for regular expressions is slightly different compared to Vim. [Head to the Regex differences section](#regex-differences) for details.
31
32> **Note:** The foundations of Zed's vim mode should already cover many use cases, and we're always looking to improve it. If you find missing features that you rely on in your workflow, please [file an issue on GitHub](https://github.com/zed-industries/zed/issues).
33
34## Enabling and disabling vim mode
35
36When you first open Zed, you'll see a checkbox on the welcome screen that allows you to enable vim mode.
37
38If you missed this, you can toggle vim mode on or off anytime by opening the command palette and using the workspace command `toggle vim mode`.
39
40> **Note**: This command toggles the following property in your user settings:
41>
42> ```json
43> {
44> "vim_mode": true
45> }
46> ```
47
48## Zed-specific features
49
50Zed is built on a modern foundation that (among other things) uses tree-sitter and language servers to understand the content of the file you're editing and supports multiple cursors out of the box.
51
52Vim mode has several "core Zed" key bindings that will help you make the most of Zed's specific feature set.
53
54### Language server
55
56The following commands use the language server to help you navigate and refactor your code.
57
58| Command | Default Shortcut |
59| ---------------------------------------- | ---------------- |
60| Go to definition | `g d` |
61| Go to declaration | `g D` |
62| Go to type definition | `g y` |
63| Go to implementation | `g I` |
64| Rename (change definition) | `c d` |
65| Go to All references to the current word | `g A` |
66| Find symbol in current file | `g s` |
67| Find symbol in entire project | `g S` |
68| Go to next diagnostic | `g ]` or `] d` |
69| Go to previous diagnostic | `g [` or `[ d` |
70| Show inline error (hover) | `g h` |
71| Open the code actions menu | `g .` |
72
73### Git
74
75| Command | Default Shortcut |
76| ------------------------------- | ---------------- |
77| Go to next git change | `] c` |
78| Go to previous git change | `[ c` |
79| Expand diff hunk | `d o` |
80| Toggle staged | `d O` |
81| Stage and next (in diff view) | `d u` |
82| Unstage and next (in diff view) | `d U` |
83| Restore change | `d p` |
84
85### Treesitter
86
87Treesitter is a powerful tool that Zed uses to understand the structure of your code. Zed provides motions that change the current cursor position, and text objects that can be used as the target of actions.
88
89| Command | Default Shortcut |
90| ------------------------------- | --------------------------- |
91| Go to next/previous method | `] m` / `[ m` |
92| Go to next/previous method end | `] M` / `[ M` |
93| Go to next/previous section | `] ]` / `[ [` |
94| Go to next/previous section end | `] [` / `[ ]` |
95| Go to next/previous comment | `] /`, `] *` / `[ /`, `[ *` |
96| Select a larger syntax node | `[ x` |
97| Select a smaller syntax node | `] x` |
98
99| Text Objects | Default Shortcut |
100| ---------------------------------------------------------- | ---------------- |
101| Around a class, definition, etc. | `a c` |
102| Inside a class, definition, etc. | `i c` |
103| Around a function, method etc. | `a f` |
104| Inside a function, method, etc. | `i f` |
105| A comment | `g c` |
106| An argument, or list item, etc. | `i a` |
107| An argument, or list item, etc. (including trailing comma) | `a a` |
108| Around an HTML-like tag | `a t` |
109| Inside an HTML-like tag | `i t` |
110| The current indent level, and one line before and after | `a I` |
111| The current indent level, and one line before | `a i` |
112| The current indent level | `i i` |
113
114Note that the definitions for the targets of the `[m` family of motions are the same as the
115boundaries defined by `af`. The targets of the `[[` are the same as those defined by `ac`, though
116if there are no classes, then functions are also used. Similarly `gc` is used to find `[ /`. `g c`
117
118The definition of functions, classes and comments is language dependent, and support can be added
119to extensions by adding a [`textobjects.scm`]. The definition of arguments and tags operates at
120the tree-sitter level, but looks for certain patterns in the parse tree and is not currently configurable
121per language.
122
123### Multi cursor
124
125These commands help you manage multiple cursors in Zed.
126
127| Command | Default Shortcut |
128| ------------------------------------------------------------ | ---------------- |
129| Add a cursor selecting the next copy of the current word | `g l` |
130| Add a cursor selecting the previous copy of the current word | `g L` |
131| Skip latest word selection, and add next | `g >` |
132| Skip latest word selection, and add previous | `g <` |
133| Add a visual selection for every copy of the current word | `g a` |
134
135### Pane management
136
137These commands open new panes or jump to specific panes.
138
139| Command | Default Shortcut |
140| ------------------------------------------ | ------------------ |
141| Open a project-wide search | `g /` |
142| Open the current search excerpt | `g <space>` |
143| Open the current search excerpt in a split | `<ctrl-w> <space>` |
144| Go to definition in a split | `<ctrl-w> g d` |
145| Go to type definition in a split | `<ctrl-w> g D` |
146
147### In insert mode
148
149The following commands help you bring up Zed's completion menu, request a suggestion from GitHub Copilot, or open the inline AI assistant without leaving insert mode.
150
151| Command | Default Shortcut |
152| ---------------------------------------------------------------------------- | ---------------- |
153| Open the completion menu | `ctrl-x ctrl-o` |
154| Request GitHub Copilot suggestion (requires GitHub Copilot to be configured) | `ctrl-x ctrl-c` |
155| Open the inline AI assistant (requires a configured assistant) | `ctrl-x ctrl-a` |
156| Open the code actions menu | `ctrl-x ctrl-l` |
157| Hides all suggestions | `ctrl-x ctrl-z` |
158
159### Supported plugins
160
161Zed's vim mode includes some features that are usually provided by very popular plugins in the Vim ecosystem:
162
163- You can surround text objects with `ys` (yank surround), change surrounding with `cs`, and delete surrounding with `ds`.
164- You can comment and uncomment selections with `gc` in visual mode and `gcc` in normal mode.
165- The project panel supports many shortcuts modeled after the Vim plugin `netrw`: navigation with `hjkl`, open file with `o`, open file in a new tab with `t`, etc.
166- You can add key bindings to your keymap to navigate "camelCase" names. [Head down to the Optional key bindings](#optional-key-bindings) section to learn how.
167- You can use `gR` to do [ReplaceWithRegister](https://github.com/vim-scripts/ReplaceWithRegister).
168- You can use `cx` for [vim-exchange](https://github.com/tommcdo/vim-exchange) functionality. Note that it does not have a default binding in visual mode, but you can add one to your keymap (refer to the [optional key bindings](#optional-key-bindings) section).
169- You can navigate to indent depths relative to your cursor with the [indent wise](https://github.com/jeetsukumaran/vim-indentwise) plugin `[-`, `]-`, `[+`, `]+`, `[=`, `]=`.
170
171## Command palette
172
173Vim mode allows you to open Zed's command palette with `:`. You can then type to access any usual Zed command. Additionally, vim mode adds aliases for popular Vim commands to ensure your muscle memory transfers to Zed. For example, you can write `:w` or `:write` to save the file.
174
175Below, you'll find tables listing the commands you can use in the command palette. We put optional characters in square brackets to indicate that you can omit them.
176
177> **Note**: We don't emulate the full power of Vim's command line yet. In particular, commands currently do not support arguments. Please [file issues on GitHub](https://github.com/zed-industries/zed) as you find things that are missing from the command palette.
178
179### File and window management
180
181This table shows commands for managing windows, tabs, and panes. As commands don't support arguments currently, you cannot specify a filename when saving or creating a new file.
182
183| Command | Description |
184| -------------- | ---------------------------------------------------- |
185| `:w[rite][!]` | Save the current file |
186| `:wq[!]` | Save the file and close the buffer |
187| `:q[uit][!]` | Close the buffer |
188| `:wa[ll][!]` | Save all open files |
189| `:wqa[ll][!]` | Save all open files and close all buffers |
190| `:qa[ll][!]` | Close all buffers |
191| `:[e]x[it][!]` | Close the buffer |
192| `:up[date]` | Save the current file |
193| `:cq` | Quit completely (close all running instances of Zed) |
194| `:vs[plit]` | Split the pane vertically |
195| `:sp[lit]` | Split the pane horizontally |
196| `:new` | Create a new file in a horizontal split |
197| `:vne[w]` | Create a new file in a vertical split |
198| `:tabedit` | Create a new file in a new tab |
199| `:tabnew` | Create a new file in a new tab |
200| `:tabn[ext]` | Go to the next tab |
201| `:tabp[rev]` | Go to previous tab |
202| `:tabc[lose]` | Close the current tab |
203| `:ls` | Show all buffers |
204
205> **Note:** The `!` character is used to force the command to execute without saving changes or prompting before overwriting a file.
206
207### Ex commands
208
209These ex commands open Zed's various panels and windows.
210
211| Command | Default Shortcut |
212| ---------------------------- | ---------------- |
213| Open the project panel | `:E[xplore]` |
214| Open the collaboration panel | `:C[ollab]` |
215| Open the chat panel | `:Ch[at]` |
216| Open the AI panel | `:A[I]` |
217| Open the git panel | `:G[it]` |
218| Open the notifications panel | `:No[tif]` |
219| Open the feedback window | `:fe[edback]` |
220| Open the diagnostics window | `:cl[ist]` |
221| Open the terminal | `:te[rm]` |
222| Open the extensions window | `:Ext[ensions]` |
223
224### Navigating diagnostics
225
226These commands navigate diagnostics.
227
228| Command | Description |
229| ------------------------ | ------------------------------ |
230| `:cn[ext]` or `:ln[ext]` | Go to the next diagnostic |
231| `:cp[rev]` or `:lp[rev]` | Go to the previous diagnostics |
232| `:cc` or `:ll` | Open the errors page |
233
234### Git
235
236These commands interact with the version control system git.
237
238| Command | Description |
239| --------------- | ------------------------------------------------------- |
240| `:dif[fupdate]` | View the diff under the cursor (`d o` in normal mode) |
241| `:rev[ert]` | Revert the diff under the cursor (`d p` in normal mode) |
242
243### Jump
244
245These commands jump to specific positions in the file.
246
247| Command | Description |
248| ------------------- | ----------------------------------- |
249| `:<number>` | Jump to a line number |
250| `:$` | Jump to the end of the file |
251| `:/foo` and `:?foo` | Jump to next/prev line matching foo |
252
253### Replacement
254
255This command replaces text. It emulates the substitute command in vim. The substitute command uses regular expressions, and Zed uses a slightly different syntax than vim. You can learn more about Zed's syntax below, [in the regex differences section](#regex-differences). Zed will replace only the first occurrence of the search pattern in the current line. To replace all matches append the `g` flag.
256
257| Command | Description |
258| ----------------------- | --------------------------------- |
259| `:[range]s/foo/bar/[g]` | Replace instances of foo with bar |
260
261### Editing
262
263These commands help you edit text.
264
265| Command | Description |
266| ----------------- | ------------------------------------------------------- |
267| `:j[oin]` | Join the current line |
268| `:d[elete][l][p]` | Delete the current line |
269| `:s[ort] [i]` | Sort the current selection (with i, case-insensitively) |
270| `:y[ank]` | Yank (copy) the current selection or line |
271
272### Set
273
274These commands modify editor options locally for the current buffer.
275
276| Command | Description |
277| ------------------------------- | --------------------------------------------------------------------------------------------- |
278| `:se[t] [no]wrap` | Lines longer than the width of the window will wrap and displaying continues on the next line |
279| `:se[t] [no]nu[mber]` | Print the line number in front of each line |
280| `:se[t] [no]r[elative]nu[mber]` | Changes the displayed number to be relative to the cursor |
281
282### Command mnemonics
283
284As any Zed command is available, you may find that it's helpful to remember mnemonics that run the correct command. For example:
285
286- `:diffs` for "toggle all hunk diffs"
287- `:cpp` for "copy path to file"
288- `:crp` for "copy relative path"
289- `:reveal` for "reveal in finder"
290- `:zlog` for "open zed log"
291- `:clank` for "cancel language server work"
292
293## Customizing key bindings
294
295In this section, we'll learn how to customize the key bindings of Zed's vim mode. You'll learn:
296
297- How to select the correct context for your new key bindings.
298- Useful contexts for vim mode key bindings.
299- Common key bindings to customize for extra productivity.
300
301### Selecting the correct context
302
303Zed's key bindings are evaluated only when the `"context"` property matches your location in the editor. For example, if you add key bindings to the `"Editor"` context, they will only work when you're editing a file. If you add key bindings to the `"Workspace"` context, they will work everywhere in Zed. Here's an example of a key binding that saves when you're editing a file:
304
305```json
306{
307 "context": "Editor",
308 "bindings": {
309 "ctrl-s": "file::Save"
310 }
311}
312```
313
314Contexts are nested, so when you're editing a file, the context is the `"Editor"` context, which is inside the `"Pane"` context, which is inside the `"Workspace"` context. That's why any key bindings you add to the `"Workspace"` context will work when you're editing a file. Here's an example:
315
316```json
317// This key binding will work when you're editing a file. It comes built into Zed by default as the workspace: save command.
318{
319 "context": "Workspace",
320 "bindings": {
321 "ctrl-s": "file::Save"
322 }
323}
324```
325
326Contexts are expressions. They support boolean operators like `&&` (and) and `||` (or). For example, you can use the context `"Editor && vim_mode == normal"` to create key bindings that only work when you're editing a file _and_ you're in vim's normal mode.
327
328Vim mode adds several contexts to the `"Editor"` context:
329
330| Operator | Description |
331| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
332| VimControl | Indicates that vim keybindings should work. Currently an alias for `vim_mode == normal \|\| vim_mode == visual \|\| vim_mode == operator`, but the definition may change over time |
333| vim_mode == normal | Normal mode |
334| vim_mode == visual | Visual mode |
335| vim_mode == insert | Insert mode |
336| vim_mode == replace | Replace mode |
337| vim_mode == waiting | Waiting for an arbitrary key (e.g., after typing `f` or `t`) |
338| vim_mode == operator | Waiting for another binding to trigger (e.g., after typing `c` or `d`) |
339| vim_operator | Set to `none` unless `vim_mode == operator`, in which case it is set to the current operator's default keybinding (e.g., after typing `d`, `vim_operator == d`) |
340
341> **Note**: Contexts are matched only on one level at a time. So it is possible to use the expression `"Editor && vim_mode == normal"`, but `"Workspace && vim_mode == normal"` will never match because we set the vim context at the `"Editor"` level.
342
343### Useful contexts for vim mode key bindings
344
345Here's a template with useful vim mode contexts to help you customize your vim mode key bindings. You can copy it and integrate it into your user keymap.
346
347```json
348[
349 {
350 "context": "VimControl && !menu",
351 "bindings": {
352 // Put key bindings here if you want them to work in normal & visual mode.
353 }
354 },
355 {
356 "context": "vim_mode == normal && !menu",
357 "bindings": {
358 // "shift-y": ["workspace::SendKeystrokes", "y $"] // Use neovim's yank behavior: yank to end of line.
359 }
360 },
361 {
362 "context": "vim_mode == insert",
363 "bindings": {
364 // "j k": "vim::NormalBefore" // In insert mode, make jk escape to normal mode.
365 }
366 },
367 {
368 "context": "EmptyPane || SharedScreen",
369 "bindings": {
370 // Put key bindings here (in addition to the context above) if you want them to
371 // work when no editor exists.
372 // "space f": "file_finder::Toggle"
373 }
374 }
375]
376```
377
378> **Note**: If you would like to emulate Vim's `map` commands (`nmap`, etc.), you can use the action `workspace::SendKeystrokes` in the correct context.
379
380### Optional key bindings
381
382By default, you can navigate between the different files open in the editor with shortcuts like `ctrl+w` followed by one of `hjkl` to move to the left, down, up, or right, respectively.
383
384But you cannot use the same shortcuts to move between all the editor docks (the terminal, project panel, assistant panel, ...). If you want to use the same shortcuts to navigate to the docks, you can add the following key bindings to your user keymap.
385
386```json
387{
388 "context": "Dock",
389 "bindings": {
390 "ctrl-w h": "workspace::ActivatePaneLeft",
391 "ctrl-w l": "workspace::ActivatePaneRight",
392 "ctrl-w k": "workspace::ActivatePaneUp",
393 "ctrl-w j": "workspace::ActivatePaneDown"
394 // ... or other keybindings
395 }
396}
397```
398
399Subword motion, which allows you to navigate and select individual words in camelCase or snake_case, is not enabled by default. To enable it, add these bindings to your keymap.
400
401```json
402{
403 "context": "VimControl && !menu && vim_mode != operator",
404 "bindings": {
405 "w": "vim::NextSubwordStart",
406 "b": "vim::PreviousSubwordStart",
407 "e": "vim::NextSubwordEnd",
408 "g e": "vim::PreviousSubwordEnd"
409 }
410}
411```
412
413Vim mode comes with shortcuts to surround the selection in normal mode (`ys`), but it doesn't have a shortcut to add surrounds in visual mode. By default, `shift-s` substitutes the selection (erases the text and enters insert mode). To use `shift-s` to add surrounds in visual mode, you can add the following object to your keymap.
414
415```json
416{
417 "context": "vim_mode == visual",
418 "bindings": {
419 "shift-s": ["vim::PushAddSurrounds", {}]
420 }
421}
422```
423
424In non-modal text editors, cursor navigation typically wraps when moving past line ends. Zed, however, handles this behavior exactly like Vim by default: the cursor stops at line boundaries. If you prefer your cursor to wrap between lines, override these keybindings:
425
426```json
427// In VimScript, this would look like this:
428// set whichwrap+=<,>,[,],h,l
429{
430 "context": "VimControl && !menu",
431 "bindings": {
432 "left": "vim::WrappingLeft",
433 "right": "vim::WrappingRight",
434 "h": "vim::WrappingLeft",
435 "l": "vim::WrappingRight"
436 }
437}
438```
439
440The [Sneak motion](https://github.com/justinmk/vim-sneak) feature allows for quick navigation to any two-character sequence in your text. You can enable it by adding the following keybindings to your keymap. By default, the `s` key is mapped to `vim::Substitute`. Adding these bindings will override that behavior, so ensure this change aligns with your workflow preferences.
441
442```json
443{
444 "context": "vim_mode == normal || vim_mode == visual",
445 "bindings": {
446 "s": "vim::PushSneak",
447 "shift-s": "vim::PushSneakBackward"
448 }
449}
450```
451
452The [vim-exchange](https://github.com/tommcdo/vim-exchange) feature does not have a default binding for visual mode, as the `shift-x` binding conflicts with the default `shift-x` binding for visual mode (`vim::VisualDeleteLine`). To assign the default vim-exchange binding, add the following keybinding to your keymap:
453
454```json
455{
456 "context": "vim_mode == visual",
457 "bindings": {
458 "shift-x": "vim::Exchange"
459 }
460}
461```
462
463### Restoring common text editing keybindings
464
465If you're using vim mode on Linux or Windows, you may find it overrides keybindings you can't live without: `ctrl+v` to paste, `ctrl+f` to search, etc. You can restore them by copying this data into your keymap:
466
467```json
468{
469 "context": "Editor && !menu",
470 "bindings": {
471 "ctrl-c": "editor::Copy", // vim default: return to normal mode
472 "ctrl-x": "editor::Cut", // vim default: decrement
473 "ctrl-v": "editor::Paste", // vim default: visual block mode
474 "ctrl-y": "editor::Undo", // vim default: line up
475 "ctrl-f": "buffer_search::Deploy", // vim default: page down
476 "ctrl-o": "workspace::Open", // vim default: go back
477 "ctrl-a": "editor::SelectAll", // vim default: increment
478 }
479},
480```
481
482## Changing vim mode settings
483
484You can change the following settings to modify vim mode's behavior:
485
486| Property | Description | Default Value |
487| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- |
488| default_mode | The default mode to start in. One of "normal", "insert", "replace", "visual", "visual_line", "visual_block", "helix_normal". | "normal" |
489| use_system_clipboard | Determines how system clipboard is used:<br><ul><li>"always": use for all operations</li><li>"never": only use when explicitly specified</li><li>"on_yank": use for yank operations</li></ul> | "always" |
490| use_multiline_find | If `true`, `f` and `t` motions extend across multiple lines. | false |
491| use_smartcase_find | If `true`, `f` and `t` motions are case-insensitive when the target letter is lowercase. | false |
492| toggle_relative_line_numbers | If `true`, line numbers are relative in normal mode and absolute in insert mode, giving you the best of both options. | false |
493| custom_digraphs | An object that allows you to add custom digraphs. Read below for an example. | {} |
494| highlight_on_yank_duration | The duration of the highlight animation(in ms). Set to `0` to disable | 200 |
495
496Here's an example of adding a digraph for the zombie emoji. This allows you to type `ctrl-k f z` to insert a zombie emoji. You can add as many digraphs as you like.
497
498```json
499{
500 "vim": {
501 "custom_digraphs": {
502 "fz": "🧟♀️"
503 }
504 }
505}
506```
507
508Here's an example of these settings changed:
509
510```json
511{
512 "vim": {
513 "default_mode": "insert",
514 "use_system_clipboard": "never",
515 "use_multiline_find": true,
516 "use_smartcase_find": true,
517 "toggle_relative_line_numbers": true,
518 "highlight_on_yank_duration": 50,
519 "custom_digraphs": {
520 "fz": "🧟♀️"
521 }
522 }
523}
524```
525
526## Useful core Zed settings for vim mode
527
528Here are a few general Zed settings that can help you fine-tune your Vim experience:
529
530| Property | Description | Default Value |
531| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------- |
532| cursor_blink | If `true`, the cursor blinks. | `true` |
533| relative_line_numbers | If `true`, line numbers in the left gutter are relative to the cursor. | `false` |
534| scrollbar | Object that controls the scrollbar display. Set to `{ "show": "never" }` to hide the scroll bar. | `{ "show": "auto" }` |
535| scroll_beyond_last_line | If set to `"one_page"`, allows scrolling up to one page beyond the last line. Set to `"off"` to prevent this behavior. | `"one_page"` |
536| vertical_scroll_margin | The number of lines to keep above or below the cursor when scrolling. Set to `0` to allow the cursor to go up to the edges of the screen vertically. | `3` |
537| gutter.line_numbers | Controls the display of line numbers in the gutter. Set the `"line_numbers"` property to `false` to hide line numbers. | `true` |
538| command_aliases | Object that defines aliases for commands in the command palette. You can use it to define shortcut names for commands you use often. Read below for examples. | `{}` |
539
540Here's an example of these settings changed:
541
542```json
543{
544 // Disable cursor blink
545 "cursor_blink": false,
546 // Use relative line numbers
547 "relative_line_numbers": true,
548 // Hide the scroll bar
549 "scrollbar": { "show": "never" },
550 // Prevent the buffer from scrolling beyond the last line
551 "scroll_beyond_last_line": "off",
552 // Allow the cursor to reach the edges of the screen
553 "vertical_scroll_margin": 0,
554 "gutter": {
555 // Disable line numbers completely:
556 "line_numbers": false
557 },
558 "command_aliases": {
559 "W": "w",
560 "Wq": "wq",
561 "Q": "q"
562 }
563}
564```
565
566The `command_aliases` property is a single object that maps keys or key sequences to vim mode commands. The example above defines multiple aliases: `W` for `w`, `Wq` for `wq`, and `Q` for `q`.
567
568## Regex differences
569
570Zed uses a different regular expression engine from Vim. This means that you will have to use a different syntax in some cases. Here are the most common differences:
571
572- **Capture groups**: Vim uses `\(` and `\)` to represent capture groups, in Zed these are `(` and `)`. On the flip side, in Vim, `(` and `)` represent literal parentheses, but in Zed these must be escaped to `\(` and `\)`.
573- **Matches**: When replacing, Vim uses the backslash character followed by a number to represent a matched capture group. For example, `\1`. Zed uses the dollar sign instead. So, when in Vim you use `\0` to represent the entire match, in Zed the syntax is `$0` instead. Same for numbered capture groups: `\1` in Vim is `$1` in Zed.
574- **Global option**: By default, in Vim, regex searches only match the first occurrence on a line, and you append `/g` at the end of your query to find all matches. In Zed, regex searches are global by default.
575- **Case sensitivity**: Vim uses `/i` to indicate a case-insensitive search. In Zed you can either write `(?i)` at the start of the pattern or toggle case-sensitivity with the shortcut {#kb search::ToggleCaseSensitive}.
576
577> **Note**: To help with the transition, the command palette will fix parentheses and replace groups for you when you write a Vim-style substitute command, `:%s//`. So, Zed will convert `%s:/\(a\)(b)/\1/` into a search for "(a)\(b\)" and a replacement of "$1".
578
579For the full syntax supported by Zed's regex engine [see the regex crate documentation](https://docs.rs/regex/latest/regex/#syntax).