-
Notifications
You must be signed in to change notification settings - Fork 70
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
Sometimes prints panic message on startup #209
Comments
Which nvim version are you using? And by any chance are you using a window manager that automatically modifies the window size (tiling wm)? Looks like gnvim is trying to report a updated window size to neovim before the |
neovim versions 0.9.0 and also with 0.9.1-pre (built from release-0.9 branch 3 days ago). I'm using KDE (including KDE's kwin window manager) under Wayland. I suppose it might be modifying the window size (to replicate the dimensions that gnvim had on its last invocation), although I don't see this occurring. If it would be helpful I can try and get some debug info out of kwin? |
Window manager modifying the window size was just a hunch. It doesn't (or shouldn't) matter if that happens or not - its still a bug in gnvim. I haven't encountered this issue earlier, but it might be a race condition between this code and everything else that is communicating with neovim. |
I flattened the rpc client stuff to make its usage a bit more straightforward, and now fixing this should be just a matter of implementing either:
I still haven't encountered this issue myself, hence my personal priority for fixing this isn't the highest. I'm happy to accept any PRs. |
Firstly, thanks very much for writing gnvim... I thought I'd give it a try, so after compilation and installation, I tried starting it from the command line and got a panic.
I compiled and I'm running on on Debian 12 amd64, under Wayland (I haven't tried other environments), and the panic occurs on approx 50% of invocations, the following is printed on startup:
The text was updated successfully, but these errors were encountered: