Closed rgauselumifi closed 1 month ago
The keymaps from LazyVim appear to be broken in version 3 too (I changed require("trouble").previous(..
to the new api; require("trouble").prev(..
):
This should be fixed now. Do let me know if you'd still encounter this!
Did you check docs and existing issues?
Neovim version (nvim -v)
0.10
Operating system/version
Ubuntu 22.04
Describe the bug
Most of the time, after running something like ':Trouble qflist toggle', if i then call ':lua require('trouble').next()' or ':Trouble next', it doesn't work correctly. If I move my cursor into the trouble window, and then execute ':lua require('trouble').next()', it does work.
This bug happens 80% of the time, but occasionally doesn't. To be clear, it only doesn't work if my cursor is not in the trouble buffer.
Steps To Reproduce
Expected Behavior
Should work with cursor outside of the buffer.
PS: side note, I noticed if I run the 'next' function when the trouble window is closed that an error occurs as the 'mode' has not been specified. I'm curious if there's a way to have the mode default to the last used one. That way if I populate the qflist or diagnostic list, I could close the trouble window and still navigate through the results.
Love the plugin, cheers my friend
Repro