Vlad

Seem like you just ignore them. https://github.com/folke/which-key.nvim/issues/79

> I'm not sure what the task `All formatting changes by the build are committed` refers to? Hi there, I can help out with this. When you build this repo...

As a patch in Neovim I added the following auto command to restart prettierd on config changes: ```lua vim.api.nvim_create_autocmd({ 'BufWritePost' }, { group = vim.api.nvim_create_augroup('RestartPrettierd', { clear = true }),...

Some discussions that may or may not be relevant: https://github.com/neovim/neovim/pull/9496

This should hopefully work now after merging: https://github.com/MeanderingProgrammer/markdown.nvim/commit/726c85cb9cc6d7d9c85af6ab093e1ee53b5e3c82. Will keep this open to track any resulting problems.

A week is probably long enough to catch any glaring issues, no need to keep this around, happy it seems to be working as expected :)

I think it's a neat idea, but I don't think I'm going to be the one to add it. This plugin relies heavily on `treesitter` to do all the real...

Have added support for the callout text here: https://github.com/MeanderingProgrammer/markdown.nvim/commit/43bbefd410333a04baf62ddfa8bb2a2d30a1bbc1 There is still the issue of matching the highlight of the quote marker to the callout which I'll track here: https://github.com/MeanderingProgrammer/markdown.nvim/issues/24...

Thank you for the kind words 🙂 I think this might be getting a little out of scope of a markdown rendering plugin. Since the GHM callouts hijack standard markdown...

Closing for now, feel free to re-open with some details.