Closed liston closed 2 months ago
Ah, I'll work on a better layout to explain what to edit to have what effect.
In this particular case you would provide highlights
-> heading
-> backgrounds
/ foregrounds
.
The highlight for backgrounds
is used for the line and foregrounds
is used for the text.
The plugin indexes into the lists based on the level, so h4's get the 4th element. If you provide fewer elements we simply use the last one. So if you provide 3 elements we use the 3rd for an h4.
Hope that makes sense!
hover over them
, I guess it's related to treesitter?
Thank you :)
2 things:
obsidian.nvim
for example its own UI logic might be interfering here: https://github.com/MeanderingProgrammer/markdown.nvim?tab=readme-ov-file#obsidiannvim. I added some known clashing plugins to the healthcheck if you update and run checkhealth render-markdown
it might help with that and likely other weird issues that will happen as a result.@markup.heading.n.markdown
highlights in the same way you set them in the config: vim.cmd(string.format([[highlight @markup.heading.1.markdown cterm=bold gui=bold guifg=%s]], color_fg))
, for example. You can run this command at any point in your config, so long is it is after your colorscheme loads.checkhealth render-markdown
output (not sure what those errors mean though):
render-markdown: require("render-markdown.health").check()
markdown.nvim [neovim version] ~
markdown.nvim [configuration] ~
markdown.nvim [nvim-treesitter] ~
markdown.nvim [executables] ~
markdown.nvim [conflicts] ~
Not really an issue, but it is not obvious to me looking at the documentation on how to change the colors of h1, h2, h3 etc.