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

Allow wt.exe to close tabs via command line argument #20277

New Issue
Closed
opened 2026-01-31 07:08:48 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 07:08:48 +00:00
Owner
Copy Link

Originally created by @bzm3r on GitHub (Jul 23, 2023).

Description of the new feature/enhancement

Currently, we can open new tabs using wt newtab.

However, we cannot close existing tabs via the command line.

Can such a command line argument be provided?

Originally created by @bzm3r on GitHub (Jul 23, 2023). # Description of the new feature/enhancement Currently, we can open new tabs using `wt newtab`. However, we cannot close existing tabs via the command line. Can such a command line argument be provided?
claunia commented 2026-01-31 07:08:50 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jul 26, 2023):

Hi @bzm3r. We're hesitant to add this kind of functionality because it could be used maliciously. Curious though, why do you want this feature?

@carlos-zamora commented on GitHub (Jul 26, 2023): Hi @bzm3r. We're hesitant to add this kind of functionality because it could be used maliciously. Curious though, why do you want this feature?
claunia commented 2026-01-31 07:08:50 +00:00
Author
Owner
Copy Link

@bzm3r commented on GitHub (Jul 26, 2023):

Hi @bzm3r. We're hesitant to add this kind of functionality because it could be used maliciously. Curious though, why do you want this feature?

Just because it's cleaner than killing a window, and re-opening it? I'm not sure I understand why this is a maliciousness issue, when it is possible to kill a terminal window quite easily, and/or any shells that are running in tabs (e.g. PowerShell's Stop-Process)?

@bzm3r commented on GitHub (Jul 26, 2023): > Hi @bzm3r. We're hesitant to add this kind of functionality because it could be used maliciously. Curious though, why do you want this feature? Just because it's cleaner than killing a window, and re-opening it? I'm not sure I understand why this is a maliciousness issue, when it is possible to kill a terminal window quite easily, and/or any shells that are running in tabs (e.g. PowerShell's `Stop-Process`)?
claunia commented 2026-01-31 07:08:50 +00:00
Author
Owner
Copy Link

@stianhoiland commented on GitHub (Apr 14, 2025):

I'm requesting this issue reopened. I'm wanting this functionality as well: close pane, close tab, and close window command line arguments.

My use case is tight integration between the terminal emulator and the shell. I use Windows Terminal sort of like how people use tmux. It is great to be able to open new panes with custom commands from within terminal apps. Without close commands, I'm limited in the kinds of interactions I can set up. For example, I cannot create a new Windows Terminal pane from within my editor to show some information (say compiler output) and then close the pane again with another command/hotkey from within my editor.

Here are some straightforward shell functions I use to control my workspace:

new() {
  if [[ "$#" -eq 0 ]]
  then
    wt -p "$WT_PROFILE_ID" "$(which busybox)" sh -lsc "cd '$PWD'"
  else
    wt -p "$WT_PROFILE_ID" "$(which busybox)" sh -lsc "cd '$PWD' && $*"
  fi
}
tab() {
  if [[ "$#" -eq 0 ]]
  then
    wt -w last nt -p "$WT_PROFILE_ID" "$(which busybox)" sh -lsc "cd '$PWD'"
  else
    wt -w last nt -p "$WT_PROFILE_ID" "$(which busybox)" sh -lsc "cd '$PWD' && $*"
  fi
}
# TODO Redo these to take a "down, up, left, right" arg
split() { # stacks
  if [[ "$#" -eq 0 ]]
  then
    wt -w last sp -p "$WT_PROFILE_ID" "$(which busybox)" sh -lsc "cd '$PWD'"
  else
    wt -w last sp -p "$WT_PROFILE_ID" "$(which busybox)" sh -lsc "cd '$PWD' && $*"
  fi
}
splitdown() {
  if [[ "$#" -eq 0 ]]
  then
    wt -w last sp -p "$WT_PROFILE_ID" -H "$(which busybox)" sh -lsc "cd '$PWD'"
  else
    wt -w last sp -p "$WT_PROFILE_ID" -H "$(which busybox)" sh -lsc "cd '$PWD' && $*"
  fi
}
splitup() {
  if [[ "$#" -eq 0 ]]
  then
    wt -w last sp -p "$WT_PROFILE_ID" -H "$(which busybox)" sh -lsc "cd '$PWD'" && wt -w last swap-pane previousInOrder
  else
    wt -w last sp -p "$WT_PROFILE_ID" -H "$(which busybox)" sh -lsc "cd '$PWD' && $*" && wt -w last swap-pane previousInOrder
  fi
}
splitfocus() {
  if [[ "$#" -eq 0 ]]
  then
    wt -w last sp -p "$WT_PROFILE_ID" -H --size 0.3 "$(which busybox)" sh -sc "source ~/.profile && cd '$(realpath "$PWD")'" && wt -w last mf previousInOrder
  else
    wt -w last sp -p "$WT_PROFILE_ID" -H --size 0.3 "$(which busybox)" sh -sc "source ~/.profile && cd '$(realpath "$PWD")' && $*" && wt -w last mf previousInOrder
  fi
}

