infinite file opening loop
See original GitHub issueHere is my System info:
Operating System: Garuda Linux
KDE Plasma Version: 5.21.5
KDE Frameworks Version: 5.82.0
Qt Version: 5.15.2
Kernel Version: 5.12.1-zen2-1-zen
OS Type: 64-bit
Graphics Platform: X11
Processors: 8 × 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz
Memory: 15.4 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics
This happened first to me when I tried ctrl+shift+p
to open up the settings.json. I wasn’t able to reproduce this in mac os and I think it just started happening recently. Anyway, the jist of it is that it just continuously opens new files. I get two errors in the console:
ERR nvim_win_close: Invalid window id: 1051: Error: Error making request to nvim_win_close
at o.request (/home/joshua/.vscode-oss/extensions/asvetliakov.vscode-neovim-0.0.78/dist/extension.js:1:15853)
at Timeout._onTimeout (/home/joshua/.vscode-oss/extensions/asvetliakov.vscode-neovim-0.0.78/dist/extension.js:3:101219)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7)
and
ERR nvim_win_get_cursor: Invalid window id: 1060: Error: Error making request to nvim_win_get_cursor
at o.request (/home/joshua/.vscode-oss/extensions/asvetliakov.vscode-neovim-0.0.78/dist/extension.js:1:15853)
at he.<anonymous> (/home/joshua/.vscode-oss/extensions/asvetliakov.vscode-neovim-0.0.78/dist/extension.js:3:100678)
at Generator.next (<anonymous>)
at /home/joshua/.vscode-oss/extensions/asvetliakov.vscode-neovim-0.0.78/dist/extension.js:3:88882
at new Promise (<anonymous>)
at ce (/home/joshua/.vscode-oss/extensions/asvetliakov.vscode-neovim-0.0.78/dist/extension.js:3:88627)
at Timeout._onTimeout (/home/joshua/.vscode-oss/extensions/asvetliakov.vscode-neovim-0.0.78/dist/extension.js:3:100617)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7)
But mostly the first window close error. I don’t know why this causes continuous new windows to open up, but when I disable the extension it stops it.
You can see what it looks like here:
As a side note, I thought maybe I could fix this myself and put in a pull request, but I don’t have a whole lot of time and I was having trouble getting into debugging the extension. I couldn’t really get it activated. If there’s a slack channel that can help me get up and running I can try to fix it myself.
Let me know! Thanks!
Issue Analytics
- State:
- Created 2 years ago
- Reactions:66
- Comments:57 (16 by maintainers)
This command writes to a file named
extensions.js
, but the correct file isextension.js
, which means the following is the correct command:How did the original comment get 6 positive reactions (at the time of writing) while having a typo, and thus not working, is beyond me. Nice solution overall though.
Released 0.0.79 with the fix. Thanks @seandewar !