Open paulober opened 7 months ago
I faced a similar issue where ${userHome}
is recognized as ${workspaceFolder}
. I'm using VSCode Macros and tried to set the following config:
"vscodemacros.macroFilePath": "${userHome}${/}personal${/}vscodemacros${/}macros.js",
However I got the following error message:
'/Users/yoshifumi/personal/foo_workspace/$$personal$vscodemacros$macros.js' not found.```
${userHome}
should be recognized as /Users/yoshifumi
but it was treated as /Users/yoshifumi/personal/foo_workspace/
which is the directory name that I was opening in VS Code.
My environment info is as the following:
Version: 1.88.1 (Universal)
Commit: e170252f762678dec6ca2cc69aba1570769a5d39
Date: 2024-04-10T17:42:52.765Z (6 days ago)
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.4.0
I face a similar issue on Windows where userHome
does not always resolve to env:USERPROFILE
.
See: https://github.com/raspberrypi/pico-vscode/issues/100
Though I guess I should open another ticket really.
Does this issue occur when all extensions are disabled?: Yes/No
Steps to Reproduce:
With an error like: "The terminal process could not be started: The path to the executable shell file "\c:\Users\myuser\myfolder\my.exe" does not exist.
NOTE: The task does work if I use
${env:USERPROFILE}
instead of${userHome}
, as env:USERPROFILE results in a path likeC:\Users\myuser/myfolder/my.exe
to be executed.