summaryrefslogtreecommitdiffstatshomepage
path: root/runtime/plugin/editorconfig.lua
AgeCommit message (Collapse)AuthorFiles
2026-03-12docs: use "ev" convention in event-handlersJustin M. Keyes1
Problem: In autocmd examples, using "args" as the event-object name is vague and may be confused with a user-command. Solution: Use "ev" as the conventional event-object name.
2025-01-14refactor: use nvim.foo.bar format for autocommand groupsMaria José Solano1
2023-04-07feat(lua): allow vim.F.if_nil to take multiple arguments (#22903)Gregory Anders1
The first argument which is non-nil is returned. This is useful when using nested default values (e.g. in the EditorConfig plugin). Before: local enable = vim.F.if_nil(vim.b.editorconfig, vim.F.if_nil(vim.g.editorconfig, true)) After: local enable = vim.F.if_nil(vim.b.editorconfig, vim.g.editorconfig, true)
2023-01-07refactor(editorconfig)!: change editorconfig_enable to editorconfigGregory Anders1
2023-01-07feat(editorconfig): allow editorconfig to be toggled dynamicallyGregory Anders1
Rather than only check `editorconfig_enable` when the plugin is loaded, check it each time the autocommand fires, so that users may enable or disable it dynamically. Also check for a buffer local version of the variable, so that editorconfig can be enabled or disabled per-buffer.
2023-01-03feat(editorconfig): add builtin EditorConfig supportGregory Anders1