0xAdk / full_visual_line.nvim

Enhance neovim's visual line mode with fully highlighted lines
MIT License
29 stars 2 forks source link

Full line not triggered with Whichkey enabled #4

Open jonathf opened 1 month ago

jonathf commented 1 month ago

I am using ~Noice.nvim~Whichkey.nvim. When enabled, full_visual_line does not trigger on the push of V. 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.

0xAdk commented 1 month ago

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.nvim ```lua local 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 `nvim -u config.lua`
jonathf commented 1 month ago

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 = {},
  }
})
0xAdk commented 1 month ago

I don't have a fix yet, but I do know it only happens if you're using both which key and lazy's keys lazy loading feature.

A workaround is just to not lazy load the plugin:

{
    '0xAdk/full_visual_line.nvim',
    opts = {},
},