Global/project search should respect a global .gitignore

[dabljues]

When using global search in my rather large project, I find that the search is really slow. Comparing to VS Code - really slow, like orders of magnitude.

The thing is, I have some gitignored files in my repo. But they are not gitignored inside my repo, I ignore them via the .global-gitignore in my dotfiles. VS Code doesn't respect the global gitignore, but is still really fast, instant (I guess because of the ripgrep).

But, VS Code has the option to respect the global gitignore config: microsoft/vscode#59364

"search.useGlobalIgnoreFiles": true,

Is there a way for zed to also have this? Or better yet - improve the search performance (I know that there are already issues about that, so this issue is I guess only about the usage of global gitignore files). When I added one problematic folder to either:

• local .gitignore in my repo
• file_scan_exclusions in the settings

, the search was near instant. That doesn't solve the issue of the search being really slow, but it could help with it. I can obviously add this stuff to my file_scan_exclusions and be done with it, but I guess having an option to have it in a global gitignore and zed respecting it is better,

[dabljues]

There's another thing. For now, I moved stuff to file_scan_exclusions, but I sometimes want to see the dirs I added there (because I added them to file_scan_exclusions solely for the purpose of excluding them from the global search) in the file tree. But adding something to file_scan_exclusions obviously also removes it from the file tree.

However, having something git ignored doesn't make it disappear from the tree. It's visible, greyed out. So having something in the gitignore makes it so:

• search ignores it
• I can still see it in the file tree (which is desirable on many occasions)

This is to say that making zed respect the global .gitignore will be even more beneficial, since I cannot add all the stuff I want to the .gitignore in my repository (because other people use it, obviously) and moving it to file_scan_exclusions removes it from the file tree.