Closed norbeyandresg closed 1 month ago
This is another limitation of using neovim < 0.10.0
, since this feature conceals and inlays content.
I'm curious what would be a better way to handle this?
vim.notify
None of these sound ideal but I also don't want to triage bugs like this. I'm very open to suggestions I just don't have a good way to handle it at the moment. The best I've been able to do is say some features will not work
for older versions in the health check but keeping the list of exactly what doesn't work up to date and understandable is not feasible.
Logging an error and submitting logs sounds reasonable and easy 🙂
Logging sounds good. Does this type of limitations generate an error in other versions of vim rather than 0.10? Or what you're going to put into that logs?
Could be confusing if is just a regular error that doesn't point to the vim version
Not using vim.notify, this plugin has a logger that appends to a file. I've updated the issue template to ask for this file's contents and updated the logic to add an error log when inline marks are skipped due to version.
More details in: https://github.com/MeanderingProgrammer/render-markdown.nvim/commit/7986be47531d652e950776536987e01dd5b55b94
Neovim version (nvim -v)
0.9.5
Operating system
MacOs
Terminal emulator / GUI
Alacritty
Describe the bug
Wikilinks are not rendering properly when add alias to it
Expected behavior
Healthcheck output
Plugin configuration
render-markdown.nvim
treesitter.vim
Confirmations
Additional information
No response