Seth Daniel
Seth Daniel
@cPMarco if you place the cursor under the thing you wish to see the definition of and then type `:lua vim.lsp.buf.definition()`. If *that* works then you have everything setup correctly...you...
@ketbra I think packaging the package.json would likely work. I'll test it on my end before saying anything definitive.
I was wrong about how it gets the schema information. It's not clear to me how it can be kept always up-to-date the way it is being done. For now...
This seems reasonable. I wouldn't want it to be the default and I would want to be able to do a "one off" where it shows me the error(s), but...
Using `:MasonLog` is fine. You can also re-run the installation within `:Mason` and see any errors that occur. I don't think it's unreasonable to want to see errors using `:messages`...
Startup seems improved by recent PR #61
Closing. The `start_delay` has helped and there has been no feedback since.
perhaps using LspProgressUpdate event.
LspProgressUpdate will work with the caveat that any LSP status plugin that overwrites the status update handler will keep it from working. Regardless, this is probably the way to go.
ATM it seems that if I have two autocmds (even in different groups) that are `User LspProgressUpdate` the events are somehow distributed between the two listeners instead of all events...