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.
Launching in WSL
See original GitHub issueOk, I know what’s the problem. The command for launching in nvim is bash-specific and therefore it fails to create a process. Or, more precisely, the process dies almost immediately after being created, because it doesn’t actually spawn nvim.
This line does a $(wslpath 'c:\blabla'). But that code doesn’t work in fish, which is my default shell. So we should probably either start nvim inside of a bash, or somehow make the path resolution shell-agnostic.
Sorry to cause trouble.
_Originally posted by @DanielFabian in https://github.com/asvetliakov/vscode-neovim/issues/145#issuecomment-573396921_
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Ya, that sounds more robust than writing an actual shell script.
Seems the PR doesn’t work at all and breaks bash shells as well. I don’t have Win/WSL installed right now, so PRs are welcome here