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
I have searched the existing issues of plugins related to this issue
Neovim version (nvim -v)
NVIM v0.10.0-dev-541+g96b94f8d7
Operating system/version
Pop!_OS 22.04 LTS
Describe the bug
Any custom options that I add in opts.mode.<mode> are not overriding the default options. Additionally, the docs seem to say you can define custom modes that are used if we use jump{mode = "<mode>"}, which doesn't work either.
Did you check docs and existing issues?
Neovim version (nvim -v)
NVIM v0.10.0-dev-541+g96b94f8d7
Operating system/version
Pop!_OS 22.04 LTS
Describe the bug
Any custom options that I add in
opts.mode.<mode>
are not overriding the default options. Additionally, the docs seem to say you can define custom modes that are used if we usejump{mode = "<mode>"}
, which doesn't work either.It seems the line in question is here:
https://github.com/folke/flash.nvim/blob/de34c832af2498c6954e34d3c08cf143f92f3d6b/lua/flash/config.lua#LL136C31-L136C31
Should this be
options.modes[opts.mode]
?Steps To Reproduce
treesitter = { labels = "zyx" },
vS
and see that the default labels are usedfuzzy = { search = { mode = "fuzzy" } },
and keymappingrequire("flash").jump({ mode = "fuzzy" })
sab
and see that exact matching is used instead of fuzzyExpected Behavior
Being able to override the options and create modes
Repro
The text was updated successfully, but these errors were encountered: