VSCode Neovim installs statistics

VSCode Neovim

<p align="center"><img src="https://github.com/asvetliakov/vscode-neovim/raw/HEAD/images/icon.png" height="128"><br>VSCode Neovim Integration</p> <p align=center> <a href="https://marketplace.visualstudio.com/items?itemName=asvetliakov.vscode-neovim"><img src="https://img.shields.io/visual-studio-marketplace/v/asvetliakov.vscode-neovim?color=%234c1&label=Visual%20Studio%20Marketplace"></a> <a href="https://github.com/asvetliakov/vscode-neovim/actions/workflows/build_test.yml"><img src="https://github.com/asvetliakov/vscode-neovim/actions/workflows/build_test.yml/badge.svg"></a> <a href="https://gitter.im/vscode-neovim/community?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge"><img src="https://badges.gitter.im/vscode-neovim/community.svg"></a> </p>

Neovim is a fork of Vim to allow greater extensibility and integration. This extension uses a fully embedded Neovim instance, no more half-complete Vim emulation! VSCode's native functionality is used for insert mode and VSCode commands, making the best use of both editors.

• 🎉 Feature-complete Vim integration (except insert-mode and some Nvim UI plugins) by utilizing Nvim as a backend.
• 🔧 Supports custom init.lua and most Nvim 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).

<strong>Table of Contents</strong>

• 🧰 Getting Started
  • Installation
  • Neovim configuration
  • VSCode Settings & Commands
• 💡 Tips and Features
  • VSCode specific differences
  • Troubleshooting
  • Performance
  • Composite escape keys
  • Jumplist
  • Multiple cursors
  • Remote development
• ⚡️ API
  • vscode.action(name, opts)
  • vscode.call(name, opts, timeout)
  • vscode.on(event, callback)
  • vscode.has_config(name)
  • vscode.get_config(name)
  • vscode.update_config(name, value, target)
  • vscode.notify(msg)
  • vscode.eval(code[, opts, timeout])
  • vscode.eval_async(code[, opts])
  • vscode.with_insert(callback[, ms])
  • Builtin module overrides
  • VimScript
• ⌨️ Keybindings (shortcuts)
  • Keybinding Passthroughs
    • Insert mode control keys passthrough
    • Normal mode control keys passthrough
    • Cmdline mode special keys passthrough
    • Disable passthrough for certain filetypes
    • Remove other vscode or passthrough keybindings
  • Code navigation bindings
  • Explorer/list navigation bindings
  • Explorer file manipulation bindings
  • Hover widget manipulation bindings
• 📟 Neovim Commands
  • File management
  • Tab management
  • Buffer/window management
• 🎨 Highlights
• 🧰 Developing
• ❤️ Credits & External Resources

🧰 Getting Started

Installation

• Install the vscode-neovim extension.
• Install Neovim 0.10.0 or newer.
  • (Optional) Set the Nvim path in the extension settings. You must specify the full path to Neovim, like C:\Neovim\bin\nvim.exe or /usr/local/bin/nvim.
  • Choose one of the following platform-specific settings:
    • vscode-neovim.neovimExecutablePaths.win32
    • vscode-neovim.neovimExecutablePaths.linux
    • vscode-neovim.neovimExecutablePaths.darwin
• If you want to use Neovim from WSL, set the useWSL configuration toggle and specify the Linux path to the 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.
• Assign affinity value for performance improvement.

Snap Users: If you want to use Neovim from Snap, the Neovim path must be resolved to the snap binary location. On some systems it might be "/snap/nvim/current/usr/bin/nvim". To check if you're running as a snap package, see if which nvim resolves to /usr/bin/snap.

Neovim configuration

Since many Vim plugins can cause issues in VSCode, it is recommended to start from an empty init.vim. For a guide for which types of plugins are supported, see troubleshooting.

Before creating an issue on Github, make sure you can reproduce the problem with an empty init.vim and no VSCode extensions.

To detect if Nvim is running in VSCode, add to your init.vim:

if exists('g:vscode')
    " VSCode extension
else
    " ordinary Nvim
endif

In lua:

if vim.g.vscode then
    -- VSCode extension
else
    -- ordinary Nvim
end
```…