Feature: Please provide a `LintInfo` command

[cryptomilk]

Please provide a LintInfo command similar to ConformInfo. It shows a floating window with something like this:

Formatters for this buffer:
<none>

Other formatters:
gofmt ready (go) /usr/bin/gofmt
rustfmt ready (rust) /usr/bin/rustfmt
shfmt ready (sh) /usr/bin/shfmt

This way you can see which linter is active for the current buffer.

[mfussenegger]

Isn't this easily visible in your configuration?

The problem is that nvim-lint doesn't have a holistic view into what linters are "active" for a given buffer.

There are:

• currently running linters. Exposed via get_running
• linters configured as default per filetype if try_lint is called without arguments (linters_by_ft)
• a ton of other options how users could call try_lint with an explicit list of linters. E.g autocmd, timers, keymaps, other plugins' events. nvim-lint has no knowledge of these

This is not like LSP where you start a process that keeps running and is attached/detached to buffers