-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: Invalid Window id Error #400
Labels
bug
Something isn't working
Comments
This is now fixed in Trouble v3. |
Awesome, took you 11 minutes, you're a machine 😄 I thought it's an edgy error, thanks for fixing |
i get a very similar error nowadays, using the following versions
i'm trying to use Trouble functions to jump around in the list of diagnostics local nmap = function(keys, func, desc, bufnr)
if desc then
desc = 'LSP: ' .. desc
end
vim.keymap.set('n', keys, func, { buffer = bufnr, silent = true, noremap = true, desc = desc })
end
-- ...
local trouble = require("trouble")
-- ...
local jump = function(fn)
return function() fn({skip_groups = true, jump = true}) end
end
nmap("<leader>ltj", jump(trouble.next), "Jump to next item")
nmap("<leader>ltk", jump(trouble.previous), "Jump to previous item")
nmap("<leader>ltg", jump(trouble.first), "Jump to first item")
nmap("<leader>ltG", jump(trouble.last), "Jump to last item")
-- ...
|
folke
added a commit
that referenced
this issue
May 30, 2024
folke
added a commit
that referenced
this issue
May 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Did you check docs and existing issues?
Neovim version (nvim -v)
NVIM v0.9.5 Build type: Release LuaJIT 2.1.1703358377
Operating system/version
MacOs 14.2.1
Describe the bug
I get a
invalid window id
error:Steps To Reproduce
nvim -u repro.lua
:Trouble quickfix
Open a emtpy trouble window. it can also be diagnostics or whatever, it does not matter:lua require('edgy').close()
Close the Edgy Window:Trouble quickfix
Open trouble againBTW: the same error occurs in several scenarios, this is just one reproduction
Expected Behavior
No Error
Repro
The text was updated successfully, but these errors were encountered: