fredizzimo
fredizzimo
As a Linux and Windows user, I have hard time seeing this as high priority or something that we should even do at all. For multiple instances the operating system/desktop...
Ok, I checked what needs to be done, the winit support, was just the last missing piece for Alacritty, and enabled by winit here: * https://github.com/rust-windowing/winit/pull/2956 But the real problem...
You need to specify a font name before `:h11`, you can check available fonts with `set guifont=*`
To change the font size you can you the `neovide_scale_factor` option. There are some examples in this discussion https://github.com/neovide/neovide/discussions/2301#discussioncomment-8223203
I don't think that patch is relevant since it applies to gvim only. I'm not sure if we have enough information here to send the correct code to Neovim. The...
Neovim uses the terminal for the keyboard handling, and neovim-qt uses qt. We use winit, and this appears to be a bug in that library, for not providing us the...
Thanks the issue looks good, I can help filling in more details if needed when we get a response from the Winit team.
This should be fixed in Neovim 0.10, and since Neovide 13.1 requires that, I'm closing this.
The reason why it's not maximized on creation, is because it creates a very noticeable white flash on Windows. There's a bug in winit that shows the window for one...
Since https://github.com/neovide/neovide/pull/2562 is now merged, I think we can close this one.