fredizzimo

Results 1393 comments of fredizzimo

@liamwh, can you run with the latest master version, it should show more info, it should show both the `stdout` and `stderr` here: https://github.com/neovide/neovide/blob/91344c2104658b9a1a4373a9fcb9a9b71081b902/src/bridge/command.rs#L95-L100

I think we should just automatically define these two environment variables when launching Neovim, since wsl.exe does not seem to set any terminal size when running as a hidden window...

I will check if we can make `COLUMNS` and `LINES` be defined automatically when launching WSL from neovide. That should fix the issue. This at the top of `.zshenv` or...

The bug was reported to Microsoft in November, but I don't have high hopes for a fix soon. * https://github.com/microsoft/WSL/issues/10701 So, I guess the best option left is to ignore...

@DZappala, thank you. You should have permissions to make a PR, everyone does. But you need to do it from your own fork. * https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork But one thing, I think...

This was fixed by: * https://github.com/neovide/neovide/pull/2374

I have a potential fix for this here: * https://github.com/neovide/neovide/pull/2562 It would be good if someone could test it.

Ok, I will re-open this. The list bugs that PR fixed was more of a wishlist than scientific proof, based on the winit documentation: > Winit has an OS requirement...

I actually think we should remove the `--fork/--no-fork` completely and never fork, or at least make `--no-fork` the default. Almost no GUI applications fork when launched from a terminal on...

@9mm, it's not that simple, the CI does this https://github.com/neovide/neovide/blob/ce0174a17674b1984c411e9f81b752d81b1b83d4/.github/workflows/build.yml#L145-L151 and https://github.com/neovide/neovide/blob/ce0174a17674b1984c411e9f81b752d81b1b83d4/.github/workflows/build.yml#L166-L181