jwortmann

After reading the minihtml documentation again, I think there should in theory be a pretty simple way to optionally let color schemes override the predefined styles from the default CSS...

Yes, I believe this should work the same. I suggested `body#mdpopups` because it seems to be the preferred way according to the documentation. But in case of `.mdpopups` the only...

I tested my example above with a color scheme CSS rule `.mdpopups .lsp_popup div.warnings` to override the plugin CSS, but it still doesn't seem to work. New properties from the...

I've gotten it to work! There were a few pitfalls that I had to figure out: * the SDL function expects the pixel data as an array of UInt32 numbers,...

The server settings are part of the `"clients"` setting, so if they are modified, servers are still restarted. `didChangeConfiguration` would need to be implemented separately. This PR is only for...

> That means that you touch some setting and now all the open views start missing something (semantic highlighting, for example). Semantic highlighting does get redrawn (added/removed) after changing the...

Actually for inlay hints we were already doing almost the right thing. The `"show_inlay_hints"` setting is different in the way that it is only used as the default value for...

Semantic tokens should now be requested/updated if the userprefs change and semantic highlighting is enabled (regardless whether that setting actually changed or not), *as soon as the view gets activated*....

> You can either override this file: https://github.com/sublimelsp/LSP/blob/main/language-ids.sublime-settings No, this is not used for the syntax highlighting in popus. You can either add ```jsonc "mdpopups.sublime_user_lang_map": { "typst": [["typst", "typc"], ["Typst/Typst"]]...

It doesn't work because the `let test();` expression is implicitly considered to be within a code context, so by itself it is just not highlighted by the Typst syntax highlighter....