Open tomtomjhj opened 3 weeks ago
This suggests that after I did something with code action (which I don't remember), the context was not clearly properly.
Most likely, it would help if you have some direction on this, does it happen after a while or sometimes at the first couple of invokes? Does it happen with a specific language server or different ones?
https://github.com/ibhagwan/fzf-lua/commit/a3f66ca0b9787129b13cc6bb491bb20476ba2da9
@tomtomjhj, the above should solve this issue regardless of repro steps.
thanks!
@tomtomjhj, revered due to https://github.com/ibhagwan/fzf-lua/commit/a3f66ca0b9787129b13cc6bb491bb20476ba2da9#commitcomment-149465672, I wasn’t too happy with this “fix” anyway as it wasn’t addressing the exact conditions causing the CTX to not be cleared.
Will await accurate reproduction conditions if you can provide such.
RTFM Checklist
man fzf
/ I am well versed in shell fzfOperating system
ubuntu 22.04
Shell
bash
Neovim version (
nvim --version
)nightly (b34e137e43)
Fzf version (
fzf --version
)0.56.0 (ff16877)
Output of
:lua print(os.getenv('FZF_DEFAULT_OPTS'))
--bind alt-a:select-all,alt-d:deselect-all,alt-t:toggle-all --color=dark
Is the problem reproducible with
mini.sh
?mini.sh
mini.sh
mini.sh
(not relevant, requires LSP, Windows, etc)Fzf-lua configuration
Describe the bug / steps to reproduce
When I ran
require('fzf-lua').lsp_references{jump_to_single_result=true}
, I gotThis happens very rarely, so I don't have a good reproducer. Instead, I added this line to see what caused the error when it happens
Here is the value of
__CTX
when the error occurred:This suggests that after I did something with code action (which I don't remember), the context was not clearly properly.