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

Showing terminal after it being open for long periods of time (over 3 days straight) will prevent it from ever being maximized until terminated. #12623

New Issue
Closed
opened 2026-01-31 03:20:28 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 03:20:28 +00:00
Owner
Copy Link

Originally created by @AraHaan on GitHub (Feb 17, 2021).

Environment

Windows build number: Windows 10 Insider Preview Dev Build: 21301.rs_prerelease.210123-1646 (from the label at the top of the taskbar).
Windows Terminal version (if applicable): I use the latest Terminal Preview Version from the Microsoft Store.

Any other software?
I have Visual Studio 2019, and many other unrelated software installed due to Visual Studio installing it, SQL Express, other Microsoft Store applications, and various versions of the .NET Core SDK / .NET 5 & 6 SDKs.

Steps to reproduce

I have currently no idea what triggers it, it happens at random when having the terminal with 3 Powershell Preview tabs (Powershell Preview from the Microsoft Store that is) which has the directory set and is running an git gui, 1 tab for deleting branches that no longer have a tracking ref on the remote (since my git is set to delete refs if the remote no longer has the branch when pulling), one tab for pulling, commiting, making branches, etc, and last tab to use .NET SDK commands (dotnet build, dotnet restore, dotnet pack, etc).

Expected behavior

The terminal with all the tabs being able to maximize even after being open for those long periods of time.

Actual behavior

Even when I click on the terminal entry on the taskbar it will refuse the maximize and show the terminal with all 3 tabs.

Originally created by @AraHaan on GitHub (Feb 17, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Windows 10 Insider Preview Dev Build: 21301.rs_prerelease.210123-1646 (from the label at the top of the taskbar). Windows Terminal version (if applicable): I use the latest Terminal Preview Version from the Microsoft Store. Any other software? I have Visual Studio 2019, and many other unrelated software installed due to Visual Studio installing it, SQL Express, other Microsoft Store applications, and various versions of the .NET Core SDK / .NET 5 & 6 SDKs. ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> I have currently no idea what triggers it, it happens at random when having the terminal with 3 Powershell Preview tabs (Powershell Preview from the Microsoft Store that is) which has the directory set and is running an git gui, 1 tab for deleting branches that no longer have a tracking ref on the remote (since my git is set to delete refs if the remote no longer has the branch when pulling), one tab for pulling, commiting, making branches, etc, and last tab to use .NET SDK commands (``dotnet build``, ``dotnet restore``, ``dotnet pack``, etc). # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> The terminal with all the tabs being able to maximize even after being open for those long periods of time. # Actual behavior <!-- What's actually happening? --> Even when I click on the terminal entry on the taskbar it will refuse the maximize and show the terminal with all 3 tabs.
claunia commented 2026-01-31 03:20:30 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 17, 2021):

Wait so I wanna be sure I understand the issue correctly - You currently have the Terminal window minimized, but you can't restore the window by clicking on it in the taskbar?

  • Does activating the window with alt+tab work?
  • What about activating the window with the task veiw, win+tab?
@zadjii-msft commented on GitHub (Feb 17, 2021): Wait so I wanna be sure I understand the issue correctly - You currently have the Terminal window minimized, but you can't restore the window by clicking on it in the taskbar? * Does activating the window with <kbd>alt+tab</kbd> work? * What about activating the window with the task veiw, <kbd>win+tab</kbd>?
claunia commented 2026-01-31 03:20:30 +00:00
Author
Owner
Copy Link

@AraHaan commented on GitHub (Feb 17, 2021):

It seems it does not work with both of those, also I somehow managed to get Discord to do the same thing as well too. 😂

@AraHaan commented on GitHub (Feb 17, 2021): It seems it does not work with both of those, also I somehow managed to get Discord to do the same thing as well too. 😂
claunia commented 2026-01-31 03:20:30 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 17, 2021):

If it's happening to the Discord app as well, then it's probably safe to assume that this isn't an issue unique to the Terminal, yea?

This is gonna sound weird, but if you alt+tab to the Terminal window, then alt+tab again, is the Terminal window the first in the alt-tab order?

You could maybe try alt-tabbing to the window, then hit alt+space, m, then tap any arrow key, then move the mouse. My theory is that somehow the Terminal window got yeeted into space, and it's restoring to a position that's not on any of the monitors. That "alt+space, m" trick will allow you to start moving the window regardless of where it is on the screen. Maybe that'll summon the window again?

@zadjii-msft commented on GitHub (Feb 17, 2021): If it's happening to the Discord app as well, then it's probably safe to assume that this isn't an issue unique to the Terminal, yea? This is gonna sound weird, but if you alt+tab to the Terminal window, then alt+tab again, is the Terminal window the first in the alt-tab order? You could maybe try alt-tabbing to the window, then hit <kbd>alt+space</kbd>, <kbd>m</kbd>, then tap any arrow key, then move the mouse. My theory is that somehow the Terminal window got yeeted into space, and it's restoring to a position that's not on any of the monitors. That "alt+space, m" trick will allow you to start moving the window regardless of where it is on the screen. Maybe that'll summon the window again?
claunia commented 2026-01-31 03:20:30 +00:00
Author
Owner
Copy Link

@AraHaan commented on GitHub (Feb 17, 2021):

yep alt tab twice did expose it first, and then it was yeeted into space.

🤔 that alt+space, m was new to me though I did not know I could alt+space, m to force move a window even if I cannot click on the title bar of the window itself due to it being yeeted to space. Something new that I learned that I could have used on yeeted windows that could have saved me from having to terminate them and reopen them and hopefully not be yeeted.

@AraHaan commented on GitHub (Feb 17, 2021): yep alt tab twice did expose it first, and then it was yeeted into space. 🤔 that alt+space, m was new to me though I did not know I could alt+space, m to force move a window even if I cannot click on the title bar of the window itself due to it being yeeted to space. Something new that I learned that I could have used on yeeted windows that could have saved me from having to terminate them and reopen them and hopefully not be yeeted.
claunia commented 2026-01-31 03:20:30 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 17, 2021):

Welp, at least that explains it. Glad you got this figured out!

@zadjii-msft commented on GitHub (Feb 17, 2021): Welp, at least that explains it. Glad you got this figured out!
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-Question Needs-Attention Needs-Tag-Fix Needs-Triage Resolution-Answered
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#12623
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?