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

Tab titles (specified via command line arguments) are lost #15316

Closed
reaching-for-libra opened this issue May 9, 2023 · 3 comments
Closed

Tab titles (specified via command line arguments) are lost #15316

reaching-for-libra opened this issue May 9, 2023 · 3 comments
Assignees
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@reaching-for-libra
Copy link

Windows Terminal version

1.17.1023

Windows build number

10.0.19044.0

Other Software

No response

Steps to reproduce

Not entirely sure which actions are relevant, and i have a hard time reproducing with explicit actions, so i'll outline my flow

  • Plug laptop into dock
  • Start windows terminal (pwsh profile). (suppressApplicationTitle is set to "true" in the settings.json file)
  • Launch new tab(s) in a new window, specifying titles for tabs

wt.exe -w 2 --title 6000 -p cmd cmd /c "cd \"c:\projectdirectory\" &\"C:\Program Files\dotnet\dotnet.exe\" run --urls \"http://*:6000\" &pause"

  • Some time later, unplug laptop from dock and close
  • Take laptop elsewhere (some amount of commute time), and plug into new dock.
  • Most likely, wait until the following day before opening the laptop again

Expected Behavior

Tab titles should be retained

Actual Behavior

Tab titles revert to the command. In the example, tab title changes to "cmd"

@reaching-for-libra reaching-for-libra 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 9, 2023
@zadjii-msft
Copy link
Member

note to self: this isn't just the "language change causes runtime settings to be lost" issue. I think there's some other issue floating around for "a settings update causes commandline settings to be lost". Probably something about NewTerminalArgs.

I'll need to go dedupe later.

@zadjii-msft
Copy link
Member

I'm pretty sure this is ultimately #5047. Really hard to tell just by reading, but that's my read of the situation. Thanks for a more concrete example!

/dup #5047

@microsoft-github-policy-service
Copy link
Contributor

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels May 10, 2023
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. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants