fredizzimo
fredizzimo
I have now fixed the issue that caused the intro message to get stuck in Neovide, it turns out that `packer.nvim` can cause `VimEnter` to be sent at least twice....
This is very easy to reproduce manually 1.nvim 2. :terminal 3. Resize the window rapidly, and observe that it crashes very quickly
I add the info here, where it belongs as well. I just noticed that the trick seems to be to make the window small enough so that the prompt wraps...
`nvim -clean` and a standard bash prompt is enough on my system, but I originally reproduced it with my standard configuration an zsh with a custom powerlevel 10k prompt. Both...
Alacritty with default settings. But I can reproduce it in Wezterm and Konsole too, but not XTerm.
@clason, If you mean c855eee91, then yes reverting that seems to fix the issue Edit: It's enough to set this to false https://github.com/neovim/neovim/blob/7668f89d5be6d463bf6ab0c2d3a0393e3ec26e7f/src/nvim/terminal.c#L223
No, problems. I haven't had any issues with this in practice. It's just something that I found out when testing another Neovide bug. I'm forced to use nightly, since the...
Since I can easily repeat this, I added a bit more logging: ``` Resizing from 54x9 to 54x1; cursor was at (40,1) rows [0..0]
@bfredl, I was going to propose something like that myself, when I have more time to think about it, as the native floating window borders are also broken in the...
I have been thinking about this and going to start working on a solution soon. I think we need to remain flexible and allow these "widgets" anywhere in the window,...