Noice is currently broken on Nightly (fixed)

[folke]

The big tui rework has been merged, which is really cool and will eventually make Noice work even better.

However, at this moment, Noice is unstable on nightly.

Last commit that works with noice is neovim/neovim@99cf111

Issues

• Crash with :redraw from vim.ui_attach() callback neovim/neovim#21604
• Assertion in rbuffer_consumed_compact tripped neovim/neovim#21299

[dbalatero]

I've been meaning to check out noice but I'm also on nightly. Would you mind updating this issue/thread once everything's stabilized? Thanks!

[folke]

I will. For now it's just waiting till the linked issue is fixed

[crivotz]

I have the same problem as the linked issue by doing =G or gg=G or =% only in normal.
I will stay on the stable for now, thanks for the work

[kierun]

Everyone here probably knows this… However, for anyone using bob: bob use 99cf111 will get you the last bleeding-edge version of Neovim before the bug.

[przepompownia]

No crash with the initial example from neovim/neovim#21604 (after update by Lazy) and in my regular environment 🎉

[surmish]

Should LazyVim change to make version false for noice?

[folke]

@surmish I just released a new version, so you can just update LazyVim

[folke]

Together with @bfredl, we've been able to come up with a work-around for the Neovim crashes with Noice, so everything should pretty much work the same as it did before the TUI rework. You can ignore my comments above about impaired functionality. Everything should work again with a recent nightly.

If you would still experience crashes, please let me know in the comments.

[folke]

Are there any other macos users that still experience segfaults?
I'm running Linux and didn't have any segfault anymore since my fix.

See also:

• bug: Crash for large lua file (with lsp configed) #315

[max397574]

I didn't experience any

[przepompownia]

I still don't have regular crashes as such from neovim/neovim#21604

[folke]

@przepompownia you do have crashes or you don't? :)

[przepompownia]

Restricting the scope to described in the above Neovim bug I don't (we can stick to this scope here ;)) :)

In last days i got some crash after enter some input but I'm not sure if it was related to Noice or UI separation and I cannot reproduce it.

[camin-mccluskey]

@folke MacOS user here. Started to notice crashes in the last week or so. I assumed I was hitting some weird "quit all" keycombo (I'm fairly new to LazyVim). Dug in a bit today and realised they are SegV of the type mentioned here.