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
I think the problem here is that we tie the cwd to the command being run, not the line range. Changing cwd inside a command like this isn't supported and I'm a little surprised to see it works in iTerm2, but I guess they just went the line route instead of linking it to the full execution. @rzhw have you read somewhere official that this is supposed to work? I think you stumbled upon some largely undefined behavior here.
Type: Bug
From VSCode:
test.py
, and follow the below instructions:OSC 1337:
OSC 7:
Run
python3 test.py
from the inbuilt terminal.Observe that Ctrl/Cmd+Click on
../test.py
opens test.py as expected.Uncomment the commented lines.
Run
python3 test.py
.Observe that Ctrl/Cmd+Click on
../test.py
does not open it. Instead, VSCode spins a while and then pops a file picker.Observe that Ctrl/Cmd+Click on
./test.py
opens test.py as expected.From iTerm2:
Run
python3 test.py
, with the lines either commented out or not.Observe that in both cases, Cmd+Click on
../test.py
and./test.py
open test.py as expected.This seems particularly notable as OSC 1337 is an iTerm2 proprietary escape sequence.
VS Code version: Code 1.95.3 (Universal) (f1a4fb1, 2024-11-13T14:50:04.152Z)
OS version: Darwin arm64 24.2.0
The text was updated successfully, but these errors were encountered: