You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the vim.mode == 'Replace' wont evaluate to true if I try to r{char}.
furthermore, to work around this, making r start a visual selection first with something like
{// weird ass workaround to get vim.mode == 'Replace' to work properly. // basically, when starting a replace always make sure that a visual selection of 1 character under the cursor is made"key": "r","when": "inputFocus && vim.mode == 'Normal'","command": "vim.remap","args": {"after": ["v","r"],"silent": true,}},
manages to qualify the vim.mode == 'Replace' clause, suggesting it's a bug where r, when used on its own, doesn't get interpreted as being in replace mode
try replacing a character with n via rn, or N via rN
Environment:
Extension (VsCodeVim) version: 1.28.1
VSCode version: 1.95.3
OS: Windows
The text was updated successfully, but these errors were encountered:
kaem-e
changed the title
vim.mode = 'Replace' doesnt evaluate to true when using r on its ownvim.mode = 'Replace' doesn't evaluate to true when using r on its own
Nov 23, 2024
Encountered a weird bug where, with the following keybinding remap
the
vim.mode == 'Replace'
wont evaluate to true if I try tor{char}
.furthermore, to work around this, making
r
start a visual selection first with something likemanages to qualify the
vim.mode == 'Replace'
clause, suggesting it's a bug wherer
, when used on its own, doesn't get interpreted as being in replace modeTo Reproduce
keybindings.json
n
viarn
, orN
viarN
Environment:
The text was updated successfully, but these errors were encountered: