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

Opening a folder from ctx menu which has ";" in it's file name fails to open #15269

New Issue
Closed
opened 2026-01-31 04:33:18 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 04:33:18 +00:00
Owner
Copy Link

Originally created by @char-ptr on GitHub (Sep 19, 2021).

Windows Terminal version (or Windows build number)

Windows Terminal 1.10.2383.0; Microsoft Windows 10.0.19043

Other Software

No response

Steps to reproduce

  1. Have a folder which contains ";" in it's name
  2. Right click the folder and click "Open in Windows Terminal"

Expected Behavior

Windows Terminal to open at the specified directory

Actual Behavior

Two tabs open saying

tab1
[error 0x8007010b when launching `cmd.exe']
Could not access starting directory "<directory up to ;>"

tab2
[error 0x80070002 when launching `<after;>\.']

this happens regardless if im using powershell or cmd as default start up.

Originally created by @char-ptr on GitHub (Sep 19, 2021). ### Windows Terminal version (or Windows build number) Windows Terminal 1.10.2383.0; Microsoft Windows 10.0.19043 ### Other Software _No response_ ### Steps to reproduce 1. Have a folder which contains ";" in it's name 2. Right click the folder and click "Open in Windows Terminal" ### Expected Behavior Windows Terminal to open at the specified directory ### Actual Behavior Two tabs open saying ``` tab1 [error 0x8007010b when launching `cmd.exe'] Could not access starting directory "<directory up to ;>" tab2 [error 0x80070002 when launching `<after;>\.'] ``` this happens regardless if im using powershell or cmd as default start up.
claunia commented 2026-01-31 04:33:19 +00:00
Author
Owner
Copy Link

@elsaco commented on GitHub (Sep 19, 2021):

@pozm semicolon is part of "Word delimiters" defined in the "Interaction" settings:

"wordDelimiters": " /\\()\"'-.,:;<>~!@#$%^&*|+=[]{}~?\u2502",

@elsaco commented on GitHub (Sep 19, 2021): @pozm semicolon is part of "Word delimiters" defined in the "Interaction" settings: ` "wordDelimiters": " /\\()\"'-.,:;<>~!@#$%^&*|+=[]{}~?\u2502",`
claunia commented 2026-01-31 04:33:20 +00:00
Author
Owner
Copy Link

@char-ptr commented on GitHub (Sep 19, 2021):

@pozm semicolon is part of "Word delimiters" defined in the "Interaction" settings:

"wordDelimiters": " /\\()\"'-.,:;<>~!@#$%^&*|+=[]{}~?\u2502",

Even after removing it from there, the same issue still persists.

@char-ptr commented on GitHub (Sep 19, 2021): > > > @pozm semicolon is part of "Word delimiters" defined in the "Interaction" settings: > > ` "wordDelimiters": " /\\()\"'-.,:;<>~!@#$%^&*|+=[]{}~?\u2502",` Even after removing it from there, the same issue still persists.
claunia commented 2026-01-31 04:33:20 +00:00
Author
Owner
Copy Link

@elsaco commented on GitHub (Sep 19, 2021):

@pozm for fun try the other way around, drop the folder name over the "+" tab. After creating a "C:\temp\wt;test" folder this is the result with drag-and-drop:

wt_semicolon_in_folder_name

@elsaco commented on GitHub (Sep 19, 2021): @pozm for fun try the other way around, drop the folder name over the "+" tab. After creating a "C:\temp\wt;test" folder this is the result with drag-and-drop: ![wt_semicolon_in_folder_name](https://user-images.githubusercontent.com/3933920/133943130-a75aca2e-cd90-4106-bb67-6ac086e88d5c.png)
claunia commented 2026-01-31 04:33:20 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 20, 2021):

I'm not quite sure what @‍elasco is on about here. This looks like a legit bug, we're not escaping semicolons in the shell extension. Good catch!

@zadjii-msft commented on GitHub (Sep 20, 2021): I'm not quite sure what **@&zwj;elasco** is on about here. This looks like a legit bug, we're not escaping semicolons in the shell extension. Good catch!
claunia commented 2026-01-31 04:33:21 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 20, 2021):

:tada:This issue was addressed in #11314, which has now been successfully released as Windows Terminal Preview v1.12.2922.0.🎉

Handy links:

@ghost commented on GitHub (Oct 20, 2021): :tada:This issue was addressed in #11314, which has now been successfully released as `Windows Terminal Preview v1.12.2922.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.12.2922.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
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-ShellExtension Issue-Bug Needs-Triage Priority-2 Product-Terminal Resolution-Fix-Committed
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#15269
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?