Unable to conceal code block backticks

[keithlxs]

Hello,

I'm having difficulties getting the inline code and code block backticks (```) to conceal. I'm not sure if I'm doing something wrong. Below is a screenshot of the code block not concealing. There are no borders that are being rendered despite including them into the configuration.

Code block

Inline

configuration
opts =
{
render_modes = true,
bg_color = 'NONE',
heading =
{
backgrounds = {},
icons = {'󰼏 ', '󰼐 ', '󰼑 ', '󰼒 ', '󰼓 ', '󰼔 '},
},
--removing code higlight, not needed for my case
code =
{
--highlight = 'bg_color',
--highlight_inline = 'bg_color',
border = 'thick',
above = '▄',
below = '▄',
width = 'block'

},

Any suggestions or pointers on what I could be doing wrong?
Thank you!

[MeanderingProgrammer]

The checkhealth should have an error for this, but the backtick concealing behavior comes from the default highlights in nvim-treesitter, not this plugin directly. So you need to enable the highlights module if you want this behavior:

require('nvim-treesitter.configs').setup({
    highlight = { enable = true },
})

[keithlxs]

Thank you for the assistance!! Do you think it could be possible to add the conceal for backticks without the reliance of treesitter?
I know the markview.nvim plugin can do it but I find the configuration of your markdown plugin easier to understand.

[MeanderingProgrammer]

markview does a few things that while totally fine, are choices I will not make for this plugin. One is shipping with its own set of highlight queries overriding any user defined ones. The other is re-implementing behavior that comes from those same queries.

There's some balance here of being easy out of the box with limited knowledge needed and playing nice with the rest of the ecosystem. I lean more into the ecosystem where I think it makes sense (totally arbitrary decision), and having tree-sitter highlights enabled using the default upstreamed highlights is I think a fair thing to rely on when the plugin requires tree-sitter as a starting point. That's also why validating highlights is part of the health check.

I get the idea and appreciate where it's coming from, but for now I'll continue to rely on things outside of this plugin to enable this behavior, maybe I'll change my mind on this at some point in the future. Hopefully it kind of makes sense where I'm coming from.

[keithlxs]

The checkhealth should have an error for this, but the backtick concealing behavior comes from the default highlights in nvim-treesitter, not this plugin directly. So you need to enable the highlights module if you want this behavior:

require('nvim-treesitter.configs').setup({
    highlight = { enable = true },
})

Thank you for the suggestion. I attempted to enable the highlight you mentioned to the render-markdown config, more specifically in the opts {} area but it wasn't working. I was getting the error below. Maybe I'm adding it in the wrong place. Could you take a look?

[MeanderingProgrammer]

This blob:

require('nvim-treesitter.configs').setup({
    highlight = { enable = true },
})

Should be added to the nvim-treesitter configuration, not the opts for this plugin. It is a completely separate thing from this plugin.

I don't know what your configuration looks like so I'm not sure how you should go about adding it (opts doesn't really work with nvim-treesitter AFAIK), but somewhere you probably have nvim-treesitter configured, add the highlight = { enable = true } settings there.

[keithlxs]

This blob:

require('nvim-treesitter.configs').setup({
    highlight = { enable = true },
})

Should be added to the nvim-treesitter configuration, not the opts for this plugin. It is a completely separate thing from this plugin.

I don't know what your configuration looks like so I'm not sure how you should go about adding it (opts doesn't really work with nvim-treesitter AFAIK), but somewhere you probably have nvim-treesitter configured, add the highlight = { enable = true } settings there.

Thank you!! I got it working thanks to your assistance. I completely understand and respect your decision on the plugin's direction. Your the author after all lol.
I was thinking maybe having everything work out of the box or plug-n-play might be a good idea and also because it seems like there is a default markdown parser that's already included in neovim. But like you mentioned earlier, having a balance is important too. Cheers!