neovide_fullscreen errors with "E475: Channel does not exists"

[jmlucjav]

Describe the bug
Setting g:neovide_fullscreen fails with an error:

To Reproduce
Steps to reproduce the behavior:

1. open command line
2. run

let g:neovide_fullscreen=v:true

using 1 instead of v:true is the same

Expected behavior
Full screen

Desktop (please complete the following information):

• OS: Win10 21H2
• Neovide 0.10.1
• Neovim 0.8 from a few days ago, running on WSL ubuntu

neovide_rCURRENT.log
neovide_r2022-08-24_19-57-59.log

thanks

[MultisampledNight]

Thanks for reporting! I can't reproduce the issue on Arch Linux/Sway though, so I guess this is a Windows or more to say WSL specific issue.

[groner]

I've run into an issue like this when connecting to a remote neovim. I'm not using Windows, but I think the fix may be the same.

The NeovideNotifycursor_animation_lengthChanged() glue function contains the channel id 1, but g:neovide_channel_id is now 3. I'm not sure why they seem to be out of sync from the get go.

In either case, updating the glue functions to use g:neovide_channel_id would probably fix this (assuming there isn't some other Windows issue at play).

[camAtGitHub]

Kind of inline with this... running neovim in WSL2 environment via command:
nvim --headless --listen 127.0.0.1:41234 and using Neovide via
C:\Users\cam\scoop\apps\neovide\0.10.1\neovide.exe --remote-tcp=127.0.0.1:41234 - It is impossible to detect Neovide exists('g:neovide') (as it may not have attached yet...).
Even creating a timer function and attaching before the timer triggers then I hit these 'Channel doesn't exist' errors.

I can confirm exists('g:neovide') = 1. Running echo g:neovide_channel_id outputs 6 as an example.

[fredizzimo]

This was fixed in the 0.12.0 release by

• set neovide_channel_id always #2070