Markdown of code blocks

[AndreasMatthias]

[ I'm not quite certain whether the following issues are related to LLS or to the editor I'm using. ]

Code blocks in markdown are indented by 4 spaces. This works great in the following example. Hovering over foo shows a tooltip in which quis ... nostrum is a code block

---Lorem ipsum dolor sit amet
---
---    quis
---    nostrum
function foo()
end

But in the next example this code block is displayed as normal text:

---Lorem ipsum dolor sit amet
--- * ut labore
--- * et dolore
---
---    quis
---    nostrum
function bar()
end

Another way to mark code bocks are fenced code block. But they do not seem to work either. The code block is displayed as normal text:

---Lorem ipsum dolor sit amet
---
--- ```
--- quis
--- nostrum
--- ```
function baz()
end

[carsakiller]

---```
---This has always worked for me to write Lua code blocks
---```

Maybe it is your editor? Try VS Code?

[AndreasMatthias]

Thanks. I checked with VSCode and these fenced code blocks are displayed correctly as code. So there seems to be an issue with lsp-emacs which displays it as normal text. I'll look into this.

But my second example is displayed incorrectly in both VSCode and lsp-emacs:

---Lorem ipsum dolor sit amet
--- * ut labore
--- * et dolore
---
---    quis
---    nostrum
function bar()
end

Is this an issue with LLS?

[carsakiller]

I have never heard of simply indenting for code blocks, I don't think that is supported markdown

[AndreasMatthias]

• Indented code blocks: https://www.markdownguide.org/basic-syntax/#code-blocks
• Fenced code blocks: https://www.markdownguide.org/extended-syntax/#fenced-code-blocks

The indented code block in my very first example is handled correctly by LLS. That's why I though that it is officially supported by LLS.
But in the second example, where the indented code block immediately follows an unordered list, LLS does not recognize it as a code block.

[AndreasMatthias]

Github supports code blocks indented by 4 spaces as well:

foo
bar

But github's official markdown documentation mentions fenced code blocks only. I couldn't find indented code blocks to be documented.
https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-and-highlighting-code-blocks

[carsakiller]

Huh, didn't know that is valid. I always prefer to use fenced code blocks, so I can specify the language. Maybe the Markdown parser LLS uses is just confused by the indenting following a list element because it thinks it is a nested child element?

[sumneko]

The rendering of Markdown is completely implemented by the client, and the server mostly just concatenates the commented content and sends it to the client.

(Translated by ChatGPT)

[sumneko]

For VSCode, you can create a Markdown file yourself and use ctrl+shift+V to preview its rendering effects. As far as I know, some details may not be completely consistent with the latest standards.

(Translated by ChatGPT)

[AndreasMatthias]

Thanks for your feedback. I didn't know that the client is responsible for rendering markdown.