When I initially created the plugin one of the most important things for me was that it didn't negatively affect the speed of neovim at startup. That's why I thought that the best option to achieve this was to leave it up to vim to load the configuration of the theme saved by the user (persistence). To do this, you had to follow a series of steps to set up a special file that would be loaded automatically at startup.
Problem
Although on paper this idea was great because of the above and other things, the reality is that this configuration was confusing for many users as it is not a common thing in the plugins ecosystem. (instructions)
Posible solution
Seeing the need to do something about it I have been testing to compare the difference between loading the state natively as before, or loading it from themery. The result is that there is practically no difference and no flickering to the user as it was initially.
✅ Themery will work out of the box.
✅ It will be possible to develop more advanced features
❌ If you uninstall themery, you will have to configure the colorscheme by hand as it will not load automatically.
So...
That's why themery will change the current persistence system, for an automatic one more transparent to the user, saving the necessary information in a default directory within the neovim data.
Origin
When I initially created the plugin one of the most important things for me was that it didn't negatively affect the speed of neovim at startup. That's why I thought that the best option to achieve this was to leave it up to vim to load the configuration of the theme saved by the user (persistence). To do this, you had to follow a series of steps to set up a special file that would be loaded automatically at startup.
Problem
Although on paper this idea was great because of the above and other things, the reality is that this configuration was confusing for many users as it is not a common thing in the plugins ecosystem. (instructions)
Posible solution
Seeing the need to do something about it I have been testing to compare the difference between loading the state natively as before, or loading it from themery. The result is that there is practically no difference and no flickering to the user as it was initially.
So...
That's why themery will change the current persistence system, for an automatic one more transparent to the user, saving the necessary information in a default directory within the neovim data.
What do you think?