starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 08:24:54 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Docking/window position should be preserved when closing and opening Terminal #1900

New Issue
Closed
opened 2026-01-30 22:41:33 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 22:41:33 +00:00
Owner
Copy Link

Originally created by @UweKeim on GitHub (Jun 22, 2019).

Steps to reproduce:

  1. Start Terminal.
  2. Press Win+Left key to dock Terminal window to the left half of my monitor. The Terminal window starts at (0|0) left top position.
  3. Exit Terminal.
  4. Start Terminal.

Actual results:

After step 4, the Terminal window starts at some probably random (X|Y) position.

Now I have to repeat above step 2:

  1. Press Win+Left key to dock the Terminal window to the left half of my monitor.

This is really annoying.

Expected results:

The Terminal window should start pixel perfect at the very same position where I closed it the last time. No offset or anything. Just start with the same size and the same position. No matter whether I manually resized the window or whether being docked before.

Google Chrome does this very well, Microsoft Edge based on Chromium does this very well, too, same does e.g. Visual Studio Code. I hope Terminal can do better, too.

Additional information:

I've described a similar issue some years back over at Super User, together with some UI mockups.

Originally created by @UweKeim on GitHub (Jun 22, 2019). **Steps to reproduce:** 1. Start Terminal. 1. Press <kbd>Win</kbd>+<kbd>Left</kbd> key to dock Terminal window to the left half of my monitor. The Terminal window starts at (0|0) left top position. 1. Exit Terminal. 1. Start Terminal. **Actual results:** After step 4, the Terminal window starts at some probably random (X|Y) position. Now I have to repeat above step 2: 1. Press <kbd>Win</kbd>+<kbd>Left</kbd> key to dock the Terminal window to the left half of my monitor. This is really annoying. **Expected results:** The Terminal window should start pixel perfect at the very same position where I closed it the last time. No offset or anything. Just start with the same **size** and the same **position**. No matter whether I manually resized the window or whether being docked before. Google Chrome does this very well, Microsoft Edge based on Chromium does this very well, too, same does e.g. Visual Studio Code. I hope Terminal can do better, too. **Additional information:** I've described a [similar issue some years back over at Super User](https://superuser.com/q/659585/11720), together with some UI mockups.
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-FixResolution-Duplicate labels 2026-01-30 22:41:33 +00:00
claunia commented 2026-01-30 22:41:34 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 22, 2019):

Duplicate of #1387, #1043

@DHowett-MSFT commented on GitHub (Jun 22, 2019): Duplicate of #1387, #1043
claunia commented 2026-01-30 22:41:34 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 22, 2019):

Also, just pitching in: I disagree. I might open multiple windows and I absolutely don’t want them all spawning over top of each other.

@DHowett-MSFT commented on GitHub (Jun 22, 2019): Also, just pitching in: I disagree. I might open multiple windows and I absolutely don’t want them all spawning over top of each other.
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-Feature Needs-Tag-Fix Needs-Triage 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#1900
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?