Default exclusion glob pattern about vscode-comment-anchors

[gsabater]

That is a good start for performance.

I would also propose an additional option to enable/disable the workspace scan on startup.
Maybe a command to perform the scan would be more useful.

A word about performance, i don't know how the scan is performed, but looks like vscode is actually opening all the files, and setting the CPU on 100% leaving the machine almost unusable for a minute or more. The problem with opening files is that other extensions like phpinteliphense and linting perform their actions as well.

There are another extension called todo+ that has a command to parse all todo's (fixme, readme, etc) in the whole project, and has the result in mere seconds without opening a single file, or at least, vscode dont perform opening operations.

I don't want to hijack an issue, if you @macjuul think that those comments should be a new issue, just move it or tell me.

[macjuul]

Ah yes, I unfortunately did not notice that because VS Code was already excluding node_modules from my project, I'll make a quick hotfix and release it today.

Thanks for your issue!

[babakks]

Just one more thing: please correct "matchFiles" in README.md, which should be "excludeFiles" instead.

[macjuul]

That is a good start for performance.

I would also propose an additional option to enable/disable the workspace scan on startup.
Maybe a command to perform the scan would be more useful.

A word about performance, i don't know how the scan is performed, but looks like vscode is actually opening all the files, and setting the CPU on 100% leaving the machine almost unusable for a minute or more. The problem with opening files is that other extensions like phpinteliphense and linting perform their actions as well.

There are another extension called todo+ that has a command to parse all todo's (fixme, readme, etc) in the whole project, and has the result in mere seconds without opening a single file, or at least, vscode dont perform opening operations.

I don't want to hijack an issue, if you @macjuul think that those comments should be a new issue, just move it or tell me.

I'm currently working on a fix that changes the way files are loaded and scanned, which should solve that. I'll also implement a setting to disable workspace anchors for those who aren't interested in it.

Just one more thing: please correct "matchFiles" in README.md, which should be "excludeFiles" instead.

Woops, will fix!