vscode: Filesystem-related variables report wrong-cased file name if filename case was changed sometimes on
- VS Code Version: Version: 1.56.1
- OS Version: Darwin x64 20.4.0
Steps to Reproduce:
- Use preserve case filesystem. For example, default on MacOS
- Create file (ex. sample.txt)
- Rename it by changing case (ex. Sample.txt)
- Create any task that uses file name variable
- Launch task. Filename is reported in a wrong case.
It breaks some basic flows with gnu make and git.
Does this issue occur when all extensions are disabled?: Yes
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 21 (16 by maintainers)
Commits related to this issue
- Create an async only variable resolver for ext host Fixes #123664 — committed to microsoft/vscode by alexr00 3 years ago
I don’t think it is frequent case, but when it happens result is quite confusing. So decision is up to you.
Many variables are only correct in the extension host (environment variables) and/or require node (install folder, exec folder), so the extension host seems like the logical place to resolve variables. Tasks has moved over to only resolving variables in the extension host because of this.
As far as I know, the only thing that needs to be duplicated in the extension host is the ability to get the orignal URI. Everything else was already there since the ext host debug service already needed to resolve variables in the extension host.