vscode-neovim: Stuck at Syncing Layout: Syncing Visible Editors
Type: Bug
Steps to reproduce:
- Write some code and go to normal mode.
- Open GitHub Copilot
- Generate some code
- Click on the code generated by it.
- Focus on your own code and try to go back to insert mode.
Expected: I should be able to type and change between insert and normal modes.
Actual: Pressing i ( for insert mode) does not do anything. There is a warning at the bottom-right side:
Additional info: Only thing that can be done is disabling the extension and enabling it again.
Extension version: 1.18.18 VS Code version: Code 1.97.2 (Universal) (e54c774e0add60467559eb0d1e229c6452cf8447, 2025-02-12T23:20:35.343Z) OS version: Darwin arm64 24.3.0 Modes:
System Info
| Item | Value |
|---|---|
| CPUs | Apple M3 Pro (11 x 2400) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off |
| Load (avg) | 17, 17, 16 |
| Memory (System) | 18.00GB (0.53GB free) |
| Process Argv | . --crash-reporter-id d916d4e5-5c43-4ce6-9032-3a3bc964cc74 |
| Screen Reader | no |
| VM | 0% |
A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
pythonvspyt551:31249599
vscod805cf:30301675
binariesv615:30325510
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dwnewjupytercf:31046870
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc2:31192216
iacca1:31171482
5fd0e150:31155592
dwcopilot:31170013
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
hdaa2157:31222309
copilot_t_ci:31222730
jda6j935:31233686
copilothoveron:31248524
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 65
- Comments: 18
Commits related to this issue
- fix: do not open in copilot to fix #2407 — committed to fecet/vscode-neovim by fecet 2 years ago
- fix: do not open in copilot to fix #2407 (#2467) — committed to vscode-neovim/vscode-neovim by fecet 2 years ago
- Revert "fix: do not open in copilot to fix #2407 (#2467)" This reverts commit da01d6b202f42b300e247339863eee5395ad038e. — committed to vscode-neovim/vscode-neovim by xiyaowong 2 years ago
- Revert "fix: do not open in copilot to fix #2407" (#2469) Revert "fix: do not open in copilot to fix #2407 (#2467)" This reverts commit da01d6b202f42b300e247339863eee5395ad038e. — committed to xiyaowong/vscode-neovim by xiyaowong 2 years ago
🚨Confirm by building from source. This issue comes from https://github.com/neovim/neovim/commit/dc37c1550bed46fffbb677d343cdc5bc94056219 Same issue: https://github.com/neovim/neovim/issues/31316
The cause of the issue has been clearly identified. Please refrain from sending meaningless replies. Thank you!
Fixed by https://github.com/neovim/neovim/pull/34412 in Nvim 0.12 (unreleased), and will be included in Nvim 0.11.3 maintenance release.
Before commenting or reporting this issue again, confirm that you are running the latest Nvim 0.12 or 0.11.3 nightly (not 0.11.2 or earlier), or if you built from source mention the exact commit sha.
Here are two temporary solutions—choose one:
0.9.5and ignore the startup error message from vscode-neovim (this does not affect normal use). This approach may cause some minor bugs e.g. #2099, but it will not make vscode-neovim completely unusable.Even though the issue is most likely caused by nvim itself, this does not mean that it will be fixed by a neovim developer (e.g. because of other priorities, complexity, etc.) so at least this issue should be used for dicusssions or comments on other workarounds. Maybe there is still the option to workaround-fix it in the vscode-neovim extension itself as it was tried in #2368.
I tested it on Windows, and I can no longer reproduce the issue.
Note: For anyone who wants to test this issue, you need to use vscode-neovim version 1.18.20 or below.
About this output panel there is an option in newest vscode to prevent that from happening: https://github.com/vscode-neovim/vscode-neovim/issues/2099#issuecomment-2657736422
In addition to switching to neovim 0.9.5, I recommend that you switch to vscode-neovim plugin version 1.18.9. This prevents vscode output panel from opening on certain actions (e.g. pressing something as common
ufor undo).1.18.10 introduced the minimum required version of neovim 0.10.0.
It became less frequent but it still happens sadly.
Has this issue improved to some extent in the latest version?
Would be very helpful if someone can try Neovim with this patch: https://github.com/neovim/neovim/pull/34412 and confirm if it fixes this issue.
Thanks for the info @KostkaBrukowa!