Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Page movements don't affect cursor

See original GitHub issue

<C-d>, <C-u>, <C-f>, and <C-b> all move the view but not the cursor, which is inconsistent with native Neovim behavior, which is to move the cursor a half/full screen and only adjust the view if necessary.

Issue Analytics

State:
Created 3 years ago
Reactions:14
Comments:8 (2 by maintainers)

Top GitHub Comments

4reactions

wcauchoiscommented, Jan 18, 2021

You’ve gotten a new contributor 😃 - I think #528 will do the trick but happy to respond to any comments.

This is my first time dev’ing an extension, VS Code makes it pretty slick actually!

3reactions

AleksueiRcommented, Mar 25, 2022

As a workaround, I tried remap <C-u/d> to simple movements, but that doesn’t work in VSCode (works in nvim though). Any ideas why?
nnoremap <C-d> 20j
nnoremap <C-u> 20k

Ah, my bad, <C-d> and <C-u> are default VSCode shortcuts and they take precedence. Adding the following to keybindings.json helped:

    { "key": "ctrl+d", "command": "vscode-neovim.send", "args": "<c-d>", "when": "editorTextFocus && neovim.init" },
    { "key": "ctrl+u", "command": "vscode-neovim.send", "args": "<c-u>", "when": "editorTextFocus && neovim.init" },