bfredl

This now works in a base x86-64 linux system without `base-devel` or any system /usr/include headers, etc ``` curl "https://ziglang.org/download/0.12.0/zig-linux-x86_64-0.12.0.tar.xz" > zig.tar.gz tar xf zig.tar.gz curl "https://codeload.github.com/bfredl/neovim/tar.gz/f39f1b9dd5c39bf32157fc56676e834fa6a5c698" > neovim.tar.gz tar...

> I mention this because it's kind of the implementation that I had mind: a function similar to update_screen() but that doesn't call win_update() for every window, just a specific...

before investigating this more, can someone confirm they still see this after #27871 ?

> since it's just an optimization without any profiling data to back up the need for it. No, it is not. Logs were just published 15 minutes ago. We do...

A hypothesis is that we lack enough synchronization between UI packing and non-UI packing (might need to flush UI messages if we have a reason to send a notification in...

> Reverting something just before a release that has been open for two months without a proper fix, is not a panic revert ?? details that identifies **this particular crash**...

Do we still want this for 0.10 ?

Hmm, it is not clear to me what problem this solves. Maybe someone who actually uses the pedit/ptag functionality (either directly or as part of a plugin) could chime in...

> I don't know when to hide the message displayed by msg_intro The root issue is that this is not defined in vim to start with. it just disappears whenever...

> Nvim doesn't crash in that case though, but just does not read on from the pipe and therefore does not act upon the message (which includes responding here, I...