MeanderingProgrammer / render-markdown.nvim

Plugin to improve viewing Markdown files in Neovim
MIT License
1.37k stars 32 forks source link

bug: With default configuration I am getting different visuals #153

Closed Divyanshg01 closed 1 week ago

Divyanshg01 commented 1 week ago

Neovim version (nvim -v)

0.10.1

Operating system

Arch Linux

Terminal emulator / GUI

Kitty terminal with zsh

Describe the bug

image

When I load the default config and open the markdown files, all the heading except level 1,2 are in red color I don't know why it is

Expected behavior

It should be of different colors and the code blocks are also of different color(black) instead they should be transparent

Healthcheck output

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

render-markdown.nvim [version] ~

render-markdown.nvim [configuration] ~

render-markdown.nvim [nvim-treesitter] ~

render-markdown.nvim [executables] ~

render-markdown.nvim [conflicts] ~

Plugin configuration

return {
    "MeanderingProgrammer/render-markdown.nvim",
    opts = {},
    -- dependencies = { "nvim-treesitter/nvim-treesitter", "echasnovski/mini.nvim" }, -- if you use the mini.nvim suite
    dependencies = { "nvim-treesitter/nvim-treesitter", "echasnovski/mini.icons" }, -- if you use standalone mini plugins
    -- dependencies = { "nvim-treesitter/nvim-treesitter", "nvim-tree/nvim-web-devicons" }, -- if you prefer nvim-web-devicons
    config = function()
        require("render-markdown").setup({
            acknowledge_conflicts = true,
            latex = { enabled = false },
        })
    end,
}

Plugin error log

No error log

Confirmations

Additional information

I am using it with obsidian.nvim but I don't think this behaviour is caused by it still I am providing my obisdian.nvim config

return {
    "epwalsh/obsidian.nvim",
    version = "*", -- recommended, use latest release instead of latest commit
    lazy = true,
    ft = "markdown",
    -- Replace the above line with this if you only want to load obsidian.nvim for markdown files in your vault:
    -- event = {
    --   -- If you want to use the home shortcut '~' here you need to call 'vim.fn.expand'.
    --   -- E.g. "BufReadPre " .. vim.fn.expand "~" .. "/my-vault/*.md"
    --   -- refer to `:h file-pattern` for more examples
    --   "BufReadPre path/to/my-vault/*.md",
    --   "BufNewFile path/to/my-vault/*.md",
    -- },
    dependencies = {
        -- Required.
        "nvim-lua/plenary.nvim",

        -- see below for full list of optional dependencies 👇
    },
    opts = {

        -- see below for full list of options 👇
    },
    config = function()
        require("obsidian").setup({
            ui = { enable = false },
            workspaces = {
                {
                    name = "personal",
                    path = "~/Documents/Notes",
                },
                {
                    name = "work",
                    path = "~/Documents/Vaults",
                },
            },
        })
    end,
}
MeanderingProgrammer commented 1 week ago

Not a bug, just the default behavior.

We use the highlight groups RenderMarkdownH1Bg .. RenderMarkdownH6Bg for the backgrounds.

In the colors section of the README: https://github.com/MeanderingProgrammer/render-markdown.nvim?tab=readme-ov-file#colors, if no values are defined by your color scheme for these highlight groups then RenderMarkdownH3Bg .. RenderMarkdownH6Bg all link to DiffDelete.

You can either: