[X] I have searched the existing issues of flash.nvim
[X] I have searched the existing issues of plugins related to this issue
Neovim version (nvim -v)
0.9.4
Operating system/version
Debian 12
Describe the bug
t is remapped to something else. In this case, to flash.jump()
On the very first time of entering a file in neovim, pressing t properly calls flash.jump(). Any subsequent presses of t invokes the enhahced t motions. The enhanced t motions are disabled properly if jump were remapped to anything else like b. These are all true as well when done with f.
Pressing t should always invoke flash.jump() and not revert back to enhanced t motions.
Additional
i have modes = { search = { enabled = false } } and it also suffers from this. Once behavior regresses back to enhanced motions, it seems that the plugin options are all reset. This is only triggered when using the remapped t or f.
Did you check docs and existing issues?
Neovim version (nvim -v)
0.9.4
Operating system/version
Debian 12
Describe the bug
t
is remapped to something else. In this case, toflash.jump()
On the very first time of entering a file in neovim, pressing
t
properly callsflash.jump()
. Any subsequent presses oft
invokes the enhahced t motions. The enhanced t motions are disabled properly if jump were remapped to anything else likeb
. These are all true as well when done withf
.I've also tried to set the keymaps like so but no fixes.
Steps To Reproduce
t
.t
flash.jump()
is invokedt
again.Expected Behavior
Pressing
t
should always invokeflash.jump()
and not revert back to enhanced t motions.Additional
i have
modes = { search = { enabled = false } }
and it also suffers from this. Once behavior regresses back to enhanced motions, it seems that the plugin options are all reset. This is only triggered when using the remappedt
orf
.