Issues with not case/fragment-normalizing file paths (macOS, Windows)
Problem
In VS Code we deal with resource `URIs` across all layers. In most cases we use `URI.toString()` to decide if a resource is equal to another resource. This assumption is not very good when we talk about file system paths because on macOS and Windows a file path should be considered equal if the paths are identical, even if the casing differs (`/some/path` === `/SOME/path`). Only Linux has a case-sensitive file system where this rule does not apply. This leads to numerous related issues: - [x] Mac: chokidar file watcher does not work if you run with wrong casing (https://github.com/Microsoft/vscode/issues/1426) - [ ] quick open and editors can show the same file multiple times (https://github.com/Microsoft/vscode/issues/17967, https://github.com/Microsoft/vscode/issues/15120, https://github.com/Microsoft/vscode/issues/18718, https://github.com/Microsoft/vscode/issues/6152, https://github.com/Microsoft/vscode/issues/16824, https://github.com/Microsoft/vscode/issues/18684, https://github.com/Microsoft/vscode/issues/19014, https://github.com/Microsoft/vscode/issues/19398)
Unverified for your environment
Select your OS to check compatibility.
1 Fix
Solution: Issues with not case/fragment-normalizing file paths (macOS, Windows)
Any update on this? I keep tripping over it particularly when using the debugger.
Trust Score
5 verifications
- 1
Any update on this? I keep tripping over it particularly when using the debugger
Any update on this? I keep tripping over it particularly when using the debugger.
Validation
Resolved in microsoft/vscode GitHub issue #12448. Community reactions: 11 upvotes.
Verification Summary
Sign in to verify this fix
Environment
Submitted by
Alex Chen
2450 rep