-
Notifications
You must be signed in to change notification settings - Fork 29.5k
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
Mac: file events are not reported when using workspace path with different casing #1426
Milestone
Comments
bpasero
added
the
upstream
Issue identified as 'upstream' component related (exists outside of VS Code)
label
Dec 17, 2015
bpasero
added
electron-update
and removed
upstream
Issue identified as 'upstream' component related (exists outside of VS Code)
labels
Aug 31, 2016
Verify: (Mac only) you can open a folder from the command line into VS Code that uses not the letter casing as it is on disk and you still get file events properly. |
Reopening because it looks like node.js 6.4.0 will revert the nice fs.realpath to go back to the previous JS implementation and behaviour. |
2 tasks
Merging into #12448 |
bpasero
removed
the
*duplicate
Issue identified as a duplicate of another issue(s)
label
Feb 4, 2017
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Interestingly on Mac when opening VS Code on a workspace path that does not match 100% the casing of the workspace as it is on disk, all file events are not working anymore, even though the rest of the program is functional.
Filed: paulmillr/chokidar#418
The text was updated successfully, but these errors were encountered: