feature: mappings to scroll commands

[Etavioxy]

Did you check the docs?

• I have read all the vscode-neovim docs
• I understand the fundamental limitations of the plugin and believe this request to be reasonable

Is your feature request related to a problem? Please describe.

vscode-neovim/vim/vscode-scrolling.vim

Lines 32 to 46 in 4a1b5fa

	" Disabled due to scroll problems (the ext binds them directly)
	" nnoremap <silent> <expr> <C-d> VSCodeExtensionNotify('scroll', 'halfPage', 'down')
	" xnoremap <silent> <expr> <C-d> VSCodeExtensionNotify('scroll', 'halfPage', 'down')
	" nnoremap <silent> <expr> <C-u> VSCodeExtensionNotify('scroll', 'halfPage', 'up')
	" xnoremap <silent> <expr> <C-u> VSCodeExtensionNotify('scroll', 'halfPage', 'up')
	" nnoremap <silent> <expr> <C-f> VSCodeExtensionNotify('scroll', 'page', 'down')
	" xnoremap <silent> <expr> <C-f> VSCodeExtensionNotify('scroll', 'page', 'down')
	" nnoremap <silent> <expr> <C-b> VSCodeExtensionNotify('scroll', 'page', 'up')
	" xnoremap <silent> <expr> <C-b> VSCodeExtensionNotify('scroll', 'page', 'up')
	" nnoremap <silent> <expr> <C-e> VSCodeExtensionNotify('scroll-line', 'down')
	" xnoremap <silent> <expr> <C-e> VSCodeExtensionNotify('scroll-line', 'down')
	" nnoremap <silent> <expr> <C-y> VSCodeExtensionNotify('scroll-line', 'up')
	" xnoremap <silent> <expr> <C-y> VSCodeExtensionNotify('scroll-line', 'up')

i want to bind them to some keys, but the extension bind them directly. i can't find out how to bind them.

Describe the solution you'd like

expose these commands as functions, or directly as original keys

Describe alternatives you've considered

.

Additional context

No response

[Etavioxy]

I'm using this script now

no <expr> , char2nr(getcharsearch().char)==13 ? '<Cmd>lua require("vscode-neovim").call("editorScroll", {args={to="up",by="line",value=3}})<CR>' : ','
 no <expr> . char2nr(getcharsearch().char)==13 ? '<Cmd>lua require("vscode-neovim").call("editorScroll", {args={to="down",by="line",value=3}})<CR>' : ';'

[Guh-Feng]

Hello there, I wanted to rebind these keys too and took a look at some of the source files. I figured out that you have to delete the normal mode bindings in VSCode's Keyboard Shortcuts panel and then add them back in the kebindings.json file as shown below. The key was to change the "command" argument to "vscode-neovim.send" and add the "args" portion too.

{
        "key": "ctrl+e",
        "command": "vscode-neovim.send",
        "when": "editorTextFocus && neovim.ctrlKeysNormal.e && neovim.init && neovim.mode != 'insert' && editorLangId not in 'neovim.editorLangIdExclusions'",
        "args": "<C-e>"
    },
    {
        "key": "ctrl+d",
        "command": "vscode-neovim.send",
        "when": "editorTextFocus && neovim.ctrlKeysNormal.d && neovim.init && neovim.mode != 'insert' && editorLangId not in 'neovim.editorLangIdExclusions'",
        "args": "<C-d>"
    },
    {
        "key": "ctrl+f",
        "command": "vscode-neovim.send",
        "when": "editorTextFocus && neovim.ctrlKeysNormal.f && neovim.init && neovim.mode != 'insert' && editorLangId not in 'neovim.editorLangIdExclusions'",
        "args": "<C-f>"
    }