HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
VSCodeVim
Vim
TypeScript2015–2025
VSCodeVim / Vim

Vim

:star: Vim for Visual Studio Code

46Distinct people
59Mentions
1Explicit recommenders
15.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

:star: Vim for Visual Studio Code

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

There are a few. I am using VSCodeVim[1] with the default settings (besides the typical `jj` command) I love it, and using anything else feels weird. I remember having some…

MFogleman used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year59 dated mentions

Observed mentions: 2015-11-18 22:14:12 UTC to 2025-05-06 19:02:05 UTC.

0369122015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 12 mentions; 0 submissions, 12 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 12 mentions; 0 submissions, 12 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC101
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC12012
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC12012
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC505
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC808
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC707
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC404
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC413
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC312

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
VSCodeVim Vim emulation for Visual Studio Code VSCodeVim is a Vim emulator for Visual Studio Code. 📃 Our change log outlines the breaking/major/minor updates between releases. Report missing features/bugs on GitHub. Table of Contents (click to expand) 💾 Installation Mac Windows ⚙️ Settings Quick Example VSCodeVim settings Neovim Integration Key Remapping "vim.insertModeKeyBindings"/"vim.normalModeKeyBindings"/"vim.visualModeKeyBindings"/"vim.operatorPendingModeKeyBindings" "vim.insertModeKeyBindingsNonRecursive"/"normalModeKeyBindingsNonRecursive"/"visualModeKeyBindingsNonRecursive"/"operatorPendingModeKeyBindingsNonRecursive" Debugging Remappings Remapping more complex key combinations Vim modes Vim settings .vimrc support 🖱️ Multi-Cursor Mode 🔌 Emulated Plugins vim-airline vim-easymotion vim-surround vim-commentary vim-indent-object vim-sneak CamelCaseMotion Input Method ReplaceWithRegister vim-textobj-entire vim-textobj-arguments 🎩 VSCodeVim tricks! 📚 F.A.Q. ❤️ Contributing Special shoutouts to: 💾 Installation VSCodeVim can be installed via the VS Code Marketplace or the OpenVSX Marketplace. Mac To enable key-repeating, execute the following in your Terminal, log out and back in, and then restart VS Code: defaults write com.microsoft.VSCode ApplePressAndHoldEnabled -bool false # For VS Code defaults write com.microsoft.VSCodeInsiders ApplePressAndHoldEnabled -bool false # For VS Code Insider defaults write com.vscodium ApplePressAndHoldEnabled -bool false # For VS Codium defaults write com.microsoft.VSCodeExploration ApplePressAndHoldEnabled -bool false # For VS Codium Exploration users defaults write com.exafunction.windsurf ApplePressAndHoldEnabled -bool false # For Windsurf defaults delete -g ApplePressAndHoldEnabled # If necessary, reset global default We also recommend increasing Key Repeat and Delay Until Repeat settings in System Settings/Preferences -> Keyboard. Windows Like real vim, VSCodeVim will take over your control keys. This behavior can be adjusted with the useCtrlKeys and handleKeys settings. ⚙️ Settings The settings documented here are a subset of the supported settings; the full list is described in the FEATURES -> Settings tab of VSCodeVim's extension details page, which can be found in the extensions view of VS Code. Quick Example Below is an example of a settings.json file with settings relevant to VSCodeVim: { "vim.easymotion": true, "vim.incsearch": true, "vim.useSystemClipboard": true, "vim.useCtrlKeys": true, "vim.hlsearch": true, "vim.insertModeKeyBindings": [ { "before": ["j", "j"], "after": ["<Esc>"] } ], "vim.normalModeKeyBindingsNonRecursive": [ { "before": ["<leader>", "d"], "after": ["d", "d"] }, { "before": ["<C-n>"], "commands": [":nohl"] }, { "before": ["K"], "commands": ["lineBreakInsert"], "silent": true } ], "vim.leader": "<space>", "vim.handleKeys": { "<C-a>": false, "<C-f>": false }, // To improve performance "extensions.experimental.affinity": { "vscodevim.vim": 1 } } VSCodeVim settings These settings are specific to VSCodeVim. Setting Description Type Default Value vim.changeWordIncludesWhitespace Include trailing whitespace when changing word. This configures the cw action to act consistently as its siblings (yw and dw) instead of acting as ce. Boolean false vim.cursorStylePerMode.{Mode} Configure a specific cursor style for {Mode}. Omitted modes will use default cursor type Supported cursors: line, block, underline, line-thin, block-outline, and underline-thin. String None vim.digraphs.{shorthand} Set custom digraph shorthands that can override the default ones. Entries should map a two-character shorthand to a descriptive string and one or more UTF16 code points. Example: "R!": ["🚀", [55357, 56960]] Object {"R!": ["🚀", [0xD83D, 0xDE80]] vim.disableExtension Disable VSCodeVim extension. This setting can also be toggled using toggleVim command in the Command Palette Boolean false vim.handleKeys Delegate configured keys to be handled by VS Code instead of by the VSCodeVim extension. Any key in keybindings section of the package.json that has a vim.use<C-...> in the when argument can be delegated back to VS Code by setting "<C-...>": false. Example: to use ctrl+f for find (native VS Code behavior): "vim.handleKeys": { "<C-f>": false }. String "<C-d>": true "<C-s>": false "<C-z>": false vim.overrideCopy Override VS Code's copy command with our own, which works correctly with VSCodeVim. If cmd-c/ctrl-c is giving you issues, set this to false and complain here. Boolean false vim.useSystemClipboard Use the system clipboard register (*) as the default register Boolean false vim.searchHighlightColor Background color of non-current search matches String findMatchHighlightBackground ThemeColor vim.searchHighlightTextColor Foreground color of non-current search matches String None vim.searchMatchColor Background color of current search match String findMatchBackground ThemeColor vim.searchMatchTextColor Foreground color of current search match String None vim.substitutionColor Background color of substitution text when vim.inccommand is enabled String "#50f01080" vim.substitutionTextColor Foreground color of substitution text when vim.inccommand is enabled String None vim.startInInsertMode Start in Insert mode instead of Normal Mode Boolean false vim.useCtrlKeys Enable Vim ctrl keys overriding common VS Code operations such as copy, paste, find, etc. Boolean true vim.visualstar In visual mode, start a search with * or # using the current selection Boolean false vim.highlightedyank.enable Enable highlighting when yanking Boolean false vim.highlightedyank.color Set the color of yank highlights String rgba(250, 240, 170, 0.5) vim.highlightedyank.duration Set the duration
Read the full README on GitHub

