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.
Add system specific vscode-neovim.neovimPath settings entries
See original GitHub issueI use VSCode ‘Settings Sync’ extension and I have a personal laptop with Linux and a work laptop with Windows. I use vscode-neovim on both.
Lately I uploaded my settings to Settings Sync from the Linux laptop with the vscode-neovim.neovimPath set to /usr/bin/nvim. Then I moved to my Windows work laptop - my neovim path was C:\tools\nvim\bin\nvim.exe and vscode-neovim was working ok. But then I downloaded the fresh settings and the neovimPath on Windows changed to the Linux one - /usr/bin/nvim and vscode-neovim stopped working.
Perhaps it would be cool to split the neovimPath into three separate settings:
neovimPath.windows,
neovimPath.linux,
neovimPath.osx,
VSCode already uses the convention I proposed with their terminal.external.[linux/windows/osx]Exec setting
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (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
for immediate workaround, you can use settings sync pragma : https://github.com/shanalikhan/code-settings-sync/wiki/Sync-Pragmas#per-os
@genesy Nope, I didn’t try it. I switched to a Windows only setup recently so it’s not so annoying to me. I’m working on the PR now though cause it’s laying around collecting dust.
The VS Code team is supposedly working on a built-in settings sync extensions and I wonder how they’re gonna solve this of “different setting value on different system”.