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

Weird parsing rule for cmd command #15427

New Issue
Open
opened 2026-01-31 04:38:22 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 04:38:22 +00:00
Owner
Copy Link

Originally created by @SainoNamkho on GitHub (Oct 4, 2021).

Windows Terminal version (or Windows build number)

10.0.19042.0, 1.4.3243.0

Other Software

No response

Steps to reproduce

C:\>"cmd /c" echo 1
1

C:\>"cmd.exe /c" echo 1
The system cannot find the path specified.

C:\>"cmd /c"echo 1
 1

C:\>cmd /c"echo 1
1


C:\>c"md /c"echo 1"
 1

note that there's a space in front of 1 in the "cmd /c"echo 1 case

Expected Behavior

When I run it in mintty.exe, command is parsed properly

$ cmd
Microsoft Windows [Version 10.0.19042.685]
(c) 2020 Microsoft Corporation. All rights reserved.

D:\>cmd /c echo 1
cmd /c echo 1
1

D:\>"cmd /c"echo 1
"cmd /c"echo 1
The filename, directory name, or volume label syntax is incorrect.

D:\>"cmd /c" echo 1
"cmd /c" echo 1
The filename, directory name, or volume label syntax is incorrect.

And win+r run dialog box errs in `Windows cannot find 'cmd /c'. Make sure you typed the name correctly, and then try again."

Actual Behavior

It seems this command is parsed specially. When I copied a program named cmd.exe which prints command-line arguments to the current directory, it's not called in this case.

C:\>cmd /c echo 1
...calling my program...
arg0 is <cmd>
arg1 is </c>
arg2 is <echo>
arg3 is <1>

C:\>"cmd /c" echo 1
1
Originally created by @SainoNamkho on GitHub (Oct 4, 2021). ### Windows Terminal version (or Windows build number) 10.0.19042.0, 1.4.3243.0 ### Other Software _No response_ ### Steps to reproduce ```cmd C:\>"cmd /c" echo 1 1 C:\>"cmd.exe /c" echo 1 The system cannot find the path specified. C:\>"cmd /c"echo 1 1 C:\>cmd /c"echo 1 1 C:\>c"md /c"echo 1" 1 ``` note that there's a space in front of 1 in the `"cmd /c"echo 1` case ### Expected Behavior When I run it in mintty.exe, command is parsed properly ```cmd $ cmd Microsoft Windows [Version 10.0.19042.685] (c) 2020 Microsoft Corporation. All rights reserved. D:\>cmd /c echo 1 cmd /c echo 1 1 D:\>"cmd /c"echo 1 "cmd /c"echo 1 The filename, directory name, or volume label syntax is incorrect. D:\>"cmd /c" echo 1 "cmd /c" echo 1 The filename, directory name, or volume label syntax is incorrect. ``` And <kbd>win+r</kbd> run dialog box errs in `Windows cannot find 'cmd /c'. Make sure you typed the name correctly, and then try again." ### Actual Behavior It seems this command is parsed specially. When I copied a program named `cmd.exe` which prints command-line arguments to the current directory, it's not called in this case. ```cmd C:\>cmd /c echo 1 ...calling my program... arg0 is <cmd> arg1 is </c> arg2 is <echo> arg3 is <1> C:\>"cmd /c" echo 1 1 ```
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-CmdPal Issue-Question Needs-Tag-Fix Needs-Triage 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#15427
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?