Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Confusion encountered by the autocomplete-paths plug-in #215

Open
linjialiang opened this issue Sep 19, 2018 · 0 comments
Open

Confusion encountered by the autocomplete-paths plug-in #215

linjialiang opened this issue Sep 19, 2018 · 0 comments

Comments

@linjialiang
Copy link

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:

    [' 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant