luukvbaal

There is a functionaltest in the neovim repo that simulates what would happen with custom sign segments in a statuscolumn when (un)placing signs: https://github.com/neovim/neovim/blob/e124672ce9a81e0ca32e6c30ea3730ad5fe981af/test/functional/ui/statuscolumn_spec.lua#L588. As long as that test keeps...

What does `:set numberwidth` say?

If it says 4 then it is expected that it will not reduce in with with that repro. It's unexpected that it is not at least 4 wide to begin...

IDK, overwriting the users' value might also lead to bug reports. Might be better to just recommend a value of 1 in the README.

> But setting it to 1 doesn't help. I got the same result as the DEMO in my OP. Then I still need a way to reproduce this first. The...

Hmm that repro seems quite different to the original issue. What exactly do you expect to happen in that repro? If you expect the width to decrease, the repro should...

I think this works like you would expect @hbiel: ```lua vim.o.nu = true vim.o.relativenumber = true vim.o.numberwidth = 1 local lazypath = vim.fn.stdpath("data") .. "/lazy/lazy.nvim" if not vim.loop.fs_stat(lazypath) then vim.fn.system({...

Yeah currently neovim only rebuilds the entire statuscolumn whenever the signcolumn is invalid and whenever the number of lines in the buffer changes. I don't think neovim should implicitly rebuild...

This `InsertEnter` autocommand forces a statuscolumn rebuild: ```lua vim.api.nvim_create_autocmd("InsertEnter", { group = id, callback = function() _G.insert = true vim.o.statuscolumn = vim.o.statuscolumn end}) ``` If the linked neovim PR gets...

Pending https://github.com/vim/vim/pull/14788. Also, for the FIXME's, the sympton is slightly different for us but the cause is the same. Instead of the blank screen Vim produces, Nvim keeps an(also incorrect)...