Open 99linesofcode opened 4 months ago
Seems like this is a configuration issue potentially caused by an issue with VSCode installing/uninstalling plugins that already landed in Insiders and will be shipped shortly (https://github.com/microsoft/vscode/issues/207813).
Nope, still an issue. For VSCode it is probably better not to configure LazyVim for the time being and rely solely on Neovim for navigation.
As I find myself working with neovim more and more I've adopted Lazyvim and tried to make it work together with VSCode. Unfortunately, as it stands now, things are still wonky. Neovim crashes, I get inline linting errors that don't make any sense, etc.
I've since removed
~/.config/nvim
while I think of a more elegant solution.