-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
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
Full line not triggered with Whichkey enabled #4
Comments
I can try and repo this later, but if you could give a mino config that reproduces the error that would help a lot. example config.lua for lazy.nvimlocal plug_dir = vim.env.HOME .. '/.local/share/nvim/lazy'
vim.opt.rtp:append {
plug_dir .. '/full_visual_line.nvim',
plug_dir .. '/foo.nvim',
}
require 'full_visual_line'.setup {} open with |
Here is the minimal config that reproduces the error: local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim"
vim.opt.rtp:prepend(lazypath)
require "lazy".setup({
{
"0xAdk/full_visual_line.nvim",
keys = "V",
opts = {},
},
{
"folke/which-key.nvim",
opts = {},
}
}) |
jonathf
changed the title
Full line not triggered with Noice enabled
Full line not triggered with Whichkey enabled
Jul 19, 2024
3 tasks
I don't have a fix yet, but I do know it only happens if you're using both which key and lazy's A workaround is just to not lazy load the plugin: {
'0xAdk/full_visual_line.nvim',
opts = {},
}, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am using
Noice.nvimWhichkey.nvim. When enabled, full_visual_line does not trigger on the push ofV
. Instead another butten needs to be pressed by the user to trigger the full visual line.Is there a way to get full visual line to work in this svenario?
EDIT:
wrong plugin. A bit to hasty in my writing.
The text was updated successfully, but these errors were encountered: