Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split Cwd setting is not respected #120442

Closed
ebeloded opened this issue Apr 2, 2021 · 2 comments
Closed

Split Cwd setting is not respected #120442

ebeloded opened this issue Apr 2, 2021 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) terminal General terminal issues that don't fall under another label
Milestone

Comments

@ebeloded
Copy link

ebeloded commented Apr 2, 2021

In the last two releases of VSCode, the Split Cwd setting has not been respected. When a terminal is split, the working directory resets to workspace root, instead of being inherited from the parent terminal, even if the setting is

"terminal.integrated.splitCwd": "inherited"

I wasn't aware of this setting, being used to splitting terminal and remaining in the same directory. But at some point it stopped working.

I also confirmed this behavior in the most recent Insiders build, without any extensions installed.

Env Info

Version: 1.55.0
Commit: c185983a683d14c396952dd432459097bc7f757f
Date: 2021-03-30T16:01:05.981Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Darwin x64 20.3.0
@meganrogge meganrogge added bug Issue identified by VS Code Team member as probable bug terminal General terminal issues that don't fall under another label labels Apr 14, 2021
@meganrogge meganrogge added this to the Backlog milestone Apr 14, 2021
@matthias-ccri
Copy link

This is also happening to me. With a monorepo in a subfolder, It's annoying when you're running a process and you want to run another command. You used to be able to split the terminal and have it keep the current working directory, but now you have to cd up to it again.

The recent Terminal Tabs update seemed to introduce it.

Why haven't more people seen this issue? I searched for existing tickets but I didn't notice this one, but when I was typing mine up, this one popped up in "similar issues". @ebeloded can you put "Terminal" in the ticket title to try to get more visibility?

Version: 1.57.1
Commit: 507ce72a4466fbb27b715c3722558bb15afa9f48
Date: 2021-06-17T13:26:56.255Z
Electron: 12.0.7
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Linux x64 4.15.0-147-generic

@Tyriar
Copy link
Member

Tyriar commented Jul 8, 2021

/duplicate #121705

@Tyriar Tyriar closed this as completed Jul 8, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Aug 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) terminal General terminal issues that don't fall under another label
Projects
None yet
Development

No branches or pull requests

5 participants
@Tyriar @ebeloded @matthias-ccri @meganrogge and others