What Hacker News says

12 sources
I suspect what you're running into is some kind of crash when running a command. I will say that I don't think we're doing a very good job handling errors, and I suspect it's that most users don't report them (they just press <Esc> and it goes back to normal). For example, this: https://github.com/VSCodeVim/Vim/pull/2087 Either way, if you're ever interested in heading back to VSCode and felt disappointed in the Vim mode, check out the progress of https://github.com/VSCodeVim/Vim/pull/1897 or https://github.com/Chillee/VSCodeNeovim. Those should provide a much higher fidelity emulation.
In VS Code Roadmap 2018
I'm an avid tmux+neovim user, too, though working with Reason is a lot easier in VS Code. Making the switch from actual vim to fake vim (ie JS emulation) sucks. Recently, VSCodeVim merged #1725 to add actual neovim as an editor - it's using NeoVim's embedding API so you're using neovim to edit the text file inside of VSCode's chrome, including all of VSCode's type hints and popups. Info here: https://github.com/VSCodeVim/Vim/issues/1735 There's an ongoing rewrite to make neovim also work with your existing .vimrc file: https://github.com/VSCodeVim/Vim/pull/1897 I'm really stoked that we get the best of both - for languages with first-class VSCode support we don't have to decide between a half-baked VIM plugin or using VSCode without vim... you get both!
In Vim after 15 Years
I'm one of the developers for VsCodeVim, and many of the prominent vim plugins support most of these. I'll break down what vscodevim supports. > text objects Yes, cit, ciw, ci), etc. all work > marks Mostly. We don't have proper support for uppercase marks (across files and persistent), nor some of the less common autogenerated marks ('] for example). > mappings Works for most common mappings. Stuff like jj to <Esc>, space to <leader>, etc work, but there are definitely bugs in it. > macros Yes. Missing some stuff like the ability to execute any register as a macro (instead of just text), but otherwise works. > ex-commands Full support through neovim integration. Technically even supports any plugins through Ex-commands. I've also been working on a PR for full neovim integration, https://github.com/VSCodeVim/Vim/pull/1897 Many of the othe
Read the rest
r vim plugins also support many of these. VsVim is excellent, for example.
In Level up your VsVim
I personally also think that the VSCode vim plugin is even better than the atom one, and it's currently in a very active state of development. We recently added neovim integration for Ex-commands, which means that practically every Ex-command is now supported. Check out our changelog: https://github.com/VSCodeVim/Vim/releases/tag/v0.8.0 Disclosure: I am one of the developers for VSCodeVim, but I am legitimately excited about all the features we've been adding recently.
In Sublime Text 3 Build 3132 released
At least for me, :%s/foo/bar seems to work fine, as does the find command. I think that registers should mostly work pretty well too ("ayy and then "ap work fine for me). I don't know if this is what you're talking about, but we have some ctrl+d/ctrl+u bugs that have to wait for upstream changes :/ https://github.com/VSCodeVim/Vim/issues/1348 I saw that you said you'll submit bugs to the tracker, so I'll see those then :) We've been pretty active about adding features/fixing bugs: https://github.com/VSCodeVim/Vim/releases
In Why I like Vim so much [video]
https://github.com/lunixbochs/ActualVim gives you neovim inside Sublime Text, altho I haven't tried it. I couldn't stand IdeaVim, the one for the Jetbrains IntelliJ platform - felt very buggy. Such as when you open a modal and it remains in Normal mode so you can't enter text. Currently using https://github.com/VSCodeVim/Vim when using VSCode which is better but still got some rough edges. Despite a fair bit of use and study - mostly using neovim - I feel that I haven't got as much from vim as I'd expected or hoped. Switching from Normal to Insert mode - even when you get good at the one-time Normal mode commands - doesn't always elegant. There's all sorts of configurations and plugins that try to plug the gaps, but it's such a huge effort to assemble them all. For example, just installed https://github.com/terryma/vim-multiple-cursors to
Read the rest
day to attempt get the elegant multiple selection of modern text editors.
In Why I like Vim so much [video]

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.