Hello again after months of silence on the main branch! We have been cooking a very large release behind the scenes. v0.6
includes several refactors and new features. I cannot list all of them here, but the documentation has been updated to reflect
the most recent changes.

Most notably, we have changed names! This project is now called nvf as opposed to the former, generic
"neovim-flake" as its name. nvf stands for several things, none of them officially confirmed as the name. You are welcome to adapt the one you think is best: nvf is not a vim flake, notashelf's vim flake, nix vim flake.

What's new

Thanks to my fellow co-maintainers and lovely contributors, we bring to you v0.6 with many notable changes. Some of them are:

• Most plugins have been converted to a new setupOpts API that generates configuration tables from Nix directly. This means you no
  longer have to wait for us to add missing options - any option with the current naming scheme will be featured in the resulting
  configuration table. Examples of this are included in the documentation.
• The configuration wrapper has been updated to allow for verbatim Lua code wherever you don't want to use Nix to configure your Neovim.
• vim.extraRuntimePaths has been added to append additional directories to your Neovim configuration. This can be used to configure generic Neovim runtime paths, such as spell/, after/ and ftplugin/.
• You can now view view nvf option documentation from the comfort of your terminal. The Home-Manager and the brand new NixOS modules have both received an enableManpages option that will optionally add the generated manual pages to your PATH. Once the option is true, simply run man 5 nvf and you will be able to view all available options from your terminal.
• Treesitter module has received more configuration options, namely for highlight and indent. Please take a look at the documentation for the new available module options.
• Project structure has changed significantly. The modules directory has been broken into multiple files, each with its own purpose. I hope this will make the project tree easier to navigate for those who want to contribute.

For details on how to migrate to setupOpts API in your configurations, please see v0.6 changenotes. @horriblename has kindly decided to include a section to make your migration much easier.

Thanks

For this release, I would like to thank @ksonj, @horriblename and @FrothyMarrow for their contributions.

As always, changes are documented in the changelog. Thanks for your continued support!