bug: line highlights/signs are not applied until leaving insert mode

[hneutr]

Neovim version (nvim -v)

0.10.4

Neovim distribution

LazyVim

Operating system

MacOS

Terminal emulator / GUI

kitty

Describe the bug

when, for example, adding a new heading, the highlights/border/signs/etc are not applied until insert mode is left, which is new behavior. The same is true for horizontal rules.

[MeanderingProgrammer]

I'm going to need an example as well as your config, this does not happen for me. There are edge cases depending on when the debounce runs and your typing speed but as is this is far too vague.

[hneutr]

Hm, I'm going to close this for now as it looks like this behavior isn't present with a minimal config. Apologies!

[hneutr]

Okay, not sure if this is or is not a bug on your end of things or on Lazy.nvim's side, but I've figured out how to replicated the bug — it shows up if the configuration in Lazy.nvim has ft = "markdown". Here's a minimal vimrc:

-- Settings
vim.opt.termguicolors = true
vim.opt.cursorline = true
vim.opt.number = true
vim.opt.relativenumber = true

-- lazy.nvim setup
local lazypath = vim.fn.stdpath('data') .. '/lazy/lazy.nvim'
if not vim.uv.fs_stat(lazypath) then
    local lazyrepo = 'https://github.com/folke/lazy.nvim.git'
    vim.fn.system({ 'git', 'clone', '--filter=blob:none', '--branch=stable', lazyrepo, lazypath })
end
vim.opt.rtp:prepend(lazypath)

require('lazy').setup({
    spec = {
        -- Some colorscheme
        {
            "catppuccin/nvim",
            lazy = false,
            name = "catppuccin",
            priority = 1000,
            config = function() vim.cmd.colorscheme("catppuccin") end,
        },

        -- Minimal nvim-treesitter config
        {
            'nvim-treesitter/nvim-treesitter',
            build = ':TSUpdate',
            config = function()
                ---@diagnostic disable-next-line: missing-fields
                require('nvim-treesitter.configs').setup({
                    ensure_installed = { 'markdown', 'markdown_inline', 'latex' },
                    highlight = { enable = true },
                })
            end,
        },
        -- Plugin settings
        {
            'MeanderingProgrammer/render-markdown.nvim',
            dependencies = { 'nvim-treesitter/nvim-treesitter', 'echasnovski/mini.nvim' },
            config = function()
                require('render-markdown').setup({
                    render_modes = true,
                    heading = { border = true },
                })
            end,
            ft = "markdown",
        },
    },
})

To replicate the bug, open a file, type insert "# heading" and you will see that the highlights aren't applied until you leave insert mode. If you remove ft = "markdown" from the above config, highlights will be applied as normal.

[MeanderingProgrammer]

I do get the same behavior, thanks for digging into it. Another edge case with lazy loading, wonderful! If you open up another buffer that new buffer will work as expected.

Most likely the bug started from this commit: 1ba6fb7, which was done to handle a problem when lazy loading using vim-plug.

[MeanderingProgrammer]

Should be fixed by: b9c98ff

[Dupond]

I know you don't want to support lazy loading, and I assume it's intended, but just in case it wouldn't be intentional: this commit impacts lazy loading with vim-plug; with this commit, render-markdown is only applied after 5 seconds. However, it's immediately applied if I press j or l keys; but it's never applied if I immediately enter Insert mode.

[MeanderingProgrammer]

Should be fixed by: 4645c18