Do you have a link to an issue, so I can know if I should be worried about this?

Here: https://github.com/zed-industries/zed/issues/38109

Similarly, I had to stop using Zed because the main thread would beachball for > 30s when trying to work in large repos on macOS. This behavior was clearly reported to them in a GitHub issue that they also closed without fixing (because they believed a partial fix was sufficient, and have ignored subsequent comments to the contrary): https://github.com/zed-industries/zed/issues/55746

Ah, yeah, I get this issue too but I've been so conditioned to close and reopen files that I've stopped thinking it was an issue. Appreciate the link.

> Closing this as I expect many of the remaining problems described in this issues comments to be fixed by #51208. > > Once that PR makes it to stable (expected March 25th 2026), please create new issues if you are still experiencing problems.

Did you open a new issue?

No, but I posted on the existing one. Sounds worth trying.

edit: Done

Woah. I’ve been meaning to check out zed but that’s a huge problem. I’ve fixed this problem before in rust, there’s just a library you can use to update file trees with a combination of batching fs notifications and a periodic rescan. Wtf guys! Maybe I’ll submit a PR… oh wait! I mean delta. :(

What is that library name? Sounds helpful.