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

Disappering window after curl command #18531

New Issue
Closed
opened 2026-01-31 06:16:55 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 06:16:55 +00:00
Owner
Copy Link

Originally created by @lbaiao on GitHub (Sep 22, 2022).

Windows Terminal version

1.14.2282

Windows build number

10.0.22000.0

Other Software

PowerShell 7.2.6

Steps to reproduce

Run wt curl microsoft.com && ping microsoft.com -t in Windows Terminal in a PowerShell shell.

Expected Behavior

The Terminal should open a new Terminal window. Following, in the newly open window, it should run the curl command. After the curl command finishes, it should run the ping command, all in the same window.

Actual Behavior

The Terminal opens a new window and runs the curl command in this newly open window. After the curl command completion, it closes the new window and runs the ping command in the original window, where the whole command was input originally.

Originally created by @lbaiao on GitHub (Sep 22, 2022). ### Windows Terminal version 1.14.2282 ### Windows build number 10.0.22000.0 ### Other Software PowerShell 7.2.6 ### Steps to reproduce Run `wt curl microsoft.com && ping microsoft.com -t` in Windows Terminal in a PowerShell shell. ### Expected Behavior The Terminal should open a new Terminal window. Following, in the newly open window, it should run the `curl` command. After the `curl` command finishes, it should run the `ping` command, all in the same window. ### Actual Behavior The Terminal opens a new window and runs the `curl` command in this newly open window. After the `curl` command completion, it closes the new window and runs the `ping` command in the original window, where the whole command was input originally.
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 06:16:55 +00:00
claunia commented 2026-01-31 06:16:56 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Sep 22, 2022):

&& has a special meaning to PowerShell and separates two commands. It's like writing ; in C-like languages. For instance try running this:

echo 1 && sleep 1 && echo 2

Furthermore, wt expects a command-line as the argument, which means that the first argument is interpreted as an executable name and all remaining arguments are passed to that executable. curl doesn't know what ping is. You have to launch a shell first, like pwsh, to make such concepts work.

So to make your command work try running this:

wt pwsh -c "curl microsoft.com && ping microsoft.com -t"

It instructs wt to spawn the executable named pwsh and passes it 2 parameters: -c which is short for -Command and the long string is the command argument. It tells pwsh to run the string as if it were a command.

@lhecker commented on GitHub (Sep 22, 2022): `&&` has a special meaning to PowerShell and separates two commands. It's like writing `;` in C-like languages. For instance try running this: ```pwsh echo 1 && sleep 1 && echo 2 ``` Furthermore, `wt` expects a command-line as the argument, which means that the first argument is interpreted as an executable name and all remaining arguments are passed to that executable. `curl` doesn't know what `ping` is. You have to launch a shell first, like `pwsh`, to make such concepts work. So to make your command work try running this: ```pwsh wt pwsh -c "curl microsoft.com && ping microsoft.com -t" ``` It instructs `wt` to spawn the executable named `pwsh` and passes it 2 parameters: `-c` which is short for `-Command` and the long string is the command argument. It tells `pwsh` to run the string as if it were a command.
claunia commented 2026-01-31 06:16:56 +00:00
Author
Owner
Copy Link

@lbaiao commented on GitHub (Sep 23, 2022):

Thanks a lot. Sorry for raising this issue, since it was not a bug after all. I read the documentation here, but I could not find this pwsh -c command in there. I thought it was a bit confusing. Maybe this documentation could be improved.

Also, thanks for the PowerShell explanation.

@lbaiao commented on GitHub (Sep 23, 2022): Thanks a lot. Sorry for raising this issue, since it was not a bug after all. I read the documentation [here](https://learn.microsoft.com/en-us/windows/terminal/command-line-arguments?tabs=powershell), but I could not find this `pwsh -c` command in there. I thought it was a bit confusing. Maybe this documentation could be improved. Also, thanks for the PowerShell explanation.
claunia commented 2026-01-31 06:16:56 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Sep 23, 2022):

That's not a problem. I'm glad I could help!

@lhecker commented on GitHub (Sep 23, 2022): That's not a problem. I'm glad I could help!
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-Question Needs-Tag-Fix Resolution-Answered
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#18531
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?