Vim/README.md

622 lines
24 KiB
Markdown
Raw Normal View History

<h2 align="center"><img src="https://raw.githubusercontent.com/VSCodeVim/Vim/master/images/icon.png" height="128"><br>VSCodeVim</h2>
<p align="center"><strong>Vim emulation for Visual Studio Code</strong></p>
2017-06-24 23:52:58 +03:00
2017-06-28 18:24:38 +03:00
[![http://aka.ms/vscodevim](https://vsmarketplacebadge.apphb.com/version/vscodevim.vim.svg)](http://aka.ms/vscodevim)
2017-06-29 20:18:29 +03:00
[![https://travis-ci.org/VSCodeVim/Vim](https://travis-ci.org/VSCodeVim/Vim.svg?branch=master)](https://travis-ci.org/VSCodeVim/Vim)
2017-06-24 23:52:58 +03:00
VSCodeVim is a [Visual Studio Code](https://code.visualstudio.com/) extension that enables:
2016-01-07 02:59:32 +03:00
* Keybindings and command combinations (`c3w`, `daw`, `2dd`, etc)
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* Modes: normal, insert, command-line, visual, visual line, visual block
* Command remapping (`jj` to `<Esc>`, `:` to command panel, etc.)
* Incremental search with `/` and `?`
2016-07-07 09:59:05 +03:00
* Marks
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* Popular vim plugin features built-in (easymotion, surround, commentary)
* Multi-cursor support, run vim commands everywhere!
* Refer to our [roadmap](ROADMAP.md) for a full list
2017-01-10 08:15:59 +03:00
Please report missing features/bugs on [GitHub](https://github.com/VSCodeVim/Vim/issues) and join us on [Slack](https://vscodevim-slackin.azurewebsites.net).
2017-01-09 04:52:32 +03:00
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
## Contents
* [Getting Started](#getting-started)
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* [Mac setup](#mac-setup)
* [Windows setup](#windows-setup)
2018-05-08 15:21:23 +03:00
* [Linux setup](#linux-setup)
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* [Settings](#settings)
* [VSCodeVim settings](#vscodevim-settings)
2017-05-22 09:45:46 +03:00
* [Neovim Integration](#neovim-integration)
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* [Key remapping](#key-remapping)
* [Vim settings](#vim-settings)
* [Status bar colors (vim-airline)](#status-bar-color-settings)
* [Multi-cursor mode](#multi-cursor-mode)
* [Emulated plugins](#emulated-plugins)
* [vim-easymotion](#vim-easymotion)
* [vim-surround](#vim-surround)
* [vim-commentary](#vim-commentary)
* [vim-indent-object](#vim-indent-object)
2018-01-18 18:09:28 +03:00
* [vim-sneak](#vim-sneak)
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* [VSCodeVim tricks](#vscodevim-tricks)
* [F.A.Q / Troubleshooting](#faq)
* [Contributing](#contributing)
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
## Getting started
VSCodeVim is automatically enabled following [installation](https://marketplace.visualstudio.com/items?itemName=vscodevim.vim) and the reloading of VSCode.
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
### Vim compatibility
All common Vim commands are supported. For a detailed list of supported features, refer to our [roadmap](ROADMAP.md). Vimscript is *not* supported, so you aren't able to load your `.vimrc` or use `.vim` plugins. You have to replicate these using our [Settings](#settings) and [Emulated plugins](#emulated-plugins).
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
### Mac setup
If key repeating isn't working for you, execute this in your Terminal, then restart VS Code.
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
```sh
defaults write com.microsoft.VSCode ApplePressAndHoldEnabled -bool false # For VS Code
defaults write com.microsoft.VSCodeInsiders ApplePressAndHoldEnabled -bool false # For VS Code Insider
defaults delete -g ApplePressAndHoldEnabled # If necessary, reset global default
```
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
We also recommend going into *System Preferences -> Keyboard* and increasing the Key Repeat and Delay Until Repeat settings to improve your speed.
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
### Windows setup
VSCodeVim will take over your control keys, just like real vim, so you get the _full_ vim experience. This behaviour can be adjusted with the [`useCtrlKeys`](#vimusectrlkeys) and [`handleKeys`](#vimhandlekeys) settings.
### Linux setup
If you have configured `vim.useSystemClipboard: "true"`, we rely on [clipboardy](https://github.com/sindresorhus/clipboardy) for cross-platform copy/paste operations. This library is dependent on `xsel`:
```sh
apt install xsel
```
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
## Settings
### Quick Example
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
Below is an example of a [settings.json](https://code.visualstudio.com/Docs/customization/userandworkspace) file for VSCode settings applicable to this extension.
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
```json
{
"vim.easymotion": true,
2018-01-18 18:09:28 +03:00
"vim.sneak": true,
"vim.incsearch": true,
"vim.useSystemClipboard": true,
"vim.useCtrlKeys": true,
"vim.hlsearch": true,
"vim.insertModeKeyBindings": [
{
"before": ["j","j"],
"after": ["<Esc>"]
}
],
2018-06-17 03:19:32 +03:00
"vim.normalModeKeyBindingsNonRecursive": [
{
"before": ["<leader>","d"],
"after": ["d", "d"]
},
{
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
"before":["<C-n>"],
"commands": [
{
"command": ":nohl"
}
]
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
}
],
"vim.leader": "<space>",
"vim.handleKeys":{
"<C-a>": false,
"<C-f>": false
}
}
```
The following is a subset of the supported settings; the full list is described in the `Contributions` tab in the extensions menu of VSCode.
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
### VSCodeVim settings
These settings are specific to VSCodeVim.
#### `"vim.startInInsertMode"`
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* Have VSCodeVim start in Insert Mode rather than Normal Mode.
* We would be remiss in our duties as Vim users not to say that you should really be staying in Normal mode as much as you can, but hey, who are we to stop you?
#### `"vim.overrideCopy"`
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* Override VSCode's copy command with our own, which works correctly with VSCodeVim.
* If cmd-c or ctrl-c is giving you issues, set this to false and complain [here](https://github.com/Microsoft/vscode/issues/217).
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* Type: Boolean (Default: `true`)
2016-07-04 20:05:53 +03:00
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
#### `"vim.useSystemClipboard"`
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* Enable yanking to the system clipboard by default
* Type: Boolean (Default: `false`)
2016-08-03 09:47:10 +03:00
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
#### `"vim.searchHighlightColor"`
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* Set the color of search highlights.
* Type: Color String (Default: `rgba(150, 150, 150, 0.3)`)
#### `"vim.substituteGlobalFlag"`
* Similar to Vim's `gdefault` setting.
* `/g` flag in a substitute command replaces all occurrences in the line.
Without this argument, replacement occurs only for the first occurrence in each line.
* When `"vim.substituteGlobalFlag"` is `true`, the 'g' is default on.
This means that all matches in a line are substituted instead of one.
When a 'g' flag is given to a ":substitute" command, this will toggle the substitution
of all or one match.
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
#### `"vim.useCtrlKeys"`
* Enable Vim ctrl keys thus overriding common VSCode operations such as copy, paste, find, etc. Enabling this setting will result in the following keybindings:
2016-12-04 08:55:09 +03:00
* `ctrl+c`, `ctrl+[` => `<Esc>`
* `ctrl+f` => Full Page Forward
* `ctrl+d` => Half Page Back
* `ctrl+b` => Half Page Forward
* `ctrl+v` => Visual Block Mode
* etc.
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* Type: Boolean (Default: `true`)
2016-12-04 08:55:09 +03:00
#### `"vim.cmdLineInitialColon"`
* Set this to have VSCodeVim mimick Vim, showing the ':' colon character in the Vim command line when it is called.
* Type: Boolean (Default: `false`)
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
#### `"vim.handleKeys"`
* Delegate certain keybindings to be handled natively by VSCode instead of by the VSCodeVim extension
* Complete list of key combinations supported by this setting can be found under the `keybindings` section of our [package.json](https://github.com/VSCodeVim/Vim/blob/master/package.json). Each key that has a `vim.use<C-...>` in the when argument can be delegated back to vscode by setting `"<C-...>": false`.
* Example: user wants to use `ctrl+f` for find (native VSCode behaviour), but wants to have [`useCtrlKeys`](#vimusectrlkeys) set to true so that other vim bindings work:
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
```json
"vim.handleKeys": {
"<C-a>": false,
"<C-f>": false
}
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
```
#### `"vim.visualstar"`
* In visual mode, start a search with `*` or `#` using the current selection
* Type: Boolean (Default: `false`)
2017-10-06 04:30:09 +03:00
#### `"vim.cursorStylePerMode"`
* Configure a specific cursor style per mode; omitted modes will use default cursor type
* Supported modes: normal, insert, replace, visual, visualline, and visualblock
* Supported cursors: line, block, underline, line-thin, block-outline, and underline-thin
2017-10-06 04:30:09 +03:00
```json
2017-10-06 04:30:09 +03:00
"vim.cursorStylePerMode" : {
"normal": "underline",
"insert": "line-thin",
"replace": "block-outline"
}
```
#### `"vim.disableExtension"`
* Disable VSCodeVim (Note: this is different from disabling extension through VSCode)
* This setting can be changed through the settings or via `toggleVim` command in the Command Palette
* Type: Boolean (Default: `false`)
2017-10-06 04:30:09 +03:00
#### `"vim.debug.loggingLevel"`
* Extension logging level. Maximum level of messages to log.
* Logs will be visible in the [developer tools](https://code.visualstudio.com/docs/extensions/developing-extensions#_profiling-your-extension).
* Type: String (Default: 'error'). Supported values: 'error', 'warn', 'info', 'verbose', 'debug'.
2017-05-22 09:45:46 +03:00
### Neovim Integration
> :warning: Experimental feature. Please leave feedback on neovim integration [here](https://github.com/VSCodeVim/Vim/issues/1735).
2017-05-22 09:45:46 +03:00
We now have neovim integration for Ex-commands. To enable,
2017-06-08 21:10:31 +03:00
1. install [neovim](https://github.com/neovim/neovim/wiki/Installing-Neovim)
2. add the following configurations:
```json
"vim.enableNeovim": true
"vim.neovimPath": <path to neovim>
```
Here's some ideas on what you can do with neovim integration:
2017-06-08 21:10:31 +03:00
* [The power of g](http://vim.wikia.com/wiki/Power_of_g)
* [The :normal command](https://vi.stackexchange.com/questions/4418/execute-normal-command-over-range)
* Faster search and replace!
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
### Key remapping
There's several different mechanisms you can use to define custom remappings. Also see the [`useCtrlKeys`](#vimusectrlkeys) and [`handleKeys`](#vimhandlekeys) settings.
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
2018-06-17 03:19:32 +03:00
#### `"vim.insertModeKeyBindings"`/`"vim.normalModeKeyBindings"`/`"vim.visualModeKeyBindings"`
2018-06-17 03:19:32 +03:00
* Keybinding overrides to use for insert, normal, and visual modes.
* Bind `jj` to `<Esc>` in insert mode:
2016-07-04 20:05:53 +03:00
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
```json
"vim.insertModeKeyBindings": [
{
"before": ["j", "j"],
"after": ["<Esc>"]
}
]
2016-12-04 07:50:07 +03:00
```
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* Bind `:` to show the command palette:
2016-07-04 20:05:53 +03:00
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
```json
2018-06-17 03:19:32 +03:00
"vim.normalModeKeyBindingsNonRecursive": [
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
{
"before": [":"],
"commands": [
{
"command": "workbench.action.showCommands",
"args": []
}
]
}
2016-12-04 08:55:09 +03:00
]
2016-12-04 07:50:07 +03:00
```
* Bind `ZZ` to the vim command `:wq` (save and close the current file):
2016-12-04 07:50:07 +03:00
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
```json
2018-06-17 03:19:32 +03:00
"vim.normalModeKeyBindingsNonRecursive": [
2016-12-04 07:50:07 +03:00
{
"before": ["Z", "Z"],
"commands": [
{
"command": ":wq",
2016-12-04 07:50:07 +03:00
"args": []
},
]
}
]
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
```
2016-12-04 07:50:07 +03:00
* Bind `ctrl+n` to turn off search highlighting and `<leader>w` to save the current file:
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
```json
2018-06-17 03:19:32 +03:00
"vim.normalModeKeyBindingsNonRecursive": [
{
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
"before":["<C-n>"],
"commands": [
{
"command": ":nohl",
"args": []
}
]
},
{
"before": ["leader", "w"],
"commands": [
{
"command": "workbench.action.files.save",
"args": []
}
]
}
]
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
```
2018-06-17 03:19:32 +03:00
* Bind `p` in visual mode to paste without overriding the current register
2018-06-17 03:19:32 +03:00
```json
"vim.visualModeKeyBindingsNonRecursive": [
{
"after": [
"\"",
"_",
"d",
"P"
],
"before": [
"p",
]
}
],
```
* Bind `>` and `<` in visual mode to indent/outdent lines (repeatable)
```json
"vim.visualModeKeyBindingsNonRecursive": [
{
"before": [
">"
],
"commands": [
{
"args": [],
"command": "editor.action.indentLines"
}
]
},
{
"before": [
"<"
],
"commands": [
{
"args": [],
"command": "editor.action.outdentLines"
}
]
},
]
```
#### `"vim.insertModeKeyBindingsNonRecursive"`/`"normalModeKeyBindingsNonRecursive"`/`"visualModeKeyBindingsNonRecursive"`
* Non-recursive keybinding overrides to use for insert, normal, and visual modes
* *Example:* Bind `j` to `gj`. Notice that if you attempted this binding normally, the j in gj would be expanded into gj, on and on forever. Stop this recursive expansion using insertModeKeyBindingsNonRecursive and/or normalModeKeyBindingNonRecursive.
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
```json
2018-06-17 03:19:32 +03:00
"vim.normalModeKeyBindingsNonRecursive": [
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
{
"before": ["j"],
"after": ["g", "j"]
}
]
```
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
### Status bar color settings
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
Almost like vim-airline in VSCode!
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
#### `"vim.statusBarColorControl"`
> :warning: Experimental feature. Due to VSCode API limitations, this function modifies settings.json in the workspace resulting in latency and a constant changing diff in your working directory (see [issue#2124](https://github.com/VSCodeVim/Vim/issues/2124)).
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* Control status bar color based on current mode
* Type: Boolean (Default: `false`)
Once enabled, configure `"vim.statusBarColors"`. Colors can be defined for each mode either as `string` (background only), or `string[]` (background, foreground).
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
```json
"vim.statusBarColorControl": true,
"vim.statusBarColors": {
"normal": ["#8FBCBB", "#434C5E"],
"insert": "#BF616A",
"visual": "#B48EAD",
"visualline": "#B48EAD",
"visualblock": "#A3BE8C",
"replace": "#D08770"
}
```
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
### Vim settings
Configuration settings that have been copied from vim. Vim settings are loaded in the following sequence:
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
1. `:set {setting}`
2. `vim.{setting}` from user/workspace settings.
3. VSCode settings
4. VSCodeVim default values
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
#### `"vim.ignorecase"`
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* Ignore case in search patterns
* Type: Boolean (Default: `true`)
2016-11-29 21:44:01 +03:00
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
#### `"vim.smartcase"`
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* Override the 'ignorecase' setting if the search pattern contains upper case characters
* Type: Boolean (Default: `true`)
2016-07-04 20:05:53 +03:00
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
#### `"vim.hlsearch"`
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* When there is a previous search pattern, highlight all its matches
* Type: Boolean (Default: `false`)
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
#### `"vim.incsearch"`
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* Show the next search match while you're searching.
* Type: Boolean (Default: `true`)
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
#### `"vim.autoindent"`
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* Copy indent from current line when starting a new line
* Type: Boolean (Default: `true`)
2016-12-04 03:50:03 +03:00
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
#### `"vim.timeout"`
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* Timeout in milliseconds for remapped commands
* Type: Number (Default: `1000`)
2016-12-05 04:21:36 +03:00
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
#### `"vim.showcmd"`
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* Show the text of any command you are in the middle of writing.
* Type: Boolean (Default: `true`)
#### `"vim.showmodename"`
* Show the name of the current mode in the statusbar.
* Type: Boolean (Default: `true`)
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
#### `"vim.textwidth"`
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* Width to word-wrap to when using `gq`.
* Type: number (Default: `80`)
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
#### `"vim.leader"`
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
* What key should `<leader>` map to in key remappings?
* Type: string (Default: `\`)
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
## Multi-Cursor mode
> :warning: Multi-Cursor mode is experimental. Please report issues in our [feedback thread.](https://github.com/VSCodeVim/Vim/issues/824)
### Entering into multi-cursor mode
Enter multi-cursor mode by:
* Pressing `cmd-d` on OSX.
* Running "Add Cursor Above/Below" or the shortcut on any platform.
* Pressing `gb`, a new shortcut we added which is equivalent to `cmd-d` on OSX or `ctrl-d` on Windows. (It adds another cursor at the next word that matches the word the cursor is currently on.)
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
### Doing stuff
Now that you have multiple cursors, you should be able to use Vim commands as you see fit. Most should work; some are unsupported (ref [PR#587](https://github.com/VSCodeVim/Vim/pull/587)).
* Each cursor has its own clipboard.
* Pressing Escape in Multi-Cursor Visual Mode will bring you to Multi-Cursor Normal mode. Pressing it again will return you to Normal mode.
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
## Emulated plugins
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
### vim-easymotion
Based on [vim-easymotion](https://github.com/easymotion/vim-easymotion). To activate easymotion, you need to make sure that `easymotion` is set to `true` in settings.json (default is `false`).
2016-12-05 09:24:44 +03:00
Once easymotion is active, initiate motions using the following commands. After you initiate the motion, text decorators/markers will be displayed and you can press the keys displayed to jump to that position. `leader` is configurable and is `\` by default.
2016-12-05 09:24:44 +03:00
Motion Command | Description
---|--------
`<leader><leader> s <char>`|Search character
`<leader><leader> f <char>`|Find character forwards
`<leader><leader> F <char>`|Find character backwards
`<leader><leader> t <char>`|Til character forwards
`<leader><leader> T <char>`|Til character backwards
`<leader><leader> w`|Start of word forwards
`<leader><leader> b`|Start of word backwards
2018-05-03 11:32:50 +03:00
`<leader><leader> l`|matches beginning & ending of word, camelCase, after _ and after # forwards
2018-05-03 11:33:18 +03:00
`<leader><leader> h`|matches beginning & ending of word, camelCase, after _ and after # backwards
`<leader><leader> e`|End of word forwards
`<leader><leader> ge`|End of word backwards
`<leader><leader> j`|Start of line forwards
`<leader><leader> k`|Start of line backwards
`<leader><leader> / <char>... <CR>`|Search n-character
`<leader><leader><leader> bdt`|Til character
`<leader><leader><leader> bdw`|Start of word
`<leader><leader><leader> bde`|End of word
`<leader><leader><leader> bdjk`|Start of line
`<leader><leader><leader> j`|JumpToAnywhere motion; default behavior matches beginning & ending of word, camelCase, after _ and after #
`<leader><leader> (2s|2f|2F|2t|2T) <char><char>` and `<leader><leader><leader> bd2t <char>char>` are also available.
The difference is character count required for search.
For example, `<leader><leader> 2s <char><char>` requires two characters, and search by two characters.
This mapping is not a standard mapping, so it is recommended to use your custom mapping.
2016-12-05 09:24:44 +03:00
You can customize the appearance of easymotion markers (the boxes with letters) using the following settings:
2017-04-11 21:11:09 +03:00
Setting | Description
---|--------
`vim.easymotionMarkerBackgroundColor`|The background color of the marker box.
`vim.easymotionMarkerForegroundColorOneChar`|The font color for one-character markers.
2017-04-11 21:16:20 +03:00
`vim.easymotionMarkerForegroundColorTwoChar`|The font color for two-character markers, used to differentiate from one-character markers.
2017-04-11 21:11:09 +03:00
`vim.easymotionMarkerWidthPerChar`|The width in pixels allotted to each character.
`vim.easymotionMarkerHeight`|The height of the marker.
`vim.easymotionMarkerFontFamily`|The font family used for the marker text.
`vim.easymotionMarkerFontSize`|The font size used for the marker text.
`vim.easymotionMarkerFontWeight`|The font weight used for the marker text.
2017-04-11 21:12:16 +03:00
`vim.easymotionMarkerYOffset`|The distance between the top of the marker and the text (will typically need some adjusting if height or font size have been changed).
2017-09-03 08:40:04 +03:00
`vim.easymotionKeys`|The characters used for jump marker name
`vim.easymotionJumpToAnywhereRegex`| Custom regex to match for JumpToAnywhere motion (analogous to `Easymotion_re_anywhere`). Example setting (which also matches start & end of line, as well as Javascript comments in addition to the regular behavior (note the double escaping required): ^\\s*.|\\b[A-Za-z0-9]|[A-Za-z0-9]\\b|_.|\\#.|[a-z][A-Z]|//|.$"
2016-12-05 09:24:44 +03:00
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
### vim-surround
2017-03-19 10:53:15 +03:00
Based on [surround.vim](https://github.com/tpope/vim-surround), the plugin is used to work with surrounding characters like parenthesis, brackets, quotes, and XML tags.
2017-03-19 10:53:15 +03:00
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
`t` or `<` as `<desired char>` or `<existing char>` will do tags and enter tag entry mode.
2017-03-19 10:53:15 +03:00
Surround is enabled by default, but can be disabled by setting `"vim.surround": false`.
2017-03-19 10:53:15 +03:00
Surround Command | Description
---|--------
`d s <existing char>`|Delete existing surround
`c s <existing char> <desired char>`|Change surround existing to desired
`y s <motion> <desired char>`|Surround something with something using motion (as in "you surround")
`S <desired char>`|Surround when in visual modes (surrounds full selection)
Some examples:
* `"test"` with cursor inside quotes type cs"' to end up with `'test'`
* `"test"` with cursor inside quotes type ds" to end up with `test`
* `"test"` with cursor inside quotes type cs"t and enter 123> to end up with `<123>test</123>`
* `test` with cursor on word test type ysaw) to end up with `(test)`
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
### vim-commentary
Similar to [vim-commentary](https://github.com/tpope/vim-commentary), but uses the VSCode native "Toggle Line Comment" and "Toggle Block Comment" features.
Usage examples:
* `gc` - toggles line comment. For example `gcc` to toggle line comment for current line and `gc2j` to toggle line comments for the current line and the next two lines.
* `gC` - toggles block comment. For example `gCi)` to comment out everything within parenthesis.
### vim-indent-object
Based on [vim-indent-object](https://github.com/michaeljsmith/vim-indent-object), it allows for treating blocks of code at the current indentation level as text objects. Useful in languages that don't use braces around statements (e.g. Python).
Provided there is a new line between the opening and closing braces / tag, it can be considered an agnostic `cib`/`ci{`/`ci[`/`cit`.
Command | Description
---|--------
`<operator>ii`|This indentation level
`<operator>ai`|This indentation level and the line above (think `if` statements in Python)
`<operator>aI`|This indentation level, the line above, and the line after (think `if` statements in C/C++/Java/etc)
2018-01-18 18:09:28 +03:00
### vim-sneak
Based on [vim-sneak](https://github.com/justinmk/vim-sneak). To activate sneak, you need to make sure that `sneak` is set to `true` in settings.json (default is `false`).
Once sneak is active, initiate motions using the following commands. For operators sneak uses `z` instead of `s` because `s` is already taken by the surround plugin.
Motion Command | Description
---|--------
`s<char><char>`|Move forward to the first occurence of `<char><char>`
`S<char><char>`|Move backward to the first occurence of `<char><char>`
`<operator>z<char><char>`|Perform `<operator>` forward to the first occurence of `<char><char>`
`<operator>Z<char><char>`|Perform `<operator>` backward to the first occurence of `<char><char>`
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
## VSCodeVim tricks!
2018-01-24 11:04:57 +03:00
Vim has a lot of nifty tricks and we try to preserve some of them:
* `gd` - jump to definition.
* `gq` - on a visual selection reflow and wordwrap blocks of text, preserving commenting style. Great for formatting documentation comments.
* `gb` - adds another cursor on the next word it finds which is the same as the word under the cursor.
* `af` - visual mode command which selects increasingly large blocks of text. For example, if you had "blah (foo [bar 'ba|z'])" then it would select 'baz' first. If you pressed `af` again, it'd then select [bar 'baz'], and if you did it a third time it would select "(foo [bar 'baz'])".
* `gh` - equivalent to hovering your mouse over wherever the cursor is. Handy for seeing types and error messages without reaching for the mouse!
2017-03-03 13:23:52 +03:00
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
## F.A.Q.
### None of the vim `ctrl` (e.g. `ctrl+f`, `ctrl+v`) commands work
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
Set the [`useCtrlKeys` setting](#vimusectrlkeys) to `true`.
### Moving `j`/`k` over folds opens up the folds
2017-05-22 09:45:46 +03:00
Try setting `vim.foldfix` to `true`. This is a hack; it works fine, but there are side effects (see [issue#22276](https://github.com/Microsoft/vscode/issues/22276)).
2017-05-22 09:45:46 +03:00
### Key repeat doesn't work
2017-05-22 09:45:46 +03:00
Are you on a Mac? Did you go through our [mac-setup](#mac-setup) instructions?
2017-05-22 09:45:46 +03:00
### There are annoying intellisense/notifications/popups that I can't close with `<esc>`! Or I'm in a snippet and I want to close intellisense
2017-05-22 09:45:46 +03:00
Press `shift+<esc>` to close all of those boxes.
README enhancements (#1547) * Reformat the heading (add logo, centered styling) The HTML is supported in the VS Code Marketplace site too, and this is layout is shamelessly stolen from the Chrome Debugger plugin: https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome * Normalize how we reference the real Vim plugins This what their repos are named, and make our README look more consistent. * Remove reference to useCtrlKeys in features list It's enabled by default, and so isn't really a feature. * Bulk refactoring of README * Re-arrange certain sections based on importance * Promoted plugin info to it's own section * Add contents * Bunch of other small formatting tweaks * Simply plugins point in features They're outlined nicely in the contents area just below, seems like overkill to have them all listed here too. * Add Contents link to status bar customization (vim-airline) * Push FAQ further down the page The tricks list is cooler (read: more important) * Additional language/linking tweaks * Add 'json' language to code blocks And clean up extra closing backticks * Prefer "setting" over "option" or "configuration" This is in-line with terminology in VSCode (i.e. `settings.json`). * Fix heading numbers and use Sentence case * Fix formatting and indentation issues * Move Key remppaing under settings And move `useCtrlKeys` and `handleKeys` into VSCodeVim Settings. * Add OS-specific setup sub-sections * More heading tweaks * Add more links to useCtrlKeys and handleKeys * Fix formatting with backticks The stuff between the <...> was getting drop because Markdown parsers think that it's HMTL tags ;) * Fix typo * More heading level and case fixes * Add quick-link to `gc` docs * Format VSCode Vim tricks list consistently * Test: backticks around settings headings * Make setting's headings map to JSON keys * Fix Contents link to Emulated plugins * Tweaks to Contributing and Release notes * Tight up features some more * Introduce "Getting started" section with OS-setup info It didn't make sense to have Settings-related info here. The quick example settings has been more to the start of the Settings section. * Add sub-section on compatibility with link to ROADMAP * Remove duplicate info about key repeat issues on Mac * Tweak waffling * Small grammar fix
2017-04-24 03:26:04 +03:00
## Contributing
This project is maintained by a group of awesome [people](https://github.com/VSCodeVim/Vim/graphs/contributors) and contributions are extremely welcome :heart:. For a quick tutorial on how you can help, see our [contributing guide](/.github/CONTRIBUTING.md).
### Special shoutouts to cool contributors
2016-12-30 22:38:29 +03:00
* Thanks to @xconverge for making over 100 commits to the repo. If you're wondering why your least favorite bug packed up and left, it was probably him.
* Thanks to @Metamist for implementing EasyMotion!
* Thanks to @sectioneight for implementing text objects!
* Special props to [Kevin Coleman](http://kevincoleman.io), who created our awesome logo!
* Shoutout to @chillee aka Horace He for his contributions and hard work.