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

new instance behaviour - create a new window - looks strange #16835

New Issue
Open
opened 2026-01-31 05:24:30 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 05:24:30 +00:00
Owner
Copy Link

Originally created by @julie777 on GitHub (Feb 20, 2022).

Windows Terminal version

1.13

Windows build number

10.0.19043.1526

Other Software

No response

Steps to reproduce

BTW, I haven't managed to run wt.exe from the commandline. Either it can't be found or it can be executed.

I have 1.11 installed and have been using it. I have it set to open a new instance in a new window. Each new window has a normal appearance with a title bar, tabs, sidebar, etc.

I installed 1.13 current preview from today and when I ran it it didn't see the settings from 1.11 version. I copied the settings file because that it I I like it. Now I can only create a new instance in a new window. I can't access anything related to WT because my window looks like this

image
I can resize the window, but I can't even move it with the bar across the top.

When I look at the settings.json, I don't see any setting that looks like it controls each instance in a new window.

Expected Behavior

I expected normal windows with tabs and settings just like 1.11

Actual Behavior

I get this

image

Originally created by @julie777 on GitHub (Feb 20, 2022). ### Windows Terminal version 1.13 ### Windows build number 10.0.19043.1526 ### Other Software _No response_ ### Steps to reproduce BTW, I haven't managed to run wt.exe from the commandline. Either it can't be found or it can be executed. I have 1.11 installed and have been using it. I have it set to open a new instance in a new window. Each new window has a normal appearance with a title bar, tabs, sidebar, etc. I installed 1.13 current preview from today and when I ran it it didn't see the settings from 1.11 version. I copied the settings file because that it I I like it. Now I can only create a new instance in a new window. I can't access anything related to WT because my window looks like this ![image](https://user-images.githubusercontent.com/5090005/154868043-1cc9e378-5d1d-4959-8ed5-ca2405088fd8.png) I can resize the window, but I can't even move it with the bar across the top. When I look at the settings.json, I don't see any setting that looks like it controls each instance in a new window. ### Expected Behavior I expected normal windows with tabs and settings just like 1.11 ### Actual Behavior I get this ![image](https://user-images.githubusercontent.com/5090005/154868092-f7c52634-8af8-4798-969c-2f509cd013cd.png)
claunia added the Needs-TriageIssue-BugNeeds-Tag-FixIssue-Docs labels 2026-01-31 05:24:30 +00:00
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 Issue-Docs Needs-Tag-Fix Needs-Triage
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#16835
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?