fredizzimo

I'm not sure if `ext_hlstate` can be fixed without completely breaking existing potential uses. Even if the `ui` key of `info` array actually referred to the original built-in highlight group,...

I'm not sure about mixing two different types of concepts here, just to get rid of an additional extension. 1. The highlight groups. * Have attributes assigned to them *...

> >We also can't afford millions of pointless ext_hlstate events when deleting text, but that's a bug and should be fixable. > Can we start with that? Only if we...

> > but that was turned down by @bfredl here [#23610 (comment)](https://github.com/neovim/neovim/issues/23610#issuecomment-1867430580) > > It was """turned down"""" together with a concrete solution of the original problem which still stand...

This PR solves the original problem. I don't see why we need a duplicate solution for it.

I don't know if it's the same issue or not, but there's a similar issue here * https://github.com/neovide/neovide/issues/1964

I can repeat this as well. And it looks like it might be related to this https://bbs.archlinux.org/viewtopic.php?pid=2161746, which might be a kernel bug, or a packaging bug in Arch Linux....

It can be repeated with just one instance as reported in the original post of this issue on some systems. And I original detected this when running the Neovim unit...

We just got this bug report in Neovide, that might be related, but it's too early to tell for sure * https://github.com/neovide/neovide/issues/2452 Based on the logs, it looks like some...

@bfredl, reverting to https://github.com/neovim/neovim/commit/6525832a8c4d44a8ebabba02a5ea1ce09b389a4f, fixes the issue in Neovide, so I'm fairly sure that https://github.com/neovide/neovide/issues/2452 is the same bug, we just detect the error and report it earlier than the...