vscode: terminal.integrated.splitCwd="inherited" is not working on mac/linux

Issue Type: Bug

This seems to have broken recently.

  1. Open an integrated terminal
  2. Switch to another directory
  3. Split the terminal Expected: New split terminal opens in the directory switched to at #2 Actual: It opens in the original directory #1

terminal.integrated.splitCwd is at default (=inherited). Explicitly added in JSON. No effect

Mac OS BigSur.

VS Code version: Code 1.55.2 (Universal) (3c4e3df9e89829dce27b7b5c24508306b151f30d, 2021-04-13T09:36:32.643Z) OS version: Darwin x64 20.3.0

System Info
Item Value
CPUs Intel® Core™ i7-9750H CPU @ 2.60GHz (12 x 2600)
GPU Status 2d_canvas: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
webgl: enabled
webgl2: enabled
Load (avg) 2, 2, 2
Memory (System) 16.00GB (0.12GB free)
Process Argv –crash-reporter-id 601e5aac-44e5-4054-a502-909a84d91473
Screen Reader no
VM 0%
Extensions (30)
Extension Author (truncated) Version
git-diff-and-merge-tool dav 1.0.4
vscode-eslint dba 2.1.20
xml Dot 2.5.1
gitlens eam 11.4.1
filter-lines ear 0.2.0
vscode-open-in-application fab 1.0.6
code-runner for 0.11.3
fontsize-shortcuts fos 1.5.0
gc-excelviewer Gra 3.0.41
beautify Hoo 1.5.0
rest-client hum 0.24.5
vscode-edit-csv jan 0.5.8
json2csv kha 0.0.1
rainbow-csv mec 1.8.1
git-graph mhu 1.30.0
remote-ssh ms- 0.65.4
remote-ssh-edit ms- 0.65.4
remote-wsl ms- 0.54.6
vscode-remote-extensionpack ms- 0.20.0
debugger-for-chrome msj 4.12.12
material-icon-theme PKi 4.6.0
vscode-data-preview Ran 2.3.0
vscode-sort-json ric 1.20.0
LiveServer rit 5.6.1
partial-diff ryu 1.4.3
now-vscode Ser 1.5.0
html-preview-vscode tht 0.2.5
todo-list Tza 1.6.0
vscodeintellicode Vis 1.2.12
better-align wwm 1.1.6

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspyt653:30270858
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry244:30276681
pythonvsdeb440:30248342
pythonvsded773:30248341
pythonvspyt875:30259475
pythonvspyt639:30281910
pythontb:30283811
openwslfolder:30282073
vspre833cf:30267465
pythonptprofiler:30281270
vshan820:30276952
vscoreces:30290705
pythondataviewer:30285071
vscus158:30286553

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 5
  • Comments: 25 (8 by maintainers)

Most upvoted comments

Split command/keybinding works, the tab button doesn’t. This is probably splitInstance not supporting it properly

Following-up that with 1.59.0 (July Update) on MacOS, the split command/keybinding and context menu split workaround no longer respects terminal.integrated.splitCwd as workspaceRoot when choosing from the “Select current working directory for new terminal” palette drop-down option. This happens with either terminal.integrated.tabs.enabled as true or false or whether terminal.integrated.defaultLocation is view or editor.

Now Split always starts in the working directory the initial terminal was opened in.

Split command/keybinding works, the tab button doesn’t. This is probably splitInstance not supporting it properly

How do i get this fix immediately, at-least on insiders?

For me on top of that - the default keyboard shortcut for splitting terminals stopped working.