VSCode Neovim
VSCode Neovim Integration
[Neovim](https://neovim.io/) is a fork of VIM to allow greater extensibility and integration. This extension uses a full
embedded Neovim instance, no more half-complete VIM emulation! VSCode's native functionality is used for insert mode and
editor commands, making the best use of both editors.
- 🎉 Almost fully feature-complete VIM integration by utilizing neovim as a backend.
- 🔧 Supports custom `init.vim` and many vim plugins.
- 🥇 First-class and lag-free insert mode, letting VSCode do what it does best.
- 🤝 Complete integration with VSCode features (lsp/autocompletion/snippets/multi-cursor/etc).
Table of Contents (click to expand)
- [🧰 Installation](#-installation)
- [💡 Tips and Features](#-tips-and-features)
- [Important](#important)
- [VSCode specific differences](#vscode-specific-differences)
- [Performance problems](#performance-problems)
- [Conditional init.vim](#conditional-initvim)
- [Custom escape keys](#custom-escape-keys)
- [Jumplist](#jumplist)
- [Wildmenu completion](#wildmenu-completion)
- [Multiple cursors](#multiple-cursors)
- [Keyboard Quickfix](#keyboard-quickfix)
- [Invoking VSCode actions from neovim](#invoking-vscode-actions-from-neovim)
- [Examples](#examples)
- [⌨️ Bindings](#️-bindings)
- [File management](#file-management)
- [Tab management](#tab-management)
- [Buffer/window management](#bufferwindow-management)
- [Insert mode special keys](#insert-mode-special-keys)
- [Normal mode control keys](#normal-mode-control-keys)
- [Cmdline special keys](#cmdline-special-keys)
- [VSCode specific bindings](#vscode-specific-bindings)
- [Editor command](#editor-command)
- [Explorer/list navigation](#explorerlist-navigation)
- [Explorer file manipulation](#explorer-file-manipulation)
- [Custom keybindings](#custom-keybindings)
- [🤝 Vim Plugins](#-vim-plugins)
- [vim-easymotion](#vim-easymotion)
- [vim-commentary](#vim-commentary)
- [quick-scope](#quick-scope)
- [📑 How it works](#-how-it-works)
- [❤️ Credits & External Resources](#️-credits--external-resources)
## 🧰 Installation
- Install the [vscode-neovim](https://marketplace.visualstudio.com/items?itemName=asvetliakov.vscode-neovim)
extension.
- Install [Neovim](https://github.com/neovim/neovim/wiki/Installing-Neovim) **0.5.0 nightly** or greater.
- Set the neovim path in the extension settings. You must specify full path to neovim, like
"`C:\Neovim\bin\nvim.exe"` or "`/usr/local/bin/nvim`".
- The setting id is "`vscode-neovim.neovimExecutablePaths.win32/linux/darwin`", respective to your system.
- If you want to use neovim from WSL, set the `useWSL` configuration toggle and specify linux path to nvim binary.
`wsl.exe` windows binary and `wslpath` linux binary are required for this. `wslpath` must be available through
`$PATH` linux env setting. Use `wsl --list` to check for the correct default linux distribution.
> ❗ **Neovim 0.5.0 nightly** or greater is **required**. Any version lower than that won't work. Many linux
> distributions have an **old** version of neovim in their package repo - always check what version are you installing.
> You can install neovim separately, outside your system's package manager installation, for example using the appimage
> from the neovim releases page.
> 🐛 See the [issues section](https://github.com/asvetliakov/vscode-neovim/issues) for known issues.
## 💡 Tips and Features
### Important
- If you get "Unable to init vscode-neovim: command 'type' already exists" message, uninstall other VSCode extensions
that register the `type` command (like
[VSCodeVim](https://marketplace.visualstudio.com/items?itemName=vscodevim.vim) or
[Overtype](https://marketplace.visualstudio.com/items?itemName=adammaras.overtype)).
- If you already have a big `init.vim` it is recommended to wrap existing settings & plugins with
[`if !exists('g:vscode')`](#conditional-initvim) to prevent potential conflicts. If you have any problems, try with
empty `init.vim` first.
- On a Mac, the h, j, k and l movement keys may not repeat when held, to
fix this open Terminal and execute the following command:
`defaults write com.microsoft.VSCode ApplePressAndHoldEnabled -bool false`.
- The extension works best if `editor.scrollBeyondLastLine` is disabled.
### VSCode specific differences
- File and editor management commands such as `:e`/`:w`/`:q`/`:vsplit`/`:tabnext`/etc are mapped to corresponding
vscode commands and behavior may be different ([see below](#️-bindings)). **Do not** use vim commands like `:w` in
scripts/keybindings, they won't work. If you're using them in some custom commands/mappings, you might need to
rebind them to call vscode commands from neovim with `VSCodeCall/VSCodeNotify`
([see below](#invoking-vscode-actions-from-neovim)).
- Visual modes don't produce vscode selections, so any vscode commands expecting selection won't work. To round the
corners, invoking the VSCode command picker from visual mode through the default hotkeys
(f1/ctrl/cmd+shift+p) converts vim selection to real vscode selection. This conversion is also
done automatically for some commands like commenting and formatting. If you're using some custom mapping for calling
vscode commands that depends on real vscode selection, you can use `VSCodeNotifyRange`/`VSCodeNotifyRangePos` (the
first one linewise, the latter characterwise) which will convert vim visual mode selection to vscode selection
before calling the command ([see below](#invoking-vscode-actions-from-neovim)).
- When you type some commands they may be substituted for the another, like `:write` will be replaced by `:Write`.
This is normal.
- Scrolling is done by VSCode. C-d/C-u/etc are slightly different.
- Editor customization (relative line number, scrolloff, etc) is handled by VSCode.
- Dot-repeat (.) is slightly different - moving the cursor within a change range won't break the repeat
sequence. In neovim, if you type `abc` in insert mode, then move cursor to `abc` and type `1` here
the repeat sequence would be `1`. However in vscode it would be `a1bc`. Another difference is that when you delete
some text in insert mode, dot repeat only works from right-to-left, meaning it will treat Del key as
BS keys when running dot repeat.
### Performance problems
If you have any performance problems (cursor jitter usually) make sure you're not using these kinds of extensions:
- Anything that renders decorators very often:
- Line number extensions (VSCode has built-in support for normal/relative line numbers)
- Indent guide extensions (VSCode has built-in indent guides)
- Brackets highlighter extensions (VSCode has built-in feature)
- VSCode extensions that delay the extension host like "Bracket Pair Colorizer"
- VIM plugins that increase latency and cause performance problems.
- Make sure to disable unneeded plugins, as many of them don't make sense with vscode and may cause problems.
- You don't need any code, highlighting, completion, lsp plugins as well any plugins that spawn windows/buffers
(nerdtree and similar), fuzzy-finders, etc.
- Many navigation/textobject/editing plugins should be fine.
If you're not sure, disable all other extensions, **reload vscode window**, and see if the problem persists before
reporting.
### Conditional init.vim
To determine if neovim is running in vscode, add to your init.vim:
```vim
if exists('g:vscode')
" VSCode extension
else
" ordinary neovim
endif
```
To conditionally activate plugins, `vim-plug` has a
[few solutions](https://github.com/junegunn/vim-plug/wiki/tips#conditional-activation). For example, using the `Cond`
helper, you can conditionally activate installed plugins
([source](https://github.com/asvetliakov/vscode-neovim/issues/415#issuecomment-715533865)):
```vim
" inside plug#begin:
" use normal easymotion when in vim mode
Plug 'easymotion/vim-easymotion', Cond(!exists('g:vscode'))
" use vscode easymotion when in vscode mode
Plug 'asvetliakov/vim-easymotion', Cond(exists('g:vscode'), { 'as': 'vsc-easymotion' })
```
### Custom escape keys
Since VSCode is responsible for insert mode, custom insert-mode vim mappings don't work. To map composite escape keys,
put into your keybindings.json:
for jj
```json
{
"command": "vscode-neovim.compositeEscape1",
"key": "j",
"when": "neovim.mode == insert && editorTextFocus",
"args": "j"
}
```
to enable jk add also:
```json
{
"command": "vscode-neovim.compositeEscape2",
"key": "k",
"when": "neovim.mode == insert && editorTextFocus",
"args": "k"
}
```
Currently, there is no way to map both `jk` and `kj`, or to map `jk` without also mapping `jj`.
### Jumplist
VSCode's jumplist is used instead of Neovim's. This is to make VSCode native navigation (mouse click, jump to
definition, ect) navigable through the jumplist.
Make sure to bind to `workbench.action.navigateBack` / `workbench.action.navigateForward` if you're using custom
mappings. Marks (both upper & lowercased) should work fine.
### Wildmenu completion
Command menu has the wildmenu completion on type. The completion options appear after 1.5s (to not bother you when you
write `:w` or `:noh`). Up/Down selects the option and Tab accepts it. See the gif:
### Multiple cursors
Multiple cursors work in:
1. Insert mode
2. Visual line mode
3. Visual block mode
To spawn multiple cursors from visual line/block modes type ma/mA or mi/mI
(by default). The effect differs:
- For visual line mode, mi will start insert mode on each selected line on the first non whitespace
character and ma will on the end of line.
- For visual block mode, mi will start insert on each selected line before the cursor block and
ma after.
- mA/mI versions accounts for empty lines (only for visual line mode, for visual block mode
they're same as ma/mi).
See gif in action:
### Keyboard Quickfix
By default, the quickfix menu can be opened using z= or C-.. However, it is currently
[not possible](https://github.com/microsoft/vscode/issues/55111) to add mappings to the quickfix menu, so it can only be
navigated with arrow keys. A
[workaround vscode extension](https://marketplace.visualstudio.com/items?itemName=pascalsenn.keyboard-quickfix) has been
made to use the quick open menu, which can be navigated with custom bindings.
To use, install the
[keyboard-quickfix](https://marketplace.visualstudio.com/items?itemName=pascalsenn.keyboard-quickfix) extension, and add
to your keybindings.json:
```jsonc
{
"key": "ctrl+.",
"command": "keyboard-quickfix.openQuickFix",
"when": "editorHasCodeActionsProvider && editorTextFocus && !editorReadonly"
},
```
and add to your init.vim:
```vim
nnoremap z= call VSCodeNotify('keyboard-quickfix.openQuickFix')
```
### Invoking VSCode actions from neovim
There are a
[few helper functions](https://github.com/asvetliakov/vscode-neovim/blob/master/vim/vscode-neovim.vim#L17-L39) that
could be used to invoke any vscode commands:
| Command | Description |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `VSCodeNotify(command, ...)`
`VSCodeCall(command, ...)` | Invoke vscode command with optional arguments. |
| `VSCodeNotifyRange(command, line1, line2, leaveSelection ,...)`
`VSCodeCallRange(command, line1, line2, leaveSelection, ...)` | Produce real linewise vscode selection from `line1` to `line2` and invoke vscode command. Put 1 for the `leaveSelection` argument to leave vscode selection after invoking the command. |
| `VSCodeNotifyRangePos(command, line1, line2, pos1, pos2, leaveSelection ,...)`
`VSCodeCallRangePos(command, line1, line2, pos1, pos2, leaveSelection, ...)` | Produce real characterwise vscode selection from `line1.pos1` to `line2.pos2` and invoke vscode command. |
> 💡 Functions with `Notify` in their name are non-blocking, the ones with `Call` are blocking. Generally **use Notify**
> unless you really need a blocking call.
#### Examples
Produce linewise/characterwise selection and show vscode commands (default binding):
```vim
function! s:openVSCodeCommandsInVisualMode()
let mode = mode()
if mode ==# 'V'
let startLine = line('v')
let endLine = line('.')
call VSCodeNotifyRange('workbench.action.showCommands', startLine, endLine, 1)
else
let startPos = getpos('v')
let endPos = getpos('.')
call VSCodeNotifyRangePos('workbench.action.showCommands', startPos[1], endPos[1], startPos[2], endPos[2] + 1, 1)
endif
endfunction
xnoremap call openVSCodeCommandsInVisualMode()
```
Open definition aside (default binding):
```vim
nnoremap gd call VSCodeNotify('editor.action.revealDefinitionAside')
```
Run Find in files for word under cursor in vscode:
```vim
nnoremap ? call VSCodeNotify('workbench.action.findInFiles', { 'query': expand('')})
```
## ⌨️ Bindings
**Custom keymaps for scrolling/window/tab/etc management**
- See [vscode-scrolling.vim](https://github.com/asvetliakov/vscode-neovim/blob/HEAD/vim/vscode-scrolling.vim) for scrolling commands reference
- See [vscode-file-commands.vim](https://github.com/asvetliakov/vscode-neovim/blob/HEAD/vim/vscode-file-commands.vim) for file commands reference
- See [vscode-tab-commands.vim](https://github.com/asvetliakov/vscode-neovim/blob/HEAD/vim/vscode-tab-commands.vim) for tab commands reference
- See [vscode-window-commands.vim](https://github.com/asvetliakov/vscode-neovim/blob/HEAD/vim/vscode-window-commands.vim) for window commands reference
> 💡 "With bang" refers to adding a "!" to the end of a command.
### File management
| Command | Description |
| ------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `e[dit]` / `ex` | Open quickopen.
With filename, e.g. `:e $MYVIMRC`: open the file in new tab. The file must exist.
With bang: revert file to last saved version.
With filename and bang e.g. `:e! $MYVIMRC`: close current file (discard any changes) and open the file. The file must exist. |
| `ene[w]` | Create new untitled document in vscode.
With bang: close current file (discard any changes) and create new document. |
| `fin[d]` | Open vscode's quick open window. Arguments and count are not supported. |
| `w[rite]` | Save current file. With bang: open 'save as' dialog. |
| `sav[eas]` | Open 'save as' dialog. |
| `wa[ll]` | Save all files. |
| `q[uit]` / C-w q / C-w c / ZQ | Close the active editor. With bang: revert changes and close the active editor. |
| `wq` / ZZ | Save and close the active editor. |
| `qa[ll]` | Close all editors, but don't quit vscode. Acts like `qall!`, so beware for nonsaved changes. |
| `wqa[ll]` / `xa[ll]` | Save all editors & close. |
### Tab management
| Command | Description |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| `tabe[dit]` | Similar to `e[dit]`. Open quickopen.
With argument: open the file in new tab. |
| `tabnew` | Open new untitled file. |
| `tabf[ind]` | Open quickopen window. |
| `tab`/`tabs` | Not supported. Doesn't make sense with vscode. |
| `tabc[lose]` | Close active editor (tab). |
| `tabo[nly]` | Close other tabs in vscode **group** (pane). This differs from vim where a `tab` is a like a new window, but doesn't make sense in vscode. |
| `tabn[ext]` / gt | Switch to next (or `count` tabs if argument is given) in the active vscode **group** (pane). |
| `tabp[revious]` / gT | Switch to previous (or `count` tabs if argument is given) in the active vscode **group** (pane). |
| `tabfir[st]` | Switch to the first tab in the active editor group. |
| `tabl[ast]` | Switch to the last tab in the active editor group. |
| `tabm[ove]` | Not supported yet. |
### Buffer/window management
| Command | Key | Description |
| ---------- | ------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `sp[lit]` | C-w s | Split editor horizontally.
With argument: open the specified file, e.g `:sp $MYVIMRC`. File must exist. |
| `vs[plit]` | C-w v | Split editor vertically.
With argument: open the specified file. File must exist. |
| `new` | C-w n | Like `sp[lit]` but create new untitled file if no argument given. |
| `vne[w]` | | Like `vs[plit]` but create new untitled file if no argument given. |
| | C-w = | Align all editors to have the same width. |
| | C-w \_ | Toggle maximized editor size. Pressing again will restore the size. |
| | [count] C-w + | Increase editor height by (optional) count. |
| | [count] C-w - | Decrease editor height by (optional) count. |
| | [count] C-w > | Increase editor width by (optional) count. |
| | [count] C-w \< | Decrease editor width by (optional) count. |
| `on[ly]` | C-w o | Without bang: merge all editor groups into the one. Don't close editors.
With bang: close all editors from all groups except current one. |
| | C-w j/k/h/l | Focus group below/above/left/right. |
| | C-w C-j/i/h/l | Move editor to group below/above/left/right.
**Note**: C-w C-i moves editor up. Ideally it should be C-w C-k but vscode has many commands mapped to C-k [key] and doesn't allow to use C-w C-k without unbinding them first. |
| | C-w J/K/H/L | Move whole editor group below/above/left/right. |
| | C-w w or C-w C-w | Focus next group. The behavior may differ than in vim. |
| | C-w W or C-w p | Focus previous group. The behavior may differ than in vim. C-w p is completely different than in vim. |
| | C-w b | Focus last editor group (most bottom-right). |
| | C-w r/R/x | Not supported, use C-w C-j and similar to move editors. |
> 💡 Split size distribution is controlled by `workbench.editor.splitSizing` setting. By default, it's `distribute`,
> which is equal to vim's `equalalways` and `eadirection = 'both'` (default).
To use VSCode command 'Increase/decrease current view size' instead of separate bindings for width and height:
- `workbench.action.increaseViewSize`
- `workbench.action.decreaseViewSize`
Copy this into init.vim
function! s:manageEditorSize(...)
let count = a:1
let to = a:2
for i in range(1, count ? count : 1)
call VSCodeNotify(to ==# 'increase' ? 'workbench.action.increaseViewSize' : 'workbench.action.decreaseViewSize')
endfor
endfunction
" Sample keybindings. Note these override default keybindings mentioned above.
nnoremap > call manageEditorSize(v:count, 'increase')
xnoremap > call manageEditorSize(v:count, 'increase')
nnoremap + call manageEditorSize(v:count, 'increase')
xnoremap + call manageEditorSize(v:count, 'increase')
nnoremap < call manageEditorSize(v:count, 'decrease')
xnoremap < call manageEditorSize(v:count, 'decrease')
nnoremap - call manageEditorSize(v:count, 'decrease')
xnoremap - call manageEditorSize(v:count, 'decrease')
### Insert mode special keys
Enabled by `useCtrlKeysForInsertMode` (default true).
| Key | Description | Status |
| ------------------------------------------- | ----------------------------------------------------------------- | --------------------------------- |
| C-r [0-9a-z"%#*+:.-=] | Paste from register. | Works |
| C-a | Paste previous inserted content. | Works |
| C-o | Switch to normal mode for a single command, then back. | Works |
| C-u | Delete all text till beginning of line. If empty, delete newline. | Bound to VSCode key |
| C-w | Delete word left. | Bound to VSCode key |
| C-h | Delete character left. | Bound to VSCode key |
| C-t | Indent lines right. | Bound to VSCode indent line |
| C-d | Indent lines left. | Bound to VSCode outindent line |
| C-j | Insert line. | Bound to VSCode insert line after |
| C-c | Escape. | Works |
Other keys are not supported in insert mode.
### Normal mode control keys
Enabled by `useCtrlKeysForNormalMode` (default true).
Refer to vim manual for their use.
- C-a
- C-b
- C-c
- C-d
- C-e
- C-f
- C-i
- C-o (to enable, see
[this issue](https://github.com/asvetliakov/vscode-neovim/issues/181#issuecomment-585264621))
- C-r
- C-u
- C-v
- C-w
- C-x
- C-y
- C-]
- C-j
- C-k
- C-l
- C-h
- C-/
### Cmdline special keys
Always enabled.
| Key | Desription |
| ------------------------------- | --------------------------------------------------------- |
| C-h | Delete one character left. |
| C-w | Delete word left. |
| C-u | Clear line. |
| C-g / C-t | In incsearch mode moves to next/previous result. |
| C-l | Add next character under the cursor to incsearch. |
| C-n / C-p | Go down/up history. |
| Up / Down | Select next/prev suggestion (cannot be used for history). |
| Tab | Select suggestion. |
### VSCode specific bindings
#### Editor command
| Key | VSCode Command |
| ----------------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| = / == | `editor.action.formatSelection` |
| gh / K | `editor.action.showHover` |
| gd / C-] | `editor.action.revealDefinition`
Also works in vim help. |
| gf | `editor.action.revealDeclaration` |
| gH | `editor.action.referenceSearch.trigger` |
| gO | `workbench.action.gotoSymbol` |
| C-w gd / C-w gf | `editor.action.revealDefinitionAside` |
| gD | `editor.action.peekDefinition` |
| gF | `editor.action.peekDeclaration` |
| Tab | `togglePeekWidgetFocus`
Switch between peek editor and reference list. |
| C-n / C-p | Navigate lists, parameter hints, suggestions, quick-open, cmdline history, peek reference list |
> 💡 To specify the default peek mode, modify `editor.peekWidgetDefaultFocus` in your settings.
#### Explorer/list navigation
| Key | VSCode Command |
| ---------------------------------- | ------------------------------- |
| j / k | `list.focusDown/Up` |
| h / l | `list.collapse/select` |
| Enter | `list.select` |
| gg | `list.focusFirst` |
| G | `list.focusLast` |
| o | `list.toggleExpand` |
| C-u / C-d | `list.focusPageUp/Down` |
| / / Escape | `list.toggleKeyboardNavigation` |
> 💡 To enable explorer list navigation, add `"workbench.list.automaticKeyboardNavigation": false` to your
> `settings.json`.
#### Explorer file manipulation
| Key | VSCode Command |
| ------------ | --------------------- |
| r | `renameFile` |
| d | `deleteFile` |
| y | `filesExplorer.copy` |
| x | `filesExplorer.cut` |
| p | `filesExplorer.paste` |
| v | `explorer.openToSide` |
| a | `explorer.newFile` |
| A | `explorer.newFolder` |
### Custom keybindings
Control keys which are not in the above tables are not sent to neovim by default. To pass additional ctrl keys to
neovim, for example C-Tab, add to your keybindings.json:
```jsonc
{
"command": "vscode-neovim.send",
// the key sequence to activate the binding
"key": "ctrl+tab",
// don't activate during insert mode
"when": "editorTextFocus && neovim.mode != insert",
// the input to send to neovim
"args": ""
}
```
To disable existing an ctrl key sequence, for example C-A add to your keybindings.json:
```json
{
"command": "-vscode-neovim.send",
"key": "ctrl+a"
}
```
## 🤝 Vim Plugins
Most vim plugins will work out of the box, but certain plugins may require some fixes to work properly.
### vim-easymotion
While the original [vim-easymotion](https://github.com/easymotion/vim-easymotion) functions as expected, it works by
replacing your text with markers then restoring back, which leads to broken text and many errors reported in VSCode.
For this reason I created the special [vim-easymotion fork](https://github.com/asvetliakov/vim-easymotion) which doesn't
touch your text and instead use vscode text decorations. Just add my fork to your `vim-plug` block or by using your
favorite vim plugin installer and delete original vim-easymotion. Also overwin motions won't work (obviously) so don't
use them.
By default, text decorations will appear behind of the associated text as shown in the screenshot. To show the
decorations on top of the text, set `vscode-neovim.textDecorationsAtTop` to true.
Happy jumping!
### vim-commentary
You can use [vim-commentary](https://github.com/tpope/vim-commentary) if you like it. But vscode already has such
functionality so why don't use it? Add to your init.vim/init.nvim:
```vim
xmap gc VSCodeCommentary
nmap gc VSCodeCommentary
omap gc VSCodeCommentary
nmap gcc VSCodeCommentaryLine
```
Similar to vim-commentary, gcc is comment line (accept count), use gc with motion/in visual mode. `VSCodeCommentary` is
just a simple function which calls `editor.action.commentLine`.
### quick-scope
[quick-scope](https://github.com/unblevable/quick-scope) plugin uses default vim HL groups by default but they are
normally ignored. To fix, add
```vim
highlight QuickScopePrimary guifg='#afff5f' gui=underline ctermfg=155 cterm=underline
highlight QuickScopeSecondary guifg='#5fffff' gui=underline ctermfg=81 cterm=underline
```
to your init.vim. The underline color can be changed by the `guisp` tag.
## 📑 How it works
- VScode connects to neovim instance
- When opening a some file, a scratch buffer is created in nvim and being init with text content from vscode
- Normal/visual mode commands are being sent directly to neovim. The extension listens for buffer events and applies
edits from neovim
- When entering the insert mode, the extensions stops listen for keystroke events and delegates typing mode to vscode
(no neovim communication is being performed here)
- After pressing escape key from the insert mode, extension sends changes obtained from the insert mode to neovim
## ❤️ Credits & External Resources
- [vim-altercmd](https://github.com/kana/vim-altercmd) - Used for rebinding default commands to call vscode command
- [neovim nodejs client](https://github.com/neovim/node-client) - NodeJS library for communicating with Neovim
- [VSCodeVim](https://github.com/VSCodeVim/Vim) - Used for various inspiration