for file search, edit in the persistent buffer can rename files
for grep, edits in the persistent buffer edit across files
and so on
I think multibuffer can be good in edit/renaming use cases, but it's very annoying for fast lookups/navigation across different files (as mentioned elsewhere).
What I hate though is really unintuitive and "non-standard"[1] shortcuts in search tab.
For example "find in project": cmd+shift+f
Whereas for "find and replace in project" I'd expect: cmd+shift+r , but it's: first toggle find, then toggle find and replace. Ok, absolutely fine, but the keyboard shortcut to toggle is: cmd+shift+h - I never can remember it.
When already searching, for my "convenience", if I'd like to adjust my search or search for something new, I click cmd+shift+f and I am focused back to find input, but here's the kicker. Input have automatically changed to what word was under my cursor. So if I was looking for some long or weird string, I need to retype it again or find and copy/paste it again.
#first-world-problems though.
I got tired of babysitting vim/neovim and all it's plugins and use Zed for most of my editing. It has pretty good vim binding support and maybe I just need to remap some key bindings to have better search experience. Zed is much better at emulating vim than Cursor/VSCode.
[1] there's no standard obviously, but some things are the same/similar across most programs.
So different tastes :-)
What you describe later is "Auto-populate the find dialog with current text under cursor". VSCode has a setting for that; I guess Zed will eventually end upnadeing one too.
The multibuffer result is so nice for "hands-on" search and replace.
How else are you going to have “a quick glance at code” *across* project files without using a new view for that? It sounds like you’re describing something impossible.
Zed’s across files search solves this in a similar way as other tools. Except that in zed you can also edit the code where your search results show up. Zed also has within file search.
Jetbrains opens up a lightweight floating panel which can also be docked. So you can choose how to view the results. Like Zed, the results view is live editable, even when searching across multiple files.
The floating panel mode is good because you can do a quick search, look at it, and just whisk it away with one key. Opening results as a tab isn't terrible, but mixes one UI (search, very ephemeral) with another (editing, less ephemeral). (Zed also has this thing where search results also show in the right-hand side panel, which I've always found confusing.)
Another thing Jetbrains does better here is to remember your search settings. Your last search is always the default, whereas Zed forgets it every time. Jetbrains also has really nice file scoping via a dropdown, so it's very quick to search all non-test files, for example.
Zed keeps stealing great features from Jetbrains, so I'm sure it's just a matter of time before this gets better.
By showing the text around match inline with the search result in the tree. Especially useful if you do not expect to edit every search result. If you do expect to edit every search result, then Zed's multibuffer is arguably better/ faster.
You also have to validate the search, it doesn't start off immediately on its own, which annoys me a lot more.
Also now they've introduced this "agent first" layout which i cannot undo. They're strength is in perf, idk why try to reinvent the wheel w.r.t DX.
You can just collapse the sidebar with the agentic stuff.