Render

[afrolino02]

I'm having a rendering question with Markdown files in Neovim, specifically when dealing with nested elements(dart) like code blocks or lists inside callouts or blockquotes. These nested elements seem to 'disappear' or render incorrectly. Do you know how can I fix that.
PD: I can't edit the title, that all the problem.

[MeanderingProgrammer]

Can you point me to the problem, I'm not seeing anything inocorrect.

Can you also send me the text in the screenshot so I can see if I get something similar.

[afrolino02]

Man, write if you can, idk if github notify other comment, my comment is below.

[afrolino02]

I'll redact well, I have a “problem” , but maybe it's the way that the plugin render, I have these notes in a code block(I'm doing a course of Flutter, and I'm taking notes with this plugin, thanks :) ), but it's render as reference IDK if it's that or what, is there a way to render as a normal code? i mean, as a normal code block without links render o something like that?

In visual mode without render

Rendering in normal mode

I'm not a native speaker, but I'm also trying to improve my writing skills, if i have a mistake tell me. :)

[MeanderingProgrammer]

If I'm understanding you correctly you don't like the background around code blocks?

Sure you can remove code block rendering with:

require('render-markdown').setup({
    code = { enabled = false },
})

[afrolino02]

Sure I'll do it, let know

[afrolino02]

print('front: ${pokemon ['sprites'][2]}'); this is the text that is rendering.
in this gist i'll let you the complete note
#The Checkhealth

==============================================================================
render-markdown:                     require("render-markdown.health").check()

render-markdown.nvim [version] ~
- ✅ OK plugin 8.4.8
- ✅ OK neovim >= 0.11

render-markdown.nvim [configuration] ~
- ❌ ERROR checkbox.anti_conceal - invalid key
- ❌ ERROR checkbox.dash - invalid key
- ❌ ERROR checkbox.winopts - invalid key

render-markdown.nvim [treesitter] ~
- ✅ OK markdown: parser installed
- ✅ OK markdown: highlights ~/.local/share/nvim/lazy/nvim-treesitter/queries/markdown/highlights.scm
- ✅ OK markdown: highlighter enabled
- ✅ OK markdown_inline: parser installed
- ✅ OK markdown_inline: highlights ~/.local/share/nvim/lazy/nvim-treesitter/queries/markdown_inline/highlights.scm
- ⚠️ WARNING latex: parser not installed
  - ADVICE:
    - disable latex support to avoid this warning
    - require('render-markdown').setup({ latex = { enabled = false } })
- ✅ OK html: parser installed

render-markdown.nvim [icons] ~
- ✅ OK using: nvim-web-devicons

render-markdown.nvim [executables] ~
- ⚠️ WARNING latex2text: not installed
  - ADVICE:
    - disable latex support to avoid this warning
    - require('render-markdown').setup({ latex = { enabled = false } })

render-markdown.nvim [conflicts] ~
- ✅ OK headlines: not installed
- ✅ OK markview: not installed
- ✅ OK obsidian: installed but should not conflict

[afrolino02]

I was looking this that i told you before docs, my question is, will the reference markdown inline renders a link without link syntax?

[MeanderingProgrammer]

Here is what my rendered output looks like:

I believe the issue on your end is the treesitter parser being out of date. After running :TSUpdate did that fix things?

my question is, will the reference markdown inline renders a link without link syntax?

I'm not sure I fully understand but I believe what you're saying is in dart accessing a map looks like a reference link. This shouldn't matter, once you have a code block in markdown the parser treats the code as whatever language the code block is. So even though you have a reference link in the code block, since it's in dart it does not get rendered as a reference link.

[afrolino02]

Thanks dude, you're the best, and I was looking this issue that explain what happened with lazyvim explain very well

[MeanderingProgrammer]

What was the solution? Setting a different conceallevel shouldn't have any impact on dart code blocks.

[afrolino02]

I had a different config in win options, it was my fault