Project-specific settings file

[JosephTLyons]

Depending the project, there is quite a bit of noise in some of my file searches. I would like to be able to exclude some directories (virtual environment directories, npm module directories, etc.) from being searched through when using command+p to find a file, to remove as much noise as possible. I'm guessing this implies some sort of project settings? I think it could just be as simple as a hidden json file, that gets committed with your project, that excludes items via patterns:

A small example might be:

{
    "excluded_patterns": [
        "<some-path-prefix-starting-from-project-root>/some_specific_file.py"
        "<some-path-prefix-starting-from-project-root>/some_specific_director/*",
        "*.scss"
    ],
}

Some open-ended questions about this:

1. When a directory is added to an exclusion list in a project setting file, what all is affected?

   • Does it affect what shows up in the file browser on the left?
   • Does it affect searches?
   • Does it affect searching for files?
   • etc.

   Or are all of those separate project settings?

2. What other sort of settings might be useful in a project settings file? Or maybe its best to let those surface naturally, over time.

---

The alternative is to hide and exclude things based on what is .gitignored, but I lean towards it being separate from that, because I can imagine times I'd want to be able to find things that are .gitignored.

[JosephTLyons]

Closing in favor of: https://github.com/zed-industries/feedback/issues/70