Repository navigation
refactor(nvim): drop lazyvim.plugins.linting import - #47
Merged
Merged
Conversation
nvim-lint was loading on every LazyFile but LazyVim's default only configures a linter for `fish`, which none of this config's languages use -- so it registered a BufWritePost/InsertLeave autocmd and then never ran a linter. Diagnostics already come from the LSP servers and none-ls (golangci_lint, deadnix). The per-language nvim-lint setups live in lazyvim.plugins.extras.lang.* modules this config doesn't import, so the `linting` import was its only spec: dropping it removes nvim-lint cleanly. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This was referenced Aug 15, 2026
potsrevennil
marked this pull request as ready for review
October 20, 2026 06:54
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
nvim-lintwas loading on everyLazyFileevent, but LazyVim's defaultlinting.luaonly configures a linter forfish— a filetype none of this config's languages (lua, sh, nix, python, go, c/cpp, typst, toml, rust, haskell, yaml) use. So it registered aBufWritePost/InsertLeaveautocmd and then never actually ran a linter.Diagnostics are already covered by the LSP servers (
lua/plugins/lsp.lua) and none-ls (golangci_lint,deadnix,statixinlua/plugins/none-ls.lua). The per-language nvim-lint configs live inlazyvim.plugins.extras.lang.*modules this config doesn't import, so thelintingimport was nvim-lint's only spec — dropping it removes the plugin outright rather than needing anenabled = falsestub.nix build+ smoke test — clean startup, no spec errors; LSP + none-ls diagnostics unaffected.