neovim/runtime/lua/vim/health.lua, branch masterVim-fork focused on extensibility and usabilityhttp://git.waynecole.info/neovim/atom?h=master2026-04-24T15:57:35Zfeat(api): nvim_echo(percent=nil) means "unknown" progress #390292026-04-24T15:57:35ZPeter Cardenas16930781+PeterCardenas@users.noreply.github.com2026-04-24T15:57:35Zurn:sha1:27191e0f4f4f9086180a8fbe3e52c1c280a70b09
Problem:
No way to signal "unknown" or "indeterminate" progress percentage.
Solution:
Treat percent=nil as "indeterminate" percent.refactor(excmd): migrate ex_checkhealth to Lua2026-04-20T00:12:05ZJustin M. Keyesjustinkz@gmail.com2026-04-18T14:40:25Zurn:sha1:fe7218528d70b6df006c356761a92620f6a989c7fix(progress): require "source" for progress-message #385142026-03-28T13:22:22ZShadmanshadmansaleh3@gmail.com2026-03-28T13:22:22Zurn:sha1:7bf83cc2a651c586267fbad2e3e57d1a65857287
Problem:
- Progress-events are filtered by "source". But "source" is not required by nvim_echo.
- Without "++nested" (force=false), nvim_echo in an event-handler does not trigger Progress events.
- vim.health does not declare a "source".
Solution:
- Make source mandatory for progress-messages
- Enable ++nested (force=true) by default when firing Progress event.
- Set "source" in vim.health module.feat(lua): replace `buffer` with `buf` in vim.keymap.set/del #383602026-03-21T16:00:06Zskewb1kskewb1kunix@gmail.com2026-03-21T16:00:06Zurn:sha1:4d3a67cd620152d11ab9b5f5bdd973f84cc2d44b
The `buffer` option remains functional but is now undocumented.
Providing both will raise an error. Since providing `buf` was disallowed
before, there is no code that will break due to using `buffer` alongside
`buf`.feat(stdlib): vim.fs.ext() returns file extension #369972026-03-20T09:08:00ZYochem van Rosmalengit@yochem.nl2026-03-20T09:08:00Zurn:sha1:72a63346d866c320bbf77c90db0574952bd1c076
Problem:
Checking the extension of a file is done often, e.g. in Nvim's codebase
for differentiating Lua and Vimscript files in the runtime. The current
way to do this in Lua is (1) a Lua pattern match, which has pitfalls
such as not considering filenames starting with a dot, or (2)
fnamemodify() which is both hard to discover and hard to use / read if
not very familiar with the possible modifiers.
vim.fs.ext() returns the file extension including the leading dot of
the extension. Similar to the "file extension" implementation of many
other stdlibs (including fnamemodify(file, ":e")), a leading dot
doesn't indicate the start of the extension. E.g.: the .git folder in a
repository doesn't have the extension .git, but it simply has no
extension, similar to a folder named git or any other filename without
dot(s).refactor: integer functions, optimize asserts #341122026-03-12T15:04:05ZLewis Russelllewis6991@gmail.com2026-03-12T15:04:05Zurn:sha1:ce1154048b11cdc402d0e5da352a3adca19afb56
refactor(lua): add integer coercion helpers
Add vim._tointeger() and vim._ensure_integer(), including optional base
support, and switch integer-only tonumber()/assert call sites in the Lua
runtime to use them.
This also cleans up related integer parsing in LSP, health, loader, URI,
tohtml, and Treesitter code.
supported by AIfix(health): add back `vim.cmd.redraw()` call (#37576)2026-01-27T07:54:27ZOlivia Kinneargit@superatomic.dev2026-01-27T07:54:27Zurn:sha1:c28113dd9d09b661061d25c147e39efadc6e700b
Was erroneously removed by #37462 during rebase.fix(ui): only internal messages are unsafe #374622026-01-26T23:18:51Zluukvbaalluukvbaal@gmail.com2026-01-26T23:18:51Zurn:sha1:d30d91f3a49e19e61473b74e42adf68e9215220d
Problem: Fast context for msg_show event inhibits vim.ui_attach from
displaying a stream of messages from a single command.
Solution: Remove fast context from msg_show events emitted as a result
of explicit API/command calls. The fast context was originally
introduced to prevent issues with internal messages.fix(health): redraw after emitting progress message #375672026-01-26T21:15:47ZOlivia Kinneargit@superatomic.dev2026-01-26T21:15:47Zurn:sha1:e9d03b92b67ca8c798c95efe9b6abc7dae0666b3
Problem:
`vim.cmd.redraw()` is not called after displaying a progress message, so
vim will display progress for the previous health check, not the current
one.
Solution:
Call `vim.cmd.redraw()` so that the correct progress message is displayed.fix(health): emit Progress message #371232026-01-09T22:00:09ZYochem van Rosmalengit@yochem.nl2026-01-09T22:00:09Zurn:sha1:f19653e3706df41190fe4fb80779f5ad37795159
Problem:
The `"Running healthchecks..."` message doesn't inform the user much and
is a hack from before we got a way to emit actual progress messages.
Solution:
Use `nvim_echo` to emit progress messages showing the name of the report
that is currently running.