Current nixpkgs evaluation of the locked vimconfig output emits both warning classes twice in downstream system evaluation:
evaluation warning: nvim-treesitter-legacy is deprecated, please migrate to the new version. This will become an error in 26.11
evaluation warning: nixfmt-rfc-style is now the same as pkgs.nixfmt which should be used instead.
The nixfmt-rfc-style fix is straightforward: use nixfmt in extraBinPath.
The tree-sitter warning needs a real compatibility decision before 26.11. The configuration still uses the old require("nvim-treesitter.configs").setup(...) API and Markid calls nvim-treesitter.define_modules, while the new nvim-treesitter package is an incompatible rewrite. The warning is reached through the configured plugin graph, including nixpkgs Markid metadata depending on nvim-treesitter-legacy; simply changing that dependency to the new package can silence evaluation while breaking runtime behavior.
A safe fix should either:
- migrate the Lua configuration and dependent plugins such as Markid to the rewritten API; or
- package nvim-treesitter’s upstream
master compatibility branch directly under a non-deprecated local name until that migration is complete.
Please preserve the existing native Zen 3 and Apple M1 policy while changing the package graph. This was found while auditing downstream jrestivo/system_config#26; that PR intentionally keeps the current upstream input unchanged rather than suppressing alias warnings or redirecting through another fork.
Current nixpkgs evaluation of the locked vimconfig output emits both warning classes twice in downstream system evaluation:
The
nixfmt-rfc-stylefix is straightforward: usenixfmtinextraBinPath.The tree-sitter warning needs a real compatibility decision before 26.11. The configuration still uses the old
require("nvim-treesitter.configs").setup(...)API and Markid callsnvim-treesitter.define_modules, while the newnvim-treesitterpackage is an incompatible rewrite. The warning is reached through the configured plugin graph, including nixpkgs Markid metadata depending onnvim-treesitter-legacy; simply changing that dependency to the new package can silence evaluation while breaking runtime behavior.A safe fix should either:
mastercompatibility branch directly under a non-deprecated local name until that migration is complete.Please preserve the existing native Zen 3 and Apple M1 policy while changing the package graph. This was found while auditing downstream
jrestivo/system_config#26; that PR intentionally keeps the current upstream input unchanged rather than suppressing alias warnings or redirecting through another fork.