Augment "index_exclude_patterns" to understand directories

[Zooce]

Currently, the "index_exclude_patterns" setting does not understand directories; only files. Teaching "index_exclude_patterns" to understand directories would be extremely useful. Let me explain why.

I use Sublime Text 3 at my job to work on a massive project. Sublime Text 3 can handle this project with no problem. However, our project has many directories that contain files that don't need to be indexed. An example of one of these directories is .git/. For me, although it is unnecessary to have the .git/ directory indexed, I still need to see it in the sidebar since I make changes to the .git/config file quite often. Thus using the "folder_exclude_patterns" doesn't work here (I'm under the impression that folders defined here are also excluded from indexing - please correct me if I'm wrong).

Interestingly, I found a very annoying issue because the .git/ directory is being indexed, where a Git plugin for Sublime Text 3 calls git status every few seconds to watch for changes to git's working set. This call creates a new file called index.lock in the .git/ directory and then deletes it when it's done. When this file gets created it ends up triggering the indexer in Sublime Text 3. While the indexer is starting up, the index.lock file is deleted and Sublime Text's UI freezes up for a second or two.

Teaching "index_exclude_patterns" to understand directories would eliminate that annoying issue, and save a good amount of time wasted on unnecessary indexing.

Example Usage:

{
    "index_exclude_patterns":
    [
        "*.log",
        "*/.git/*"
    ]
}

The above example would exclude all files with the .log extension from being indexed, as well as all files within any directory named .git/.

[wbond]

This was fixed in build 3158.