diff options
| author | Ville Penttinen <[email protected]> | 2019-02-07 10:37:36 +0000 |
|---|---|---|
| committer | Ville Penttinen <[email protected]> | 2019-02-07 10:37:36 +0000 |
| commit | 77a4a311fe22ac3b786378c452ab0f60e289cf87 (patch) | |
| tree | 3deca42c8e3a5799d9ce83ce798c746164d2ed93 /crates/ra_syntax/tests/data/lexer/0014_unclosed_char.rs | |
| parent | 736a55c97e69f95e6ff4a0c3dafb2018e8ea05f9 (diff) | |
Add new configuration "enableEnhancedTyping" to control registering of "type" command
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.
Diffstat (limited to 'crates/ra_syntax/tests/data/lexer/0014_unclosed_char.rs')
0 files changed, 0 insertions, 0 deletions