jwortmann
jwortmann
Another one you can add: * LSP issue: https://github.com/sublimelsp/LSP/issues/1363 * Upstream issue: https://github.com/sublimehq/sublime_text/issues/1378 Btw in "Completions: initial $ not considered..." the upstream issue is listed twice.
Some more: Render diagnostics with "Deprecated" tag with strikethrough Upstream issue: https://github.com/sublimehq/sublime_text/issues/5538 --- Register view in a non-hacky way when tab is moved to create new window LSP issue: https://github.com/sublimelsp/LSP/issues/1791...
The relevant part of the Markdown content from the payload is ```... use [`&`](`&`). Example: ...``` (and there are other similar places too). Primarily I think it is a language...
Aha, there even is already an issue report for that in mdpopups: https://github.com/facelessuser/sublime-markdown-popups/issues/130 Could have saved me a bit debugging/writing time if I had seen it earlier...
Interesting, which server is it that uses such links? There is already some simple logic implemented to parse and open URIs in the form `file://path/to/file#34` on the respective line: https://github.com/sublimelsp/LSP/blob/2ac87a73b3a4d95c74d10c39caca4d5820d31e0c/plugin/hover.py#L304-L313...
1. Are you sure that the D server has the `completionProvider.completionItem.labelDetailsSupport` capability? I think this capability was renamed from `detailedLabelSupport`, so if the server still expects the old name, it...
> 1. i guess so, otherwise it wouldn't work on vscode? Yes, but I meant that maybe the D server expects `detailedLabelSupport` instead of `labelDetailsSupport` as a client capability, and...
Maybe LSP should favor `labelDetails.description`, if it exists, over `detail` for the "annotation" field, and don't show it in the "details" area at the bottom then? I think the descriptions...
> only checks if the first selection has changed so when adding new cursors **after** the existing one, the `different` is false and the handlers don't run. From the docstring...
Is there any language server which already has support for the inlay hints from the LSP specs? I just did an experimental and untested implementation at https://github.com/jwortmann/LSP/tree/inlay-hints, partly based on...