Repository navigation
Remove (seemingly incorrect) workaround for old markdown parser - #2930
Conversation
|
We can add a workaround inside LSP-clangd itself. Probably something like |
|
Why does the code flow not use the CommonMark parser from mdpopups? |
It does: Lines 601 to 602 in 5561bfa But only if supported by the mdpopups version (i.e. on ST dev build). |
|
So: it should be auto-fixed when MARKO_MD_PARSER_VERSION becomes true-ish for the majority of users. Then we can remove the workaround. I will revert this because it breaks my hover info. |
|
Wait. I said that I will add this workaround to LSP-clangd instead, where it belongs. |
|
And please follow our convention and only push any meaningful changes to main through a PR. |
|
Not all users use LSP-* helper packages... so that would only help for a subset of the users. |
OK, I'll keep it in mind. |
I think this is a pretty weak argument. We don't have numbers of course but why would one not uses dedicated package for it given that it provides all the extra convenience like documented settings and extra features? And also that's the documented way to set up clangd according to our instructions. It doesn't even use managed server by default so those who have problem with that shouldn't complain either. I think that if someone is in the minority that is not using that package should also not mind this minor rendering inconvenience. I don't want to create a conflict about this now but I really think you should revert your revert. It's an issue in clangd so we shouldn't create incorrect and non-compliant workarounds that break rendering in other servers. |


Discussion and context in #2928
Fixes #2928