When indexing a project, consider handling excluded directories

[pope]

cindex doesn't have any flags to exclude a folder from being indexed from a path like ST can exclude directories from a project path. But, it should be doable to expand the one path in ST to the directories and paths that ST has in the project.

Take the following directory structure

project/
  |- dir-a/
  |    |- foo/
  |    |- bar/
  |    `- file.txt
  |- dir-b/
  |    `- bar/
  |- foo/
  |    `- bar/
  `- file.txt

If I wanted to index project, yet exclude foo, I could transform this into the following paths for cindex to search:

project/dir-a/bar/
project/dir-a/file.txt
project/dir-b/
project/file.txt

This does add a lot of expansion, and I don't think cindex should have any issues with this, but it's worth keeping an eye out for.

[metaflow]

@pope Do you keep maintaining of this project? I would like to fix this issue if you would like to review PR.

[pope]

Hit me up with one and I will review!

[metaflow]

@pope I have talked with @whoenig from original SublimeCodeSearch and he kindly added MIT license to the project thus removing argument to keep this project separate.
Do you have any interest in merging two projects or they are too distinct already and merge makes no sense?

[pope]

I'm open to a merge. As noted, licensing was one concern. The other was that this behaves slightly different.

• Results are placed in a buffer, not in a menu.
• Queries have keywords to restrict searches to filenames and case.

If we can resolve those things and come up with what SublimeCodeSearch should look like, let's do it.

Also, if you want to talk merging, let's do that on a new issue. This issue is for adding the ability to set exclude directories to the cindex command such that you're not searching in directories not listed in your project.