You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Windows path variables like ${relativeFile} or ${workspaceFolder} are return in the platform format. I.E. using backslashes instead of forward slashes, this seems to be recent regression from this issue: #40256
According to this issue forward slashes should be used on all OSes.
Doing this on windows, when the shell is bash is failing:
Trying to find if there is a solution, the following discussion suggest that there should be a command to specify whether to replace slashes or not, but I could not find such a thing: #37438
VS Code version: Code 1.32.3 (a3db5be, 2019-03-14T23:43:35.476Z)
OS version: Windows_NT x64 6.1.7601
Issue Type: Bug
On Windows path variables like ${relativeFile} or ${workspaceFolder} are return in the platform format. I.E. using backslashes instead of forward slashes, this seems to be recent regression from this issue:
#40256
According to this issue forward slashes should be used on all OSes.
Doing this on windows, when the shell is bash is failing:
Will show abc instead of a/b/c.
My bash scripts are not working any more.
Is there a setting to control the behaviour? I could not find one.
Doing this work as the path is in the platform format:
Trying to find if there is a solution, the following discussion suggest that there should be a command to specify whether to replace slashes or not, but I could not find such a thing:
#37438
VS Code version: Code 1.32.3 (a3db5be, 2019-03-14T23:43:35.476Z)
OS version: Windows_NT x64 6.1.7601
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: unavailable_off
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
Extensions (14)
The text was updated successfully, but these errors were encountered: