Allow setting stdpath's to avoid collision with terminal neovim

Hello!

It seems a lot of neovim plugins expect the UI to be a dedicated UI for neovim itself, and not an integration into another editor platform. Because of this, there seems to be some collisions of functionality with things such as session management, for example.

I’ve attempted doing a bit of a hacky work around in my init.lua that I found from this post. It’s a fine idea, but doesn’t seem to be working completely in practice? When I echo stdpath("data") it returns the original path, however, doing lua print(vim.fn.stdpath("data")) works as desired.

I can see this is not functioning on the level I need it to as I still get messages from plugins like vim-go, thus it appears it’s still using ~/.local/share/nvim for the data directory.

Is this within the scope of this plugin? I’m not sure how else to go about doing this, but I’d like to maintain separation between the two instances.

Thanks for the plugin!

[justinmk]

I created this issue mainly to see if we can separate the two so I don’t have to really screw with my nvim config

To solve this issue you need to screw with some config, either in vscode or Nvim. You can set ‘packpath’ and ‘runtimepath’ in a exists('g:vscode') condition, and that’s that. There is no reason for vscode-neovim to add another mechanism to do this.

[theol0403]

My dotfiles might help. You should generally think about which vim plugins to use with vscode.

https://github.com/theol0403/dotfiles/blob/master/.config/nvim/vimrc/moon/common.moon https://github.com/theol0403/dotfiles/blob/master/.config/nvim/vimrc/moon/plugins.moon