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

All tabs cannot be closed #6286

New Issue
Closed
opened 2026-01-31 00:34:41 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 00:34:41 +00:00
Owner
Copy Link

Originally created by @avdain on GitHub (Feb 4, 2020).

Environment

Windows build number: 10.0.18363.628
Windows Terminal version:  0.8.10261.0

Any other software?

Steps to reproduce

  • Create two or more tabs.
  • Reduce the width and the length until it is no longer possible.
  • Press ALT+F4
  • Maximize the width and the length.

Anmerkung 2020-02-04 224705

Expected behavior

The "Do you want to close all tabs" window should remain in the middle.

Actual behavior

The "Do you want to close all tabs" window is displayed in the upper left corner.

Originally created by @avdain on GitHub (Feb 4, 2020). # Environment ``` Windows build number: 10.0.18363.628 Windows Terminal version: 0.8.10261.0 Any other software? ``` # Steps to reproduce - Create two or more tabs. - Reduce the width and the length until it is no longer possible. - Press ALT+F4 - Maximize the width and the length. ![Anmerkung 2020-02-04 224705](https://user-images.githubusercontent.com/47790579/73790182-5aaf5180-47a0-11ea-93a7-b29da067a0ad.png) # Expected behavior The "Do you want to close all tabs" window should remain in the middle. # Actual behavior The "Do you want to close all tabs" window is displayed in the upper left corner.
claunia added the Resolution-Duplicate label 2026-01-31 00:34:41 +00:00
claunia commented 2026-01-31 00:34:42 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 4, 2020):

Dude, same bug as last time you filed it. /dup #2380

@DHowett-MSFT commented on GitHub (Feb 4, 2020): Dude, same bug as last time you filed it. /dup #2380
claunia commented 2026-01-31 00:34:42 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 4, 2020):

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!

@ghost commented on GitHub (Feb 4, 2020): 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!
claunia commented 2026-01-31 00:34:42 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 4, 2020):

Thanks!

@DHowett-MSFT commented on GitHub (Feb 4, 2020): Thanks!
claunia commented 2026-01-31 00:34:43 +00:00
Author
Owner
Copy Link

@avdain commented on GitHub (Feb 4, 2020):

I'm sorry, if I irritated you. 😅

@avdain commented on GitHub (Feb 4, 2020): I'm sorry, if I **irritated** you. 😅
claunia commented 2026-01-31 00:34:43 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Feb 5, 2020):

You haven't irritated me 👍 alles gut

@DHowett-MSFT commented on GitHub (Feb 5, 2020): You haven't irritated me 👍 alles gut
claunia commented 2026-01-31 00:34:43 +00:00
Author
Owner
Copy Link

@avdain commented on GitHub (May 13, 2020):

@DHowett-MSFT
Could you delete this report? I'd like to run a diagnostic on Github and maybe find a weakness.
Thank you very much! :)

@avdain commented on GitHub (May 13, 2020): @DHowett-MSFT Could you delete this report? I'd like to run a diagnostic on Github and maybe find a weakness. **Thank you very much! :)**
claunia commented 2026-01-31 00:34:44 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 13, 2020):

Please do not run a diagnostic on GitHub using our repository.

@DHowett-MSFT commented on GitHub (May 13, 2020): **Please do not run a diagnostic on GitHub using our repository.**
claunia commented 2026-01-31 00:34:44 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 13, 2020):

@AVDAX I'm not concerned about this repository specifically, it is simply inappropriate to use a production repository to test for flaws in other software. 😄

This is best done on a personal repository, where you have control over the reports and when you delete them. It makes for a better vulnerability report if you can reproduce it in isolation!

@DHowett-MSFT commented on GitHub (May 13, 2020): @AVDAX I'm not concerned about this repository specifically, it is simply inappropriate to use a production repository to test for flaws in other software. :smile: This is best done on a personal repository, where you have control over the reports and when you delete them. It makes for a better vulnerability report if you can reproduce it in isolation!
claunia commented 2026-01-31 00:34:44 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 13, 2020):

I appreciate that. Thank you. Unfortunately, by the policy we follow in this repository we don't really delete issue content. I can't complete your request.

@DHowett-MSFT commented on GitHub (May 13, 2020): I appreciate that. Thank you. Unfortunately, by the policy we follow in this repository we don't really delete issue content. I can't complete your request.
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 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#6286
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?