starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

"persistedWindowLayout" bug when starting with arguments #20975

New Issue
Closed
opened 2026-01-31 07:29:22 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 07:29:22 +00:00
Owner
Copy Link

Originally created by @alex-jitbit on GitHub (Dec 10, 2023).

Windows Terminal version

1.18.3181.0

Windows build number

10.0.22631.2715

Other Software

No response

Steps to reproduce

I have "firstWindowPreference": "persistedWindowLayout"

Also "new instance behavior" is set to "Attach to most recently used"

  • When starting Windows Terminal from command prompt via wt - all godd
  • When starting by clicking a pinned taskbar icon - all good.
  • When starting via wt -d . to start in current directory and the terminal is already running - all good.
  • When starting via wt -d . when no termonal instance is running yet - it opens in a weird random location.

Expected Behavior

No response

Actual Behavior

  • When starting via wt -d . when no termonal instance is running yet - it opens in a weird random location.
Originally created by @alex-jitbit on GitHub (Dec 10, 2023). ### Windows Terminal version 1.18.3181.0 ### Windows build number 10.0.22631.2715 ### Other Software _No response_ ### Steps to reproduce I have `"firstWindowPreference": "persistedWindowLayout"` Also "new instance behavior" is set to "Attach to most recently used" * When starting Windows Terminal from command prompt via `wt` - all godd * When starting by clicking a pinned taskbar icon - all good. * When starting via `wt -d .` to start in current directory and the terminal is already running - all good. * ***When starting via `wt -d .` when no termonal instance is running yet - it opens in a weird random location.*** ### Expected Behavior _No response_ ### Actual Behavior * ***When starting via `wt -d .` when no termonal instance is running yet - it opens in a weird random location.***
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 07:29:22 +00:00
claunia commented 2026-01-31 07:29:23 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 11, 2023):

What "weird random location", exactly/?

I'd expect, with your settings, that if you're cold starting the terminal with wt -d ., that the Terminal should spawn either {one} or {two or more} tabs:

  • one tab, if you closed out the last tab when closing the terminal previously, so that there was nothing for the terminal to restore from the previous session.
  • two or more, if you just closed the terminal with lots of tabs before. In this case, the terminal should open your previous tabs, and a new tab for the new-tab -d . request.
@zadjii-msft commented on GitHub (Dec 11, 2023): What "weird random location", _exactly_/? I'd expect, with your settings, that if you're cold starting the terminal with `wt -d .`, that the Terminal should spawn either {one} or {two or more} tabs: * **one** tab, if you closed out the last tab when closing the terminal previously, so that there was nothing for the terminal to restore from the previous session. * **two or more**, if you just closed the terminal with lots of tabs before. In this case, the terminal should open your previous tabs, and a _new_ tab for the `new-tab -d .` request.
claunia commented 2026-01-31 07:29:23 +00:00
Author
Owner
Copy Link

@alex-jitbit commented on GitHub (Dec 11, 2023):

What "weird random location", exactly/?

In my case it's at the center with half of the window hidden outside the screen (top edge). Do you need the exact coordinates?

And sometimes when cold-starting with wt -d . it opens TWO separate windows, one in the profile folder (%HOMEPATH%) positioned correctly, and one in the current folder it's instructed to go to (this window is half outside the screen centered)

Have you tried reproducing the problem?

@alex-jitbit commented on GitHub (Dec 11, 2023): > What "weird random location", exactly/? In my case it's at the center with half of the window hidden outside the screen (top edge). Do you need the exact coordinates? And sometimes when cold-starting with `wt -d .` it opens TWO separate windows, one in the profile folder (`%HOMEPATH%`) positioned correctly, and one in the current folder it's instructed to go to (this window is half outside the screen centered) Have you tried reproducing the problem?
claunia commented 2026-01-31 07:29:24 +00:00
Author
Owner
Copy Link

@alex-jitbit commented on GitHub (Dec 11, 2023):

Also saving the current position only works when closing the window by clicking the top-right "X" window icon.

