Investigate Replay/Environment Undo Functionality for reloading a plugin

[miversen33]

Per #15 , research how difficult it is to do something like this. This issue will be updated with scope once I get to it.

[miversen33]

I've got a current theory on this, revolving around diffing vim.g, vim.w, vim.b, vim.t, and vim.v before and after a plugin is imported, and then saving the "revert" state with the plugins import. I haven't gotten around to testing this out because its kinda disgusting and I have been working on other things. But thats my current running theory on this

[ciesling]

@miversen33

Hello, this year I got rid of Windows completely. I am glad I ran into neovim pretty early on cus I thought it was neat to just use my 60 keyboard only to code. Then I found neovide and was blown away when I realized just how crippling my old windows os really was for the first time.

Do you know I can keep being a neovide chad while I edit my nvim dotfiles?

[miversen33]

Erm, what does this have to do with this issue?

[ciesling]

Sorry I seem to be misunderstanding. It was about not having to close and reopen neovide everytime i make a save in my nvim dot files to get it to update.

[miversen33]

Gotcha ok, I am following now.

This issue is a feature request for research into being able to properly "unload" a plugin so you can hot reload it "correctly". How import.nvim currently handles this it it just "nils" out the global table representation of a plugin and then re requires the plugin. It's not great but it "works" mostly.

All that said, as called out both in the readme and #21 import.nvim is deprecated. I am no longer updating this plugin. So if you are having issues with something you want, you might consider forking or looking into something like lazy.nvim which supports plugin reloading (I have no idea if folke solved this problem in a better way than I did but at the very least lazy has similar capability in terms of reloading).