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

"Open in Terminal" to start in existing terminal instances by default? #18838

New Issue
Closed
opened 2026-01-31 06:25:56 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 06:25:56 +00:00
Owner
Copy Link

Originally created by @vadimkantorov on GitHub (Nov 5, 2022).

Right now, it always spawns a new Terminal instance / window which can be a tad slower than just spawning a new tab in existing instance. This can be compared as opening an HTML file from disk which usually would open it in existing Chrome instances and just open a new tab.

Propose to have a discussion to have the same behavior for Terminal by default (great that an option already exists in the config though! thanks to @237dmitry for pointing it out!)

Originally created by @vadimkantorov on GitHub (Nov 5, 2022). Right now, it always spawns a new Terminal instance / window which can be a tad slower than just spawning a new tab in existing instance. This can be compared as opening an HTML file from disk which usually would open it in existing Chrome instances and just open a new tab. Propose to have a discussion to have the same behavior for Terminal by default (great that an option already exists in the config though! thanks to @237dmitry for pointing it out!)
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 06:25:56 +00:00
claunia commented 2026-01-31 06:25:57 +00:00
Author
Owner
Copy Link

@237dmitry commented on GitHub (Nov 5, 2022):

This option already exists

"windowingBehavior": "useAnyExisting"
@237dmitry commented on GitHub (Nov 5, 2022): This option already [exists](https://learn.microsoft.com/en-us/windows/terminal/customize-settings/startup) ``` "windowingBehavior": "useAnyExisting" ```
claunia commented 2026-01-31 06:25:57 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (Nov 5, 2022):

thank you! great to know! i'll then repurpose this issue to propose to make it default

@vadimkantorov commented on GitHub (Nov 5, 2022): thank you! great to know! i'll then repurpose this issue to propose to make it default
claunia commented 2026-01-31 06:25:57 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 7, 2022):

Thanks for the suggestion! Until we've got tab tear-out sorted out, I've been reluctant to change any defaults to useExisting. That would just make the windows glom together and now you'd be stuck without it being able to tear into it's own window. Trust when I say, when tear-out is ready for stable releases, we'll be changing the default to useExisting.

There's also /dup #7071 for adding a separate setting to control the shell context menu's behavior separate from the globals, but that's quite a bit farther out.

@zadjii-msft commented on GitHub (Nov 7, 2022): Thanks for the suggestion! Until we've got tab tear-out sorted out, I've been reluctant to change any defaults to `useExisting`. That would just make the windows glom together and now you'd be stuck without it being able to tear into it's own window. Trust when I say, when tear-out is ready for stable releases, we'll be changing the default to `useExisting`. There's also /dup #7071 for adding a separate setting to control the shell context menu's behavior separate from the globals, but that's quite a bit farther out.
claunia commented 2026-01-31 06:25:58 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 7, 2022):

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 (Nov 7, 2022): 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 06:25:58 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (Nov 7, 2022):

One nuance, in Chrome it would use last active window for opening disk files, not just "any existing window"

@vadimkantorov commented on GitHub (Nov 7, 2022): One nuance, in Chrome it would use last active window for opening disk files, not just "any existing window"
claunia commented 2026-01-31 06:25:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 7, 2022):

One nuance, in Chrome it would use last active window for opening disk files, not just "any existing window"

That's literally exactly what useExisting does

@zadjii-msft commented on GitHub (Nov 7, 2022): > One nuance, in Chrome it would use last active window for opening disk files, not just "any existing window" That's literally exactly what [`useExisting`](https://learn.microsoft.com/en-us/windows/terminal/customize-settings/startup#new-instance-behavior) does
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 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#18838
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?