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

Script opened with WT fail when there is space in the path #17970

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

Originally created by @VCourdy on GitHub (Jul 19, 2022).

Windows Terminal version

1.14.1862.0

Windows build number

10.0.22000.0

Other Software

Powershell 5.1.22000.653

Steps to reproduce

  1. Set WT as the default terminal (Settings > Startup)
  2. Create a PS1 script in a folder with space 
    Write-Host "Bar"
Pause
    Example : foo.ps1 in C:\folder with space
  3. Double click the script
  4. Error :
    "the term "C:\folder" is not recognized as cmdlet function script file or operable program..."

Expected Behavior

Output "Bar"

Actual Behavior

When WT launch a script by double clicking or doing right click / open, the script location is not correctly encapsulated in double quotes.

Originally created by @VCourdy on GitHub (Jul 19, 2022). ### Windows Terminal version 1.14.1862.0 ### Windows build number 10.0.22000.0 ### Other Software Powershell 5.1.22000.653 ### Steps to reproduce 1. Set WT as the default terminal (Settings > Startup) 2. Create a PS1 script in a folder with space ```powershell Write-Host "Bar" Pause ``` Example : foo.ps1 in C:\folder with space 3. Double click the script 4. Error : "the term "C:\folder" is not recognized as cmdlet function script file or operable program..." ### Expected Behavior Output "Bar" ### Actual Behavior When WT launch a script by double clicking or doing right click / open, the script location is not correctly encapsulated in double quotes.
claunia added the Needs-TriageIssue-BugNeeds-Tag-Fix labels 2026-01-31 05:59:55 +00:00
claunia commented 2026-01-31 05:59:57 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 19, 2022):

You cannot typically run a powershell script by double-clicking it. They default to opening in Notepad when you double-click them.
If you have installed something that adds support for double-clicking a PowerShell script, there is a chance that it has been misconfigured or authored improperly.

@DHowett commented on GitHub (Jul 19, 2022): You cannot typically run a powershell script by double-clicking it. They default to opening in Notepad when you double-click them. If you have installed something that adds support for double-clicking a PowerShell script, there is a chance that it has been misconfigured or authored improperly.
claunia commented 2026-01-31 05:59:57 +00:00
Author
Owner
Copy Link

@VCourdy commented on GitHub (Jul 19, 2022):

In fact i simply went in a ps1 file property and set powershell as the default app to use in order to open scripts.
I disabled WT and i have the same issue with powershell so it's not a WT issue.

I'm sorry to have wrongfuly created an issue.

I worked around the issue thanks to this SO :
https://stackoverflow.com/questions/59423051/how-to-run-a-powershell-script-in-a-path-with-spaces

@VCourdy commented on GitHub (Jul 19, 2022): In fact i simply went in a ps1 file property and set powershell as the default app to use in order to open scripts. I disabled WT and i have the same issue with powershell so it's not a WT issue. I'm sorry to have wrongfuly created an issue. I worked around the issue thanks to this SO : https://stackoverflow.com/questions/59423051/how-to-run-a-powershell-script-in-a-path-with-spaces
claunia commented 2026-01-31 05:59:57 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 19, 2022):

I'm sorry to have wrongfuly created an issue.

Oh, that's not a problem at all! It's good for us to know about all of these problems, so we can help people in the future :)
Thank you!

@DHowett commented on GitHub (Jul 19, 2022): > I'm sorry to have wrongfuly created an issue. Oh, that's not a problem at all! It's good for us to know about all of these problems, so we can help people in the future :) Thank you!
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-Bug Needs-Tag-Fix Needs-Triage
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#17970
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?