At the moment I'm experimenting with the following kludge to provide at least some semblance of this functionality, and from which you can glean @bzm3r's argument that if you want to tamper with a process launched by the terminal, lacking a convenient and hygienic way of doing so isn't gonna stop a malicious actor. It leaves the pane dangling (and the process dead) according to the "Profile termination behavior" setting.

wt -w last sp -p "$WT_PROFILE_ID" "$(which busybox)" sh -lsc "echo \$$ > '$TMP/split.$$.pid' && cd '$PWD'" && sleep 0.2 && kill $(cat "$TMP/split.$$.pid") # sleep 0.14 will sometimes be too quick
@stianhoiland commented on GitHub (Apr 14, 2025): I'm requesting this issue reopened. I'm wanting this functionality as well: close pane, close tab, and close window command line arguments. My use case is tight integration between the terminal emulator and the shell. I use Windows Terminal sort of like how people use tmux. It is great to be able to open new panes with custom commands from within terminal apps. Without close commands, I'm limited in the kinds of interactions I can set up. For example, I cannot create a new Windows Terminal pane from within my editor to show some information (say compiler output) and then close the pane again with another command/hotkey from within my editor. Here are some straightforward shell functions I use to control my workspace: ```sh new() { if [[ "$#" -eq 0 ]] then wt -p "$WT_PROFILE_ID" "$(which busybox)" sh -lsc "cd '$PWD'" else wt -p "$WT_PROFILE_ID" "$(which busybox)" sh -lsc "cd '$PWD' && $*" fi } tab() { if [[ "$#" -eq 0 ]] then wt -w last nt -p "$WT_PROFILE_ID" "$(which busybox)" sh -lsc "cd '$PWD'" else wt -w last nt -p "$WT_PROFILE_ID" "$(which busybox)" sh -lsc "cd '$PWD' && $*" fi } # TODO Redo these to take a "down, up, left, right" arg split() { # stacks if [[ "$#" -eq 0 ]] then wt -w last sp -p "$WT_PROFILE_ID" "$(which busybox)" sh -lsc "cd '$PWD'" else wt -w last sp -p "$WT_PROFILE_ID" "$(which busybox)" sh -lsc "cd '$PWD' && $*" fi } splitdown() { if [[ "$#" -eq 0 ]] then wt -w last sp -p "$WT_PROFILE_ID" -H "$(which busybox)" sh -lsc "cd '$PWD'" else wt -w last sp -p "$WT_PROFILE_ID" -H "$(which busybox)" sh -lsc "cd '$PWD' && $*" fi } splitup() { if [[ "$#" -eq 0 ]] then wt -w last sp -p "$WT_PROFILE_ID" -H "$(which busybox)" sh -lsc "cd '$PWD'" && wt -w last swap-pane previousInOrder else wt -w last sp -p "$WT_PROFILE_ID" -H "$(which busybox)" sh -lsc "cd '$PWD' && $*" && wt -w last swap-pane previousInOrder fi } splitfocus() { if [[ "$#" -eq 0 ]] then wt -w last sp -p "$WT_PROFILE_ID" -H --size 0.3 "$(which busybox)" sh -sc "source ~/.profile && cd '$(realpath "$PWD")'" && wt -w last mf previousInOrder else wt -w last sp -p "$WT_PROFILE_ID" -H --size 0.3 "$(which busybox)" sh -sc "source ~/.profile && cd '$(realpath "$PWD")' && $*" && wt -w last mf previousInOrder fi } ``` At the moment I'm experimenting with the following kludge to provide at least some semblance of this functionality, and from which you can glean @bzm3r's argument that if you want to tamper with a process launched by the terminal, lacking a convenient and hygienic way of doing so isn't gonna stop a malicious actor. It leaves the pane dangling (and the process dead) according to the "Profile termination behavior" setting. ```sh wt -w last sp -p "$WT_PROFILE_ID" "$(which busybox)" sh -lsc "echo \$$ > '$TMP/split.$$.pid' && cd '$PWD'" && sleep 0.2 && kill $(cat "$TMP/split.$$.pid") # sleep 0.14 will sometimes be too quick ```
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-Commandline Issue-Task Needs-Discussion Needs-Triage Product-Terminal
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#20277
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?