[eread]

Add rumdl to the list of language servers for Markdown: https://lsp.sublimetext.io/language_servers/#markdown.

For more information, see: https://rumdl.dev/lsp/.

Documentation preview: https://deploy-preview-2842--sublime-lsp.netlify.app/language_servers/#rumdl.

CC @rvben just FYI.

[netlify]

✅ Deploy Preview for sublime-lsp ready!

Name	Link
🔨 Latest commit	73f059c
🔍 Latest deploy log	https://app.netlify.com/projects/sublime-lsp/deploys/69cb1fdf67171d00072dfe94
😎 Deploy Preview	https://deploy-preview-2842--sublime-lsp.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[predragnikolic]

To be consistent with other client configs:

https://lsp.sublimetext.io/language_servers/#assembly
https://lsp.sublimetext.io/language_servers/#clojure

I would suggest to inline the json configuration on the language_servers.md page.

[rchl]

To be consistent with other client configs:

https://lsp.sublimetext.io/language_servers/#assembly https://lsp.sublimetext.io/language_servers/#clojure

I would suggest to inline the json configuration on the language_servers.md page.

I don't agree. If there is an upstream documentation the it's better to link to it to avoid having to maintain two places and potentially getting out of sync.

[jwortmann]

I don't agree. If there is an upstream documentation the it's better to link to it to avoid having to maintain two places and potentially getting out of sync.

Ideally upstream docs would link to our docs page. Then we can easily update it if some parts of the configs change in the future, eg. point 2 in #2800.

To follow the conventions from the rest of the page, I'd say the server name should also not be formatted as inline code.

[eread]

Thanks for the feedback @predragnikolic @rchl @jwortmann

I've rebased and refactored this one. I'm on board with inlining the configuration here, and making that the source of truth. As @jwortmann said (#2842 (comment)), that would allow this project to document what is valid configuration.

Assuming this PR is merged, I'll raise a PR on the rumdl project to look at establishing the docs on this project as the source of truth.

[jfcherng]

Just a FYI. https://github.com/jfcherng-sublime/LSP-rumdl (it just downloads binary from GitHub)

I am fine to move it to sublimelsp org.