E5018: Invalid window id
jonahfang opened this issue · comments
The error detail message like this:
E5108: Error executing lua: ...m/data/confignext/lazy/FTerm.nvim/lua/FTerm/terminal.lua:193: WinEnter Autocommands for "*": Vim(append):Error executing lua callback: ...vim/data/confi
gnext/lazy/detour.nvim/lua/detour/util.lua:40: Invalid window id: 1456
stack traceback:
[C]: in function 'nvim_win_get_position'
...vim/data/confignext/lazy/detour.nvim/lua/detour/util.lua:40: in function 'get_text_area_dimensions'
...vim/data/confignext/lazy/detour.nvim/lua/detour/util.lua:70: in function <...vim/data/confignext/lazy/detour.nvim/lua/detour/util.lua:69>
vim/shared.lua: in function 'find_covered_bases'
...vim/data/confignext/lazy/detour.nvim/lua/detour/util.lua:80: in function 'find_top_popup'
...nfignext/lazy/detour.nvim/lua/detour/plugin_autocmds.lua:8: in function <...nfignext/lazy/detour.nvim/lua/detour/plugin_autocmds.lua:7>
[C]: in function 'nvim_win_close'
...m/data/confignext/lazy/FTerm.nvim/lua/FTerm/terminal.lua:193: in function 'close'
...m/data/confignext/lazy/FTerm.nvim/lua/FTerm/terminal.lua:218: in function 'toggle'
.../nvim/data/confignext/lazy/FTerm.nvim/lua/FTerm/init.lua:37: in function 'toggle'
.../fzx/work/nvim/confignext/lua/plugins/terminal/fterm.lua:107: in function <.../fzx/work/nvim/confignext/lua/plugins/terminal/fterm.lua:104>
stack traceback:
[C]: in function 'nvim_win_close'
...m/data/confignext/lazy/FTerm.nvim/lua/FTerm/terminal.lua:193: in function 'close'
...m/data/confignext/lazy/FTerm.nvim/lua/FTerm/terminal.lua:218: in function 'toggle'
.../nvim/data/confignext/lazy/FTerm.nvim/lua/FTerm/init.lua:37: in function 'toggle'
I think this may be a temporary bug that got in the dev branch (I infer you're on the dev branch because I see the plugin_autocmds.lua
file in the trace and that file has not made it on the main branch yet). I think the problem may fix itself if you update detour the the most recent version of the dev
branch and restart neovim. Please give it a try and let me know how it goes. Thanks for being on the dev
branch and reporting this issue :)
I have switched to the dev branch.
Did you update to the most recent version of the dev
branch? Did it fix your issue?
I start to use the lastest dev branch just for 1 hour and everything is ok now.