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

Let wt.exe test by window name if the corresponding window is already opened #16846

New Issue
Closed
opened 2026-01-31 05:24:55 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 05:24:55 +00:00
Owner
Copy Link

Originally created by @edshamis on GitHub (Feb 22, 2022).

Description of the new feature/enhancement

My use case: I want to keep single headless window and single tab with a favourite text editor always opened.
Now I can run wt -Mf -w vv -p Ubuntu wsl zsh -i -c vim and get this window.
But how do I check if the window is already running and run wt -w vv ft to just open it again instead of creating a new tab?

Originally created by @edshamis on GitHub (Feb 22, 2022). # Description of the new feature/enhancement My use case: I want to keep single headless window and single tab with a favourite text editor always opened. Now I can run `wt -Mf -w vv -p Ubuntu wsl zsh -i -c vim` and get this window. But how do I check if the window is already running and run `wt -w vv ft` to just open it again instead of creating a new tab?
claunia added the Issue-FeatureResolution-DuplicateArea-Windowing labels 2026-01-31 05:24:55 +00:00
claunia commented 2026-01-31 05:24:56 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 23, 2022):

Ah, the key operative phrase here is

But how do I check if the window is already running

That's a good question. I suppose there isn't a great way to do that today.

  • #12135 might be a potential solution for this. For that, you'd create a "vv" profile for vim, and then you'd be able to run something like wt summon --profile vv, which would find the "nearest" terminal running the vv profile and activate it.
  • Otherwise, more complicated-ly, maybe some version of #9992, where you set the default profile/commandline for the "vv" named window to wsl zsh -i -c vim. Then, wt -w vv ft -t 0 would always work to:
    1. create the window if it doesn't exist yet (which would launch the default profile for that window, which would be vim)
    2. focus that window's first tab

Either of those sound like they'd work for you?

@zadjii-msft commented on GitHub (Feb 23, 2022): Ah, the key operative phrase here is > But how do I check if the window is already running That's a good question. I suppose there isn't a great way to do that today. * #12135 might be a potential solution for this. For that, you'd create a "vv" profile for vim, and then you'd be able to run something like `wt summon --profile vv`, which would find the "nearest" terminal running the vv profile and activate it. * Otherwise, more complicated-ly, maybe some version of #9992, where you set the default profile/commandline for the "vv" named window to `wsl zsh -i -c vim`. Then, `wt -w vv ft -t 0` would always work to: 1. create the window if it doesn't exist yet (which would launch the default profile for that window, which would be vim) 2. focus that window's first tab Either of those sound like they'd work for you?
claunia commented 2026-01-31 05:24:56 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 27, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Feb 27, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 05:24:57 +00:00
Author
Owner
Copy Link

@edshamis commented on GitHub (Feb 28, 2022):

Thanks a lot! I'll check it later)) Peace!

@edshamis commented on GitHub (Feb 28, 2022): Thanks a lot! I'll check it later)) Peace!
claunia commented 2026-01-31 05:24:57 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 28, 2022):

Okay thanks!

/dup #12135
/dup #9992

@zadjii-msft commented on GitHub (Feb 28, 2022): Okay thanks! /dup #12135 /dup #9992
claunia commented 2026-01-31 05:24:57 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 28, 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 (Feb 28, 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!
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 Area-Windowing 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#16846
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?