Confusion encountered by the `autocomplete-paths` plug-in

> I encountered these problems when using the `autocomplete-paths` plug-in, and I hope my English speaking compatriots can help submit them to the author on github.

1. The `autocomplete-paths` plug-in always competes for all file indexes in the global directory, whether you can specify the directory to index or the directory not to index.Because not all the directories in a project need to be indexed, this creates a lot of unnecessary problems

2. The `autocomplete-paths` plug-in, which is not clear about the way to set the files to be indexed, can it be optimized to edit directly in the background of the plug-in, such as:

```js
[' HTML ', 'js',' json ', 'PHP', 'c']
```

3. Don't know whether caused by the mechanism of the atom itself, why every time is to the index, this depends on a bit of a problem, and the other ide in terms of the index are increase and change the contents of the change, rather than to the index, whether can the project directly increase the index file, so can more convenient and intuitive, of course, the atom itself might be the problem

The report concerns the autocomplete-paths plug-in in Atom, but names no files, tests, or code entry points. First separate and reproduce the three requests: configurable indexed directories, clearer indexed-file settings, and incremental indexing. Work is complete only when the maintainers define which request is in scope and its expected behavior.

Written by the indexing model from the issue text.