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 startup script has trouble with environment variable values with spaces
See original GitHub issueI was not able to start FVim at all, it claimed nvim was not in the path. I think I tracked this down to the fvim-osx-launcher file in /Applications/FVim.app/Contents/MacOS
The bash snippet in there can’t deal with spaces in environment variable values, in particular if you have VScode installed, you probably got /Applications/Visual Studio Code.app/Contents/Resources/app/bin added to your $PATH. But when the launcher script is run your $PATH will get truncated after /Applications/Visual. If nvim is in a directory after that, FVim will not find it.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:6 (6 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
Bash was doing string splitting in the
forstatement based on the default IFS (Internal Field Separator) value, which is usually space, tab, and newline. Resetting it to just a newline helps. This is non-obvious behavior, but has been around in Bash and other Unix-derived shells for a long time. I always have to look it up 😁 .Wow. Thank you for explaining! This is truly non obvious that I read twice and didn’t realize!