MiniMax updates: vim.pack on Neovim>=0.12, config for Neovim=0.10
nvim-0.12 for Neovim>=0.12 (uses vim.pack) and nvim-0.10 for Neovim=0.10
Hello, Neovim users!
MiniMax (a Neovim config generator based on ‘mini.nvim’) got two new reference versions:
nvim-0.12for Neovim=0.12. Although this Neovim version is currently under development, its release is expected soon-ish. The main theme of this config is that it will switch from using ‘mini.deps’ as a plugin manager tovim.pack.nvim-0.10for Neovim=0.10. Although this is not the latest stable release, it is not yet very old so might be still used by a few people. It is fairly similar tonvim-0.11with the main differences in how ‘nvim-treesitter’ and ‘nvim-lspconfig’ plugins are set up.
For new MiniMax users it means that setting up with nvim executable for version 0.12 (you can check your version with nvim --version) will generate a config that uses more up-to-date Neovim features. And for nvim version 0.10 it is now possible to generate a MiniMax config at all.
For (hopefully) happy users of MiniMax, it means a guided opportunity to practise updating their config after Neovim 0.12 becomes a stable release. MiniMax doesn’t come with full proof updating mechanism (by design, the generated config is fully owned by the user). However, I am excited to share that there are now dedicated pages that show differences when moving from one config to the next:
These pages show only the parts that change which should make it easier to reference when manually updating.
The release of nvim-0.12 is a very exciting event for MINI since it is a first step towards adapting vim.pack as the recommended plugin manager. The ‘mini.deps’ module is planned to be retired (i.e. will be present but without updates) soon-ish after Neovim=0.12 is released. There will be a separate blog post about it.
Give the new configs a try and reach out with the feedback in dedicated issue: for nvim-0.12 and for nvim-0.10.
Thank you for reading!