We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.9.5
Windows 11
I have this mapping in my init.lua, which is supposed to center the current search result on screen:
vim.keymap.set("n", "n", "nzzzv")
While this work in neovim, it does not work in vscode-neovim.
Running the same command by hand in vscode-neovim (i.e. "n" to move to the next search result and then "zz" to center it on screen) works as expected.
There was a similar issue opened some time back (#767) but it got closed while the issue is still there.
Search results should be centered on screen.
The text was updated successfully, but these errors were encountered:
Currently valid alternative: Use vscode.call to call the vscode command to center the viewport
Sorry, something went wrong.
@uraza try sth like this:
vim.keymap.set("n", "*", function() vim.cmd(":norm! *") local curline = vim.fn.line(".") vscode.call("revealLine", { args = {lineNumber = curline, at = "center"} }) end, { noremap = true, silent = true })
No branches or pull requests
Check the following:
Neovim version (nvim -v)
0.9.5
Operating system/version
Windows 11
Describe the bug
I have this mapping in my init.lua, which is supposed to center the current search result on screen:
vim.keymap.set("n", "n", "nzzzv")
While this work in neovim, it does not work in vscode-neovim.
Running the same command by hand in vscode-neovim (i.e. "n" to move to the next search result and then "zz" to center it on screen) works as expected.
There was a similar issue opened some time back (#767) but it got closed while the issue is still there.
Steps To Reproduce
Expected Behavior
Search results should be centered on screen.
The text was updated successfully, but these errors were encountered: