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

persistedWindowLayout doesn't restore CWD in split panes #17283

Closed
tunaflsh opened this issue May 17, 2024 · 3 comments
Closed

persistedWindowLayout doesn't restore CWD in split panes #17283

tunaflsh opened this issue May 17, 2024 · 3 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@tunaflsh
Copy link

tunaflsh commented May 17, 2024

Windows Terminal version

1.19.11213.0

Windows build number

10.0.22631.3593

Other Software

No response

Steps to reproduce

  1. Follow the instructions in here.
  2. Run terminal.
  3. Set "firstWindowPreference": "persistedWindowLayout" or in the UI Startup > When Terminal starts to Open windows from a previous session
  4. Create split panes.
  5. Change the working directories in each pane.
  6. Restart terminal.

Expected Behavior

Terminal restores the CWDs in all panes.

Actual Behavior

This only works for the first pane in a tab and for the tabs that do not have split panes.

@tunaflsh tunaflsh added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels May 17, 2024
Copy link

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@zadjii-msft
Copy link
Member

Hmm, this does work for tearout in canary 1.22. I think it does even work generally in canary 1.22.

I wonder if this was a 1.19 backport-specific regression?

@tunaflsh
Copy link
Author

Looks like it's working now. Still the same version. I'm not sure what went wrong for me back then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants