sphamba / smear-cursor.nvim

Neovim plugin to animate the cursor with a smear effect
GNU General Public License v3.0
202 stars 3 forks source link

Glitchy cursor while changing line #4

Open pcorbineau opened 23 hours ago

pcorbineau commented 23 hours ago

I post also here (from reddit) for issue tracking,

Here is what I see on Windows using plugin on last master 3cacbf0 :

smearcursor

I use default conf using lazy.vim :

return {
    "sphamba/smear-cursor.nvim",
    opts = {},
}
wt --version
1.21.3231.0
NVIM v0.10.2
Build type: Release
LuaJIT 2.1.1713484068

I retry with a minimal example :

 vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
    spec = {
        "stevearc/conform.nvim",
        "nvim-neotest/nvim-nio",
        { "sphamba/smear-cursor.nvim", opts = {} },
    },
})

I didnt get the glitch as above but its clearly not smooth 😞

pcorbineau commented 22 hours ago

got the same glitch from windows terminal on cmd.exe and also on wsl2 Ubuntu 24.04

pcorbineau commented 14 hours ago

got exact same behaviour on wezterm (on Windows), I will try later on my linux laptop.

sphamba commented 14 hours ago

I'll try your configuration and let you know. In the meantime, could you check if highlight groups SmearCursorNormal* and SmearCursorNormalInverted* (with * going from 1 to 16) do exist?

pcorbineau commented 14 hours ago

It looks like I don't have highlight for Smear set up. (I'm not sure if Telescope highlights is a good command to check this, I'm a new neovim user) image

pcorbineau commented 9 hours ago

Ok super interresting . My config glitch also on my laptop linux.

sphamba commented 9 hours ago

Interesting indeed. I suspect a bad interaction with another plugin. Does the config provided in your original post reproduce the bug?

require("lazy.minit").repro({
    spec = {
        "stevearc/conform.nvim",
        "nvim-neotest/nvim-nio",
        { "sphamba/smear-cursor.nvim", opts = {} },
    },
})
pcorbineau commented 9 hours ago

I don't have the glitch with this minimal config. It looks like my config trigger this.

sphamba commented 5 hours ago

It'd be interesting to know what in your config causes this! It looks like only the definition of highlight groups is compromised. The rest of the plugin seems to work as intended.