> I think the value in healthcheck is not running it for vim, but
> providing a standard API that **plugins** can rely on and users can
> expect. ale has three `:ALEInfo` commands, vim-lsp has `:LspStatus`,
> omnisharp has `:OmniSharpStatus`. Some of these commands only print
> results, some create a buffer, some write to a file.
>
> As a user, if I can run `:CheckHealth` to see issues with my plugins
> (e.g., binaries they depend on are missing or failing to run, dump
> configuration info, etc), then it's easier for me to know how to start
> debugging my problems.
>
> As a plugin author, if vim has a built-in framework for triggering and
> displaying diagnostic information then I'm more likely to implement
> those diagnostics. The alternative of writing my own mini version of
> checkhealth is usually more work than I want to bother and getting
> users to `:redir @+ | call myplugin#dump_state() | :redir END` is
> unreliable and undiscoverable.
I agree, it would be nice to have an independent way to do this, no
matter what plugin framework you use. Big question is how plugins would
hook into this. Where is the documentation for this CheckHealth plugin?
Demo is just advertising, I want to see the technical side of it.
Perhaps just a global dictionary where each plugin can add an entry
under its name? There must be an API for reporting back the results.
--
ALL: A witch! A witch!
WITCH: It's a fair cop.
ALL: Burn her! Burn her! Let's make her into a ladder.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// \\\
\\\ sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/20221029220504.2656E1C0739%40moolenaar.net.
