You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default mappings for avante.nvim cause operator pending mode. this is highly undesirable - c is a very common motion. I was pulling my hair out trying to figure out why neovim suddenly felt so laggy.
I later learned about operator-pending mode and timeoutlen. I like that avante has a way to override timeoutlen when hovering over diffs, but I think this is still insufficient, and so is manually overriding the defaults to not conflict - the default experience should reflect what is recommended to users, and therefore should not conflict with any built-in vim bindings.
Continuing the status-quo will only result in hard to debug and very noticeable "lag" for end users.
To reproduce
default config
Expected behavior
basic vim motions should not feel laggy due to entering operator-pending mode.
Installation method
Use lazy.nvim:
{
"yetone/avante.nvim",
event="VeryLazy",
lazy=false,
version=false, -- set this if you want to always pull the latest changeopts= {
-- add any opts here
},
-- if you want to build from source then do `make BUILD_FROM_SOURCE=true`build="make",
-- build = "powershell -ExecutionPolicy Bypass -File Build.ps1 -BuildFromSource false" -- for windowsdependencies= {
"nvim-treesitter/nvim-treesitter",
"stevearc/dressing.nvim",
"nvim-lua/plenary.nvim",
"MunifTanjim/nui.nvim",
},
}
Describe the bug
The default mappings for avante.nvim cause operator pending mode. this is highly undesirable -
c
is a very common motion. I was pulling my hair out trying to figure out why neovim suddenly felt so laggy.I later learned about operator-pending mode and timeoutlen. I like that avante has a way to override timeoutlen when hovering over diffs, but I think this is still insufficient, and so is manually overriding the defaults to not conflict - the default experience should reflect what is recommended to users, and therefore should not conflict with any built-in vim bindings.
Continuing the status-quo will only result in hard to debug and very noticeable "lag" for end users.
To reproduce
default config
Expected behavior
basic vim motions should not feel laggy due to entering operator-pending mode.
Installation method
Use lazy.nvim:
Environment
❯ nvim --version
NVIM v0.10.2
Build type: Release
LuaJIT 2.1.1713773202
The text was updated successfully, but these errors were encountered: