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

Unable to pass command line parameters after the double dash in Windows Terminal #22581

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

Originally created by @hh54188 on GitHub (Nov 21, 2024).

Windows Terminal version

1.21.2911.0

Windows build number

10.0.19045.2604

Other Software

Node: v20.16.0
NPM: 10.8.1

Steps to reproduce

Here is the command I want to run on Windows Terminal:

pm2 start C:\Users\User\AppData\Roaming\npm\node_modules\http-server\bin\http-server --name http-server-app -- --port 3000

If I run it in the Windows Terminal, I will get this error:

error: unknown option `--port'.

The same error will appear in the Powershell. But it will succeed in the Command Line.

Is there a way to solve this problem?

Expected Behavior

The port number parameter can be passed to the command line successfully.

Actual Behavior

error: unknown option `--port'.

Originally created by @hh54188 on GitHub (Nov 21, 2024). ### Windows Terminal version 1.21.2911.0 ### Windows build number 10.0.19045.2604 ### Other Software Node: v20.16.0 NPM: 10.8.1 ### Steps to reproduce Here is the command I want to run on Windows Terminal: ``` pm2 start C:\Users\User\AppData\Roaming\npm\node_modules\http-server\bin\http-server --name http-server-app -- --port 3000 ``` If I run it in the Windows Terminal, I will get this error: > error: unknown option `--port'. The same error will appear in the Powershell. But it will succeed in the Command Line. Is there a way to solve this problem? ### Expected Behavior The port number parameter can be passed to the command line successfully. ### Actual Behavior error: unknown option `--port'.
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 08:17:36 +00:00
claunia commented 2026-01-31 08:17:37 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 21, 2024):

When you say “in Windows Terminal,” is there a chance you mean “in PowerShell”?

Terminal supports running different shells, like PowerShell and Command Prompt.

If you are seeing a difference in argument handling, there is a chance you are not using the shell you are expecting.

EDIT: ah, I see you included that info in your original issue.

@DHowett commented on GitHub (Nov 21, 2024): ~~When you say “in Windows Terminal,” is there a chance you mean “in PowerShell”?~~ ~~Terminal supports running different shells, like PowerShell and Command Prompt.~~ ~~If you are seeing a difference in argument handling, there is a chance you are not using the shell you are expecting.~~ EDIT: ah, I see you included that info in your original issue.
claunia commented 2026-01-31 08:17:37 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 21, 2024):

Is there a way to solve this problem?

You can run Command Prompt inside Windows Terminal. Please consult the dropdown menu for either a one-off option to run Command Prompt or a permanent option to configure your “Default Profile”.

@DHowett commented on GitHub (Nov 21, 2024): > Is there a way to solve this problem? You can run Command Prompt inside Windows Terminal. Please consult the dropdown menu for either a one-off option to run Command Prompt or a permanent option to configure your “Default Profile”.
claunia commented 2026-01-31 08:17:37 +00:00
Author
Owner
Copy Link

@elsaco commented on GitHub (Nov 21, 2024):

@hh54188 in pwsh try using quotes or escape the double hyphen.

Sample output:

PS C:\Users\WDAGUtilityAccount> pm2 start C:\Users\User\AppData\Roaming\npm\node_modules\http-server\bin\http-server --name http-server-app '--' --port 3000
[PM2][ERROR] Script not found: C:\Users\User\AppData\Roaming\npm\node_modules\http-server\bin\http-server
PS C:\Users\WDAGUtilityAccount> pm2 start .\AppData\Roaming\npm\node_modules\http-server\bin\http-server --name http-ser
ver-app -- --port 3000

  error: unknown option `--port'

PS C:\Users\WDAGUtilityAccount> pm2 start .\AppData\Roaming\npm\node_modules\http-server\bin\http-server --name http-server-app `-- --port 3000
[PM2] Starting C:\Users\WDAGUtilityAccount\AppData\Roaming\npm\node_modules\http-server\bin\http-server in fork_mode (1 instance)
[PM2] Done.
┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
│ id │ name               │ mode     │ ↺    │ status    │ cpu      │ memory   │
├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤
│ 0  │ http-server-app    │ fork     │ 0    │ online    │ 0%       │ 45.6mb   │
└────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘
@elsaco commented on GitHub (Nov 21, 2024): @hh54188 in pwsh try using quotes or escape the double hyphen. Sample output: ``` PS C:\Users\WDAGUtilityAccount> pm2 start C:\Users\User\AppData\Roaming\npm\node_modules\http-server\bin\http-server --name http-server-app '--' --port 3000 [PM2][ERROR] Script not found: C:\Users\User\AppData\Roaming\npm\node_modules\http-server\bin\http-server PS C:\Users\WDAGUtilityAccount> pm2 start .\AppData\Roaming\npm\node_modules\http-server\bin\http-server --name http-ser ver-app -- --port 3000 error: unknown option `--port' PS C:\Users\WDAGUtilityAccount> pm2 start .\AppData\Roaming\npm\node_modules\http-server\bin\http-server --name http-server-app `-- --port 3000 [PM2] Starting C:\Users\WDAGUtilityAccount\AppData\Roaming\npm\node_modules\http-server\bin\http-server in fork_mode (1 instance) [PM2] Done. ┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐ │ id │ name │ mode │ ↺ │ status │ cpu │ memory │ ├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤ │ 0 │ http-server-app │ fork │ 0 │ online │ 0% │ 45.6mb │ └────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘ ```
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#22581
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?