File Finder forgets open buffers when filtering

[djrenren]

Summary

If I have an open file that is outside the current workspace, I cannot open it by typing its name in file finder

Steps to trigger the problem:

1. Create a workspace folder demo
2. Open demo in zed.
3. Open a terminal (ctrl-`) and create a new file one directory up touch ../findme.txt
4. Open that file in the current zed window zed ../findme.txt
5. Open the file finder cmd-p (Note that findme.txt is listed)
6. Type a prefix of its name: fi
7. Note that file finder reports "no matches"

Actual Behavior:
File finder is unable to locate a file it previously knew about

Expected Behavior:
It should list the file after typing a prefix of it.

Zed Version and System Specs

Zed: v0.172.10 (Zed)
OS: macOS 15.0.1
Memory: 36 GiB
Architecture: aarch64

[djrenren]

I've looked at the File Finder source code and can see what's happening. It has the notion of workspace files and "history".

Initial contents include "history" but upon filtering the history is lost. History is also distinct from the list of open buffers. This means if your extra-workspace file (findme.txt) ages out of this list, it's incredibly hard to find.

[JosephTLyons]

Nice catch @djrenren - strange that its in the list initially, but not when searching.