TJ DeVries

We should add a different output format maybe that is JSON or something and you could just put in qflist programmatically

Yeah, we can add some documentation for it definitely. I would prefer to use it doing the docgen style we've used for telescope and some other projects, but I haven't...

https://github.com/tjdevries/tree-sitter-lua/blob/master/HOWTO.md And then in telescope: https://github.com/nvim-telescope/telescope.nvim/blob/master/scripts/gendocs.lua (this is being actively worked on, we have some weird grammar bugs occasionally which i'm working on tracking down)

have you tried `:help vim.lsp.diagnostics.set_signs()` info? ``` sign define LspDiagnosticsSignError text=E texthl=LspDiagnosticsSignError linehl= numhl= sign define LspDiagnosticsSignWarning text=W texthl=LspDiagnosticsSignWarning linehl= numhl= sign define LspDiagnosticsSignInformation text=I texthl=LspDiagnosticsSignInformation linehl= numhl= sign define...

That todo is for a different thing (there was some error when trying to _find_ the signs that had been displayed. it's an internal bug I think, not related or...

Ah, I meant to just try the ex commands listed in the docs to configure the signs.

:laughing: such is life. No worries. I changed the names in the PR because they were randomly named before and now follow a pattern, so at least you're not too...

Two options (I'm open to either): 1. Create `sync_` or `_sync` variants of functions 2. Allow any function that could be sync/async to have an optional final `callback` parameter that...

I think perhaps it's better to not even have this anymore. You can just use `vim.diagnostic.get` since that already does workspaces. I think I should just remove it completely, what...

Hmmm, it would probably be good to add an API around seeing if there exists any keymap for a particular key.... we do not have it yet though :laughing: I...