-
Notifications
You must be signed in to change notification settings - Fork 88
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
Cannot seem to watch files outside of VS Code workspace directory #418
Comments
In order to watch files outside of the workspace we need to use a @ryanluker we do this in Hope that helps. |
@fquinner Thanks for the ticket! We will have to triage this work against the other in the next milestone. @mattseddon Thanks for responding and providing that input, I bet there wasn't a feature like this when the extension was first built heh 😅 . |
Describe the bug
Watch does not seem to work with files outside of vscode directory. In C / C++, it's common to build projects outside of the workspace to keep the workspace clean and avoid bleeding over the codebase. However when you generate a build there, the watcher does not seem to pick up changes.
Note the initial parsing actually works fine, but it does not refresh.
To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
Updated file should be refreshed.
Desktop (please complete the following information):
Additional context
There generally seems to be some funnies in this area. I'm not a JS guy, but I also noticed that if I run with
Then watch doesn't work either. Again, initial search might work but watch doesn't, it finds
{/workspaces/project-dir}//{lcov.info}
Now I don't know about the GlobPattern in use here from the vscode libs, but if that was a bash glob, that would expand out to literal curly braces unless there was more than one element listed.
The text was updated successfully, but these errors were encountered: