This is a pretty massive change; see pull request #4735 for full details
Most notably:
- Support for operator-pending mode, including remaps and a half-cursor decoration
- Correct handling of ambiguous remaps with timeout
- Correct handling of recursive special case when the RHS starts with the LHS
- Correct handling of multi-key remaps in insert mode
- Failed movements that occur partway through a remap stop & discard the rest of the remap
- Implement `unmap` and `mapclear` in .vimrc
Refs #463, refs #4908Fixes#1261, fixes#1398, fixes#1579, fixes#1821, fixes#1835Fixes#1870, fixes#1883, fixes#2041, fixes#2234, fixes#2466Fixes#2897, fixes#2955, fixes#2975, fixes#3082, fixes#3086Fixes#3171, fixes#3373, fixes#3413, fixes#3742, fixes#3768Fixes#3988, fixes#4057, fixes#4118, fixes#4236, fixes#4353Fixes#4464, fixes#4530, fixes#4532, fixes#4563, fixes#4674Fixes#4756, fixes#4883, fixes#4928, fixes#4991, fixes#5016Fixes#5057, fixes#5067, fixes#5084, fixes#5125
- Make easymotion default decorations have the same defaults as the Vim
plugin.
- Deprecate no longer needed configurations like
'easymotionMarkerMargin' and 'easymotionMarkerWidthPerChar'.
- Change 'easymotionMarkerFontWeight' default to 'bold'
- Add seperate color for each character of two-character markers,
default values are the same as the Vim plugin. (two different yellows)
- Add color for dimmed characters, default value is the same as the Vim
plugin. (grey)
- Add color for higlighting characters searched with search n-characters
command, default value is the same as the Vim
plugin. (green)
- Add changes to README file and update the default values.
- Change easymotion TextEditorDecorations to make them simpler to use
and understand. Remove all unnecessary parts.
- Fix the dimming zones that were including the markers as well.
- Fix the hack for two consecutive markers that wasn't checking if those
markers were on the same line.
Fixes#5092Fixes#5022Fixes#4252Fixes#1746
The current easymotion decorations are kinda wonky, they are misaligned and little bit intrusive, also it deviates from the official easymotion. With this pr it behaves more like the official
Fixes#4610Fixes#4524Fixes#3899Fixes#2938
The workaround for linux key changes & vsCode, which is displayed on line 713 ( "keyboard.dispatch": "keyCode" ) had 'keycode' but it should be 'keyCode'. Using 'keycode' does not resolve the issue. The link 'known issue in VS Code' has the solution in it, and they also use keyCode. I've tested that keyCode resolves the issue still.
This PR implements two text-objects from the vim-textobj-entire plugin
This Vim plugin adds two useful text-objects:
ae which represents the entire content of a buffer
ie which represents the entire content of a buffer without the leading and trailing spaces.
You can then use gUae to transform the whole text buffer content in uppercase, whereas normally you would have to use gggUG.
This text-object has the advantage that you can use it from anywhere your cursor is currently located, you don't have to be conscious of the cursor position.
Fixes#3379
* many people seem to copy the 'quick example' from the readme as
their initial config. The problem with that quick example is that it
enables 'sneak', which by defaults breaks the S and s commands (see
issue #3274).
* by removing that setting from the example, people should have a
working config out of the box. If someone is interested in sneak,
other sections of the readme still go into details.
Small documentation change.
Change the expression "extension menu" to "extension view" to match
vscode documentation.
Adding a couple of details about how to get to this extension's contribution
page for people new to vscode.
Read key remapping commands from $HOME/.vimrc, $HOME/_vimrc, or a
user-specified Vim configuration file. For each, build an IKeyRemapping
object and append it to the appropriate collection, _if_ doing so will
not override a remapping specified in the VS Code settings.
Partially addresses #463. This implementation borrows heavily from
Sheepolution/vimrc-to-json.
* Add `editVimrc` command
* Add .vimrc validator, correct usage of new config names
* Source .vimrc automatically after saving it
Note that this already works without the change, but the five modes
added in this commit aren't officially listed as options. The default
coloring for each appears to be the same as the standard VSCode
coloring, which happens to be #007ACC
In the README, a number of nifty tricks are referenced, however, the text incorrectly refers to these features as being Vim features. While `gd` and `gq` are standard, `af`, `gb` and `gh` are not standard vim features. What is probably intended is that these features are VSCode features adapted for VSCodeVim.
Fixes broken links regarding logging level settings. As far as
I can tell, these links have never been valid, and should direct
to the information regarding VSCodeVim's settings.
