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

"Open in Windows Terminal" Explorer context menu on left pane opens to wrong location #16398

New Issue
Closed
opened 2026-01-31 05:06:25 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 05:06:25 +00:00
Owner
Copy Link

Originally created by @johnburnett on GitHub (Jan 13, 2022).

Windows Terminal version

1.11.3471.0

Windows build number

22000.434

Other Software

No response

Steps to reproduce

Assume a directory tree that looks like this:

parentDir/
  childDirA/
  childDirB/
  1. Navigate to the childDirA subdir so that the contents shows in the right pane of explorer
  2. right-click on childDirB in the left (treeview) pane of explorer (the contents of childDirA will continue to show in the right pane)
  3. Choose "Open in Windows Terminal"

Expected Behavior

A terminal to open with childDirB as the current dir.

Actual Behavior

The terminal opens to childDirA. Might be related to #11587 (which references internal issues MSFT:36795851 and MSFT:36416534.

Originally created by @johnburnett on GitHub (Jan 13, 2022). ### Windows Terminal version 1.11.3471.0 ### Windows build number 22000.434 ### Other Software _No response_ ### Steps to reproduce Assume a directory tree that looks like this: ``` parentDir/ childDirA/ childDirB/ ``` 1. Navigate to the `childDirA` subdir so that the contents shows in the right pane of explorer 2. right-click on `childDirB` in the *left* (treeview) pane of explorer (the contents of `childDirA` will continue to show in the right pane) 3. Choose "Open in Windows Terminal" ### Expected Behavior A terminal to open with `childDirB` as the current dir. ### Actual Behavior The terminal opens to `childDirA`. Might be related to #11587 (which references internal issues MSFT:36795851 and MSFT:36416534.
claunia commented 2026-01-31 05:06:27 +00:00
Author
Owner
Copy Link

@elsaco commented on GitHub (Jan 14, 2022):

@johnburnett if you open childDirB (content shown in the right pane) then right-click directory childDirA the terminal will open in childDirB. I tried with more subfolders and the terminal opens to whatever folder has been selected in the left pane to have its contend shown.

@elsaco commented on GitHub (Jan 14, 2022): @johnburnett if you open `childDirB` (content shown in the right pane) then right-click directory `childDirA` the terminal will open in `childDirB`. I tried with more subfolders and the terminal opens to whatever folder has been selected in the left pane to have its contend shown.
claunia commented 2026-01-31 05:06:28 +00:00
Author
Owner
Copy Link

@johnburnett commented on GitHub (Jan 14, 2022):

@elsaco - correct, the terminal always opens to the folder shown in the right pane. This is surprising/wrong, as right-clicking on a folder on the left pane should indicate that that is the folder I want to open to. This seems to be a problem with the new Windows 11 context menu specifically. If you choose "Show more options > Open in Windows Terminal" for step 3 above, you can see the old/correct behavior.

@johnburnett commented on GitHub (Jan 14, 2022): @elsaco - correct, the terminal always opens to the folder shown in the right pane. This is surprising/wrong, as right-clicking on a folder on the left pane should indicate that *that* is the folder I want to open to. This seems to be a problem with the new Windows 11 context menu specifically. If you choose "Show more options > Open in Windows Terminal" for step 3 above, you can see the old/correct behavior.
claunia commented 2026-01-31 05:06:28 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 18, 2022):

Thanks for filing this! I've moved this upstream to the File Explorer folks, in MSFT:37779037.

@zadjii-msft commented on GitHub (Jan 18, 2022): Thanks for filing this! I've moved this upstream to the File Explorer folks, in MSFT:37779037.
claunia commented 2026-01-31 05:06:28 +00:00
Author
Owner
Copy Link

@johnburnett commented on GitHub (Jan 18, 2022):

@zadjii-msft - great, thanks! Is there any was to get visibility to this? This same issue seems to impact other tools that interact with the left pane (e.g. TortoiseGit has the same problem), and I'd imagine the fix will be the same.

@johnburnett commented on GitHub (Jan 18, 2022): @zadjii-msft - great, thanks! Is there any was to get visibility to this? This same issue seems to impact other tools that interact with the left pane (e.g. TortoiseGit [has the same problem](https://gitlab.com/tortoisegit/tortoisegit/-/issues/3845)), and I'd imagine the fix will be the same.
claunia commented 2026-01-31 05:06:28 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 18, 2022):

Unfortunately not really. On the bright side, my experience with the File Explorer team has been pretty positive overall, and they've been fairly good about getting on top of the context menu bugs we've thrown their way.

@zadjii-msft commented on GitHub (Jan 18, 2022): Unfortunately not really. On the bright side, my experience with the File Explorer team has been pretty positive overall, and they've been fairly good about getting on top of the context menu bugs we've thrown their way.
claunia commented 2026-01-31 05:06:28 +00:00
Author
Owner
Copy Link

@johnburnett commented on GitHub (Jan 18, 2022):

Ok, no worries - I'll keep an eye on this ticket as a proxy for what the
fix might look like.

@johnburnett commented on GitHub (Jan 18, 2022): Ok, no worries - I'll keep an eye on this ticket as a proxy for what the fix might look like.
claunia commented 2026-01-31 05:06:29 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 19, 2022):

This got duped to MSFT:36889296, which was just fixed internally and should be flowing out to an Insiders build sometime soon.

@zadjii-msft commented on GitHub (Mar 19, 2022): This got duped to MSFT:36889296, which was just fixed internally and should be flowing out to an Insiders build sometime soon.
claunia commented 2026-01-31 05:06:29 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 3, 2022):

I believe this was either fixed in 22570 or 25071 - build numbers are confusing these days, but both those builds date back to March. Thanks all!

@zadjii-msft commented on GitHub (Aug 3, 2022): I believe this was either fixed in `22570` or `25071` - build numbers are confusing these days, but both those builds date back to March. Thanks all!
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 Product-Terminal Resolution-Fix-Committed Tracking-External
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#16398
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?