diff options
| author | bors[bot] <bors[bot]@users.noreply.github.com> | 2019-02-07 12:42:53 +0000 |
|---|---|---|
| committer | bors[bot] <bors[bot]@users.noreply.github.com> | 2019-02-07 12:42:53 +0000 |
| commit | d0fd05142f45fb69a9dc64bfd55d2453b1927b9c (patch) | |
| tree | c16c666f8b6176e9a055464f8b19022458853408 /crates/ra_syntax/tests/data/parser/err/0025_nope.rs | |
| parent | a69ee774ca39f1300bd9dd7eb34b632db9098e26 (diff) | |
| parent | a4d0aebcb89367d23600d0f14ba2c7f1cd0bbb44 (diff) | |
Merge #755
755: Add new configuration "enableEnhancedTyping" to control registering of "type" command r=matklad a=vipentti
This further fixes problems when having a VIM extension (at least vscodevim)
enabled, by not calling `overrideCommand('type', commands.onEnter.handle)` when
enableEnhancedTyping is set to `false`.
The problem is dependent on the order in which extensions are activated, if
rust-analyzer is activated before `vscodevim`, rust-analyzer will register the
`type` command, and when `vscodevim` finally attempts to activate, it will fail
to register the command. This causes `vscodevim` to stop working properly.
This setting allows users to disable the registerCommand `type` in
rust-analyzer, allowing `vscodevim` to work. The setting defaults to `true`.
Currently changing the setting requires reloading of the window.
Co-authored-by: Ville Penttinen <[email protected]>
Diffstat (limited to 'crates/ra_syntax/tests/data/parser/err/0025_nope.rs')
0 files changed, 0 insertions, 0 deletions