Closed 0x00-ketsu closed 1 year ago
wired .I can't reproduce ..
gitsigns.nvim
commit : dc2962f
(latest)
Did anyone find a solution for this?
Should I open a new issue in gitsigns.nvim
repo?
BTW, I don't think this is a gitsigns.nvim
bug; Because I checked out commit from 2 months ago, and the problem persists.
I just checked out the lspsaga.nvim
commit from last month, and it works fine; So I think this issue should be reopened.
this issue has been fixed
I have updated to the latest version.
I don't get the error, but I still get the exact same thing as show in the above picture (i.e. gitsigns.nvim
actions).
What do you mean? I don't get your problem? No error .so what is the problem?
If you look at the top picture, instead of showing code actions for fixing problems (like auto import, etc.), it only shows gitsigns.nvim
commands.
Why show auto import?there is no lsp actions it has import fmt? All the code of picture is correct?
It was just an example. If there's an error, and you try to do Lspsaga diagnostic_jump_next
, it won't show the options for code action. It only shows gitsigns
actions.
So here's a simple example. It says fix available, but doesn't show anything.
I think igot your point ,test later reopen
thanks
does vim.lsp.buf.code action has output?
It works now. Thanks
Describe the bug
Steps to reproduce
main.go
min.lua
Expected behavior
Can do code actions.
Neovim version (nvim -v)
0.9.1
lspsaga commit
8a05cb1
Terminal name/version
iterm2 3.4.19