Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
FVim crashes when executing with --wsl flag
See original GitHub issueUsing FVim
with NeoVim
I get the following error:
I am running on Windows 10 using Cmder running PowerShell Core 7. I would paste the text, but I can’t seem to copy the text out of that window.
Issue Analytics
- State:
- Created 3 years ago
- Comments:16 (8 by maintainers)
Top Results From Across the Web
Nvim crashes when opening a python file in WSL #20270
No, vim 9.0 Operating system/version Windows 11 (10.0.22621.521) with wsl 0.66.2.0 Here's the result of wsl --version on my end: WSL ...
Read more >Ubuntu crashes on windows: 0x80040326 Wsl error
Open a PowerShell or Command Prompt window in Administrator mode · Run the command wsl.exe --update · Run wsl.exe again to see if...
Read more >Temporary Failure in name resolution on WSL
I found out, that it only fails the DNS lookup when I first connect the VPN before starting WSL-Ubuntu after System-Reboot.
Read more >Release Notes for WSL
Read release notes for the Windows Subsystem for Linux. These release notes include fixed issues and are updated weekly.
Read more >Running WSL vs Running Linux : r/linux
I use Vim all the time in WSL under Ubuntu/Fedora/Gentoo and have never experienced this. "a" and "i" both work as expected. Windows...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
the “unexpected byte message” is actually raw text coming from neovim. I guess it really wants to say something now that it doesn’t follow the protocol 😃
@citizen428 can you try latest head 9697d59 – I’ve patched it so that it will print the raw message in the crash dialog on exit, like, if you do
fvim --help:noprob, I’m glad you figured it out 😉