Arrow keys to navigate within soft-wrapped text block.
See original GitHub issueThanks in advance. I’m sorry if this has an easy fix. I did spend quite a bit of time trying to find a solution or a configuration option and I hope I didn’t miss something trivial. I also poked around the Slack channel but must have joined at a slow time.
Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT maybe? Probably FEATURE REQUEST?
What happened: See https://github.com/Microsoft/vscode/issues/34448 . The arrow keys don’t allow me to navigate among visual (soft-wrapped) lines in any mode. I have remapped j
and k
to gj
and gk
in non-insert modes, but in insert mode, I get around with the arrow keys.
What did you expect to happen: I expect (or at least wish) that navigation with arrow keys works as it does with vanilla VS Code. That is, I want to navigate up and down within soft-wrapped lines using the arrow keys (or at least have the option to enable it.)
How to reproduce it (as minimally and precisely as possible): Type a long line with soft wrap, and then try to navigate within it.
Environment: Ubuntu, Xmonad based custom desktop environment using Xorg.
- Extension (VsCodeVim) version: v0.11.0
- VSCode version: 1.20.1
- OS version: 17.10.1
Issue Analytics
- State:
- Created 6 years ago
- Reactions:6
- Comments:10 (7 by maintainers)
Top GitHub Comments
On the Slack channel, some helpful people pointed out that I should avoid using the arrow keys anyway, as there are almost always better ways to move about in normal-mode. I think that’s largely true. Although I already use a lot of vim movement commands effectively, I’m compelled to work harder to build more effective habits when working in a very small neighbourhood of a file (where I would normally default to using arrows).
In the meantime, a suitable workaround is to rebind the keys. I tried this, of course, before posting the issue, but I didn’t know well enough to apply
<C-o>
first:Thanks to @arussellk, @Nick and @chillee from the slack. https://vscodevim.slack.com/archives/C0ENQMTUM/p1520358214000115
Now that the documentation PR is open, you can probably close this one @timtro.