bug: CodeBlock not works

[noahlias]

Neovim version (nvim -v)

v0.11.0-dev-1844+gc3337e357a

Neovim distribution

N/A

Operating system

macos

Terminal emulator / GUI

kitty

Describe the bug

It seems I updated to the latest version of neovim and update the new version nvim-treesitter, it not works as expected.

When I revert this change
nvim-treesitter/nvim-treesitter#7685

It works as expected.

Expected behavior

I hope it works with the latest nvim-treesitter.

Healthcheck output

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

render-markdown.nvim [version] ~
- OK plugin 8.0.12
- OK neovim >= 0.10

render-markdown.nvim [configuration] ~
- OK valid

render-markdown.nvim [treesitter] ~
- OK markdown: parser installed
- OK markdown_inline: parser installed
- OK latex: parser installed
- OK markdown: highlight enabled

render-markdown.nvim [icons] ~
- OK using: mini.icons

render-markdown.nvim [executables] ~
- OK latex2text: installed

render-markdown.nvim [conflicts] ~
- OK headlines: not installed
- ERROR obsidian: installed
  - ADVICE:
    - Ensure UI is disabled by setting ui = { enable = false } in obsidian.nvim config

Plugin configuration

{
  code = {
    right_pad = 1,
    sign = false,
    width = "block"
  },
  file_types = {
    [2] = "Avante",
    [3] = "copilot-chat"
  },
  heading = {
    sign = false
  }
}

Plugin error log

N/A

Confirmations

• I have updated this plugin to the latest version using my plugin manager
• I have provided the text contained in all screenshots as raw text in this issue. This means if there is a screenshot below it is the copy pasted contents of the file in the screenshot. I understand that my issue will be closed if I have not.

Additional information

No response

[MeanderingProgrammer]

This should only impact 0.11, since the coneal_lines directive is relatively new: neovim/neovim#31324.

I think 0.11 in general is going to come with some breaking changes for this plugin from a combination of async treesitter parsing & new mark / highlighting features.

I'll create an overall issue to get ahead of these.

[MeanderingProgrammer]

Will keep track here: #352

[maxrzaw]

I think this is related to this, but when using lsp_hover I am having issues that I believe are caused by this plugin.

With this plugin disabled:

With this plugin enabled:

The text in the buffer is:

```lua
(field) cond: boolean = true
```

[lmnzx]

@maxrzaw yeah i am also facing some weird visual issues with lsp hover

can we disable render-markdown for lsp and only have it enables on .md files??

[MeanderingProgrammer]

The conceal_lines highlight being on by default is going to cause some strange behaviors.

@maxrzaw I'm actually not sure why you're seeing the raw fenced code block, can you try updating the plugin and see if it still looks like that?

@lmnzx I've got no idea what's going on there, seems like one decoration is being shifted into the incorrect position, potentially related to this: neovim/neovim#33033, but honestly not sure.

Yeah, you can disable this plugin for LSP hover docs with:

require('render-markdown').setup({
    overrides = {
        buftype = {
            nofile = { enabled = false },
        },
    },
})

[MeanderingProgrammer]

Should work after: e6c8081