| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2024-02-22 | [hover] ParseLSPResult sets language 'text' for missing spec (#4699) | Oliver Albertini | |
| I have an LSP that is returning markdown code blocks on Hover with no language specified, e.g. ```` ``` Foobar ``` ```` As a result, you get "```" in the message line which is not that useful. I made the regex to catch the first code fence accept empty language as well, and if it's empty, we set it to "text". This makes it so that LSPs that return no language still produce legible restuls on the message line. Co-authored-by: Oliver Ruben Albertini <ora@fb.com> | |||
| 2023-09-16 | Fix #4505 - Handle spaces in markdown fences | w0rp | |
| 2023-08-15 | Fix error loading "text" syntax for hover (#4574) | Tomáš Janoušek | |
| rust-analyzer sometimes returns a hover result with language being "text", but there's no syntax/text.vim, so this would fail with: Error detected while processing function <SNR>150_VimOutputCallback[6]..<lambda>8[1]..ale#lsp#HandleMessage[30]..ale#hover#HandleLSPResponse[42]..ale#floating_preview#Show[13]..<SNR>161_VimShow: line 13: E484: Cannot open file syntax/text.vim Only including the file when it actually exists fixes this. | |||
| 2020-08-12 | Close #3274 - Handle basic LSP markdown formatting | w0rp | |
 |
index : ale | |
| Check syntax in Vim asynchronously and fix files, with Language Server Protocol (LSP) support | cos |
| summaryrefslogtreecommitdiff |