The VSCodeVim team prioritizes issues based on reaction count.
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Environment:
latest MACOS + latest VSCode + VSCodeVim
What happened:
In "Insert" mode,
But they have no effect.
I notice that
{ "key": "ctrl+f", "command": "extension.vim_ctrl+f",
"when": "editorTextFocus && vim.active && vim.use
{ "key": "ctrl+b", "command": "extension.vim_ctrl+b",
"when": "editorTextFocus && vim.active && vim.use
I think "vim.mode != 'Insert'" should be applied to every "Normal" mode commands, like ^a, ^f, ^e, ^d ...
What did you expect to happen:
How to reproduce it:
+1
I really want use ^a, ^f, ^e, ^b to control my cursor , because I use Mac . So I want to know how to remap these keys.
this problem is resolve;you can config keybinding.json
@wYuanHpp can you give an example how to bind ctrl+f to move forward a char in insertmode?
@reducm here is an example shows how to move cursor in insert mode
{
// Ctrl-h : Move backward
"key": "ctrl+h",
"command": "extension.vim_left",
"when": "editorTextFocus && vim.active && vim.mode == 'Insert' && !inDebugRepl"
},
{
// Ctrl-l : Move foward
"key": "ctrl+l",
"command": "extension.vim_right",
"when": "editorTextFocus && vim.active && vim.mode == 'Insert' && !inDebugRepl"
},
{
// Ctrl-l : Move upward
"key": "ctrl+k",
"command": "extension.vim_up",
"when": "editorTextFocus && vim.active && vim.mode == 'Insert' && !inDebugRepl"
},
{
// Ctrl-l : Move downward
"key": "ctrl+j",
"command": "extension.vim_down",
"when": "editorTextFocus && vim.active && vim.mode == 'Insert' && !inDebugRepl"
}
I believe this is a dupe of https://github.com/VSCodeVim/Vim/issues/3126. The fix will be included in our next release 1.0.4
Most helpful comment
@reducm here is an example shows how to move cursor in insert mode