This setup 'just' works for me. I have mapped certain functionality, for e.g. toggling the file explorer to a nvim keymap (the extension also enables h, j, k, l, y, p, etc. commands in the explorer) but I use the cmd/ctrl + P keymap for searching files in the current project, so it feels incomplete sometimes. When I am editing a set of files it works great, but as soon as I use a VS code feature, for e.g. project search, the experience is okay and may require a mouse, which is not surprising but I hope the integration gets even better.
I am sure that with more configuration, the experience could be made more NeoVim like but I don't know whether I should spend time doing this or invest my time learning/adapting to a terminal based flow for the few tasks for which I am used to the VS Code GUI (browsing Git history, diffs for pull requests, git stash operations, debugging).
I started with a base config (kickstart.nvim) after trying out LazyVim sometime back, but kept going back to VS Code for some of the tasks. So what I have now is not significantly better but I like it.
I am sure that with more configuration, the experience could be made more NeoVim like but I don't know whether I should spend time doing this or invest my time learning/adapting to a terminal based flow for the few tasks for which I am used to the VS Code GUI (browsing Git history, diffs for pull requests, git stash operations, debugging).
I started with a base config (kickstart.nvim) after trying out LazyVim sometime back, but kept going back to VS Code for some of the tasks. So what I have now is not significantly better but I like it.