starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

An Error is emitted when passing a path, containing spaces, to the "Target a directory" [-d] command line argument. #9877

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

Originally created by @AceTheWiz on GitHub (Jul 27, 2020).

Environment

Microsoft Windows [Version 10.0.18362.959]
Windows Terminal Preview [Version: 1.2.2022.0]

Steps to reproduce

Launch Windows Terminal from the Start menu Win+R passing a path containing spaces as a parameter.

wt -d c:\Program Files (x86)\Microsoft\

OR with the path enclosed in quotes.

wt -d "c:\Program Files (x86)\Microsoft\"

Expected behavior

Windows Terminal should launch and open a Tab running PowerShell with the current directory set to the supplied "Target directory", passed as a parameter. In this example the current directory, in PowerShell, should be set to c:\Program Files (x86)\Microsoft\

Actual behavior

Windows Terminal opens and displays an error in a PowerShell Tab.

for the first case i.e. path without quotes.

[error 0x80070002 when launching `Files (x86)\Microsoft\']

for the second case i.e. path with quotes.

[error 0x8007010b when launching `powershell.exe']

The Tab is not usable, iaw it does not respond to any user input.

Originally created by @AceTheWiz on GitHub (Jul 27, 2020). # Environment ```none Microsoft Windows [Version 10.0.18362.959] Windows Terminal Preview [Version: 1.2.2022.0] ``` # Steps to reproduce Launch _Windows Terminal_ from the Start menu ```Win+R``` passing a path containing spaces as a parameter. ```console wt -d c:\Program Files (x86)\Microsoft\ ``` OR with the path enclosed in quotes. ```console wt -d "c:\Program Files (x86)\Microsoft\" ``` # Expected behavior _Windows Terminal_ should launch and open a _Tab_ running PowerShell with the current directory set to the supplied "Target directory", passed as a parameter. In this example the current directory, in PowerShell, should be set to ```c:\Program Files (x86)\Microsoft\``` # Actual behavior _Windows Terminal_ opens and displays an error in a PowerShell _Tab_. for the first case i.e. path without quotes. ```console [error 0x80070002 when launching `Files (x86)\Microsoft\'] ``` for the second case i.e. path with quotes. ```console [error 0x8007010b when launching `powershell.exe'] ``` The _Tab_ is not usable, iaw it does not respond to any user input.
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 02:06:27 +00:00
claunia commented 2026-01-31 02:06:28 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 27, 2020):

I can't reproduce this with 1.1 or 1.2. The key, however, is the \" at the end. The \ is being used to escape the quote (and therefore corrupting the path). Either leave the \ off or use \. 😄

@DHowett commented on GitHub (Jul 27, 2020): I can't reproduce this with 1.1 or 1.2. The key, however, is the `\"` at the end. The `\` is being used to escape the quote (and therefore corrupting the path). Either leave the `\` off or use `\.` :smile:
claunia commented 2026-01-31 02:06:28 +00:00
Author
Owner
Copy Link

@AceTheWiz commented on GitHub (Aug 1, 2020):

I can't reproduce this with 1.1 or 1.2. The key, however, is the \" at the end. The \ is being used to escape the quote (and therefore corrupting the path). Either leave the \ off or use \. 😄

Great thanks it works. Was the only variation I didn't try.

@AceTheWiz commented on GitHub (Aug 1, 2020): > I can't reproduce this with 1.1 or 1.2. The key, however, is the `\"` at the end. The `\` is being used to escape the quote (and therefore corrupting the path). Either leave the `\` off or use `\.` 😄 Great thanks it works. Was the only variation I didn't try.
claunia commented 2026-01-31 02:06:28 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 1, 2020):

Happy to help! Thanks!

@DHowett commented on GitHub (Aug 1, 2020): Happy to help! Thanks!
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#9877
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?