Closing the last open tab should do the same, but nope, after that the new terminal windows starts at a random position again.

But that's another bug...

Do you want me to record a video so you see how broken it is?

@alex-jitbit commented on GitHub (Dec 11, 2023): Also saving the current position only works when closing the window by clicking the top-right "X" window icon. Closing the last open tab should do the same, but nope, after that the new terminal windows starts at a random position again. But that's another bug... Do you want me to record a video so you see how broken it is?
claunia commented 2026-01-31 07:29:24 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Dec 13, 2023):

Okay, we're a little bit psychic debugging here. I think what you're seeing here is a bit of a weird combo of "things that are mostly by design":

  • There's slightly different behavior for persisted layouts, depending on how you close things. If you close the tab, then we take that as a signal of "I don't want this to be persisted". If you close the window with one tab - then we'll persist that tab.
    • when you close the tab (so there's no tab left to persist), the next window will use the position from your settings
  • Depending on what your initialPosition is in the settings, that probably accounts for the "random position" you're seeing. The default value will let the system position the window, which is behavior that seems apparently random

#12633 is the dupe around here for "I want to persist window positions but not really the tabs".

Does that clear things up/?

@zadjii-msft commented on GitHub (Dec 13, 2023): Okay, we're a little bit psychic debugging here. I think what you're seeing here is a bit of a weird combo of "things that are mostly by design": * There's slightly different behavior for persisted layouts, depending on how you close things. If you close the tab, then we take that as a signal of "I don't want this to be persisted". If you close the _window_ with one tab - then we'll persist that tab. * when you close the tab (so there's no tab left to persist), the _next_ window will use the position from your settings * Depending on what your `initialPosition` is in the settings, that probably accounts for the "random position" you're seeing. The default value will let the system position the window, which is behavior that seems apparently random #12633 is the dupe around here for "I want to persist window positions but not really the tabs". Does that clear things up/?
claunia commented 2026-01-31 07:29:24 +00:00
Author
Owner
Copy Link

@alex-jitbit commented on GitHub (Dec 14, 2023):

Nope. This stilll does not explain why the app starts at a different location when I run wt -d .

@alex-jitbit commented on GitHub (Dec 14, 2023): Nope. This stilll does not explain why the app starts at a different location when I run `wt -d .`
claunia commented 2026-01-31 07:29:24 +00:00
Author
Owner
Copy Link

@alex-jitbit commented on GitHub (Dec 14, 2023):

TL;DR

  • press WIN + R, type wt - correct location. Close terminal window
  • press WIN + R, type wt - again correct location. Close terminal window
  • press WIN + R, type wt -d . - I get two separate Terminal windows, one at random location, one at correct
@alex-jitbit commented on GitHub (Dec 14, 2023): TL;DR * press `WIN + R`, type `wt` - correct location. Close terminal window * press `WIN + R`, type `wt` - _again_ correct location. Close terminal window * press `WIN + R`, type `wt -d .` - I get two separate Terminal windows, one at random location, one at correct
claunia commented 2026-01-31 07:29:24 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 10, 2024):

So, yea that does kinda explain it. When you do the wt -d . command (with no open windows), what you get is

  • the last window you closed, at the size and position you closed it at
  • a brand new window, at the random location

It's kinda wacky, but ultimately, it's the same thing that browsers do in the case of a cold launch with edge.exe github.com (or similar)

and ultimately, I think what you're expecting here is the behavior that we'd add with /dup #12633.

@zadjii-msft commented on GitHub (Jan 10, 2024): So, yea that does kinda explain it. When you do the `wt -d .` command (with no open windows), what you get is * the last window you closed, at the size and position you closed it at * a brand new window, at the random location It's kinda wacky, but ultimately, it's the same thing that browsers do in the case of a cold launch with `edge.exe github.com` (or similar) and ultimately, I think what you're expecting here is the behavior that we'd add with /dup #12633.
claunia commented 2026-01-31 07:29:25 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Jan 10, 2024):

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[bot] commented on GitHub (Jan 10, 2024): 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! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20975
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?