neovim/runtime/example_init.lua, branch master

docs: api, plugins, ui2

2026-03-23T23:14:55Z

docs: misc

2026-03-20T22:30:09Z

docs: example_init #38372

2026-03-19T17:22:32Z

* docs(example_init): consistently use `:h` * docs(example_init): align PLUGINS section with the overall style Since this entire file is example, all sections use declarative voice, avoiding "For example". Replaces summary list with related help tags. * docs(example_init): adjust mini.completion URI See https://github.com/nvim-mini/mini.nvim/discussions/1970 * docs(example_init): misc grammar fix

docs: api, messages, lsp, trust

2026-03-11T17:00:18Z

gen_vimdoc.lua: In prepare for the upcoming release, comment-out the "Experimental" warning for prerelease features.

fix: misc typos #37471

2026-01-27T14:18:02Z

refactor(lua): use vim.system #34707

2025-07-24T03:03:30Z

feat(pack): add built-in plugin manager `vim.pack`

2025-07-04T12:56:28Z

Problem: No built-in plugin manager Solution: Add built-in plugin manager Co-authored-by: Lewis Russell

docs: provide example_init.lua #33524

2025-04-27T15:11:02Z

Problem: There are some "boilerplate" steps for new users. Although we are constantly improving defaults and lifting patterns into core, users eventually want to know how to start their own config, add plugins, etc. Solution: Add `runtime/example_init.lua` and refer to it from docs.