fredizzimo

Thank you. It looks like it's getting reverted here: * https://github.com/neovim/neovim/pull/28235

The buffer is closed when you close the intro message, and you can disable it completely with `set shortmess+=I`, so it should not be a big problem. It's not easy...

This is now fixed in Neovide 0.13.0, since Neovim 0.10.0 now properly sends the intro message to UI implementation, so we don't need our own hacky workaround anymore.

~Hm, I installed monaspace v1.101 from the Arch Linux repositories https://archlinux.org/packages/extra/any/otf-monaspace/, and I'm unable to reproduce the issue.~ ~Which version of the font are you using?~ Ignore that, my mistake

Edit: **Ignore this as well, I looked at the wrong FiraCode font:** The problem seems to be that Monaspace uses center alignment of the ligatures, and not the alignment of...

This time I think I got it. For FiraCode, the following glyphs are emitted; `exclam.spacer + exclam equal.liga`, which are assigned glyph index `0+1` respectively. While Monaspace does this `emptyAdvanceWidth...

This was exactly what [worried me](https://github.com/neovide/neovide/pull/2265#issuecomment-1913058866) when we merged this: * https://github.com/neovide/neovide/pull/2265 But I had no other choice than to merge it, since the reports of hangs were getting out...

It's not an universal problem, I ran this crazy stress test in powershell `0..1000 | ForEach-Object { neovide -- --clean --cmd sleep --cmd quit }`, launching 1000 instances at the...

I also tested with the downloaded 0.12.2 from the releases and Neovim nightly installed by scoop. And no problem with that either launching 1000 instances simultaneously. This could be something...

@kareigu, that was probably the shada issue reported here then https://github.com/neovide/neovide/issues/2182#issuecomment-1913618605 Maybe we can replicate it be creating zero bytes files. For anyone that are having the problem, don't delete...