feature request : fenced-block cells

[pierrecamilleri]

Hi, thanks for the useful plugin.

I am using quarto file format where cells are similar to markdown fenced-block starting and ending with ```.

I think it would be useful (to me at least ;) ) to add support for such cells that have opening and closing delimiters.

The difference in behavior that it would introduce and that I noticed so far :

• SlimeCells{Next,Prev} would skip closing delimiters
• ac textobject would include the closing delimiter as well (ic is already working properly).
• (optionnaly) the closing delimiter may be highlighted differently (for instance with an horizontal rule above instead of below the closing delimiter)

[Klafyvel]

Hi,
This might be feasible. But I wonder, wouldn't using a treesitter query (if you are a neovim user) be easier?

[pierrecamilleri]

I am indeed a neovim user, but relatively new to treesitter.

I don't think there is a treesitter parser for qmd quarto format yet : the "quarto-vim" plugin) I use for syntax highlighting runs on "vim-pandoc-syntax", which does not provide a treesitter parser yet. There seems to be a standard markdown treesitter parser available, but not sure how it plays with the quarto format.

If you think such functionality would be outdated as soon as a treesitter parser exists, then I don't mind waiting until the quarto tooling matures.

[Klafyvel]

I guess it shouldn't be too difficult to implement. I'm rather busy lately but if I can find some time I'll give it a try. Le mer. 29 mars 2023, 17:50, Pierre Camilleri ***@***.***> a écrit :

…

I am indeed a neovim user, but relatively new to treesitter. I don't think there is a treesitter parser for qmd quarto format yet : the "quarto-vim" plugin <https://github.com/quarto-dev/quarto-vim>) I use for syntax highlighting runs on "vim-pandoc-syntax" <https://github.com/vim-pandoc/vim-pandoc-syntax>, which does not provide a treesitter parser yet <vim-pandoc/vim-pandoc-syntax#334>. There seems to be a standard markdown treesitter parser available, but not sure how it plays with the quarto format. If you think such functionality would be outdated as soon as a treesitter parser exists, then I don't mind waiting until the quarto tooling matures. — Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABPL4LYRGAOSFP6FK26MUF3W6RK5LANCNFSM6AAAAAAWL24D3U> . You are receiving this because you commented.Message ID: ***@***.***>

[Klafyvel]

I think this issue can be easily solved if we introduced a slime_cell_delimiter_start and a slime_cell_delimiter_stopparameter and makePrev/Next` use thoses. I'll give it a try.