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

"Open Terminal Here" can't be used with both the dev build and preview at the same time #8917

New Issue
Closed
opened 2026-01-31 01:41:21 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 01:41:21 +00:00
Owner
Copy Link

Originally created by @zadjii-msft on GitHub (Jun 8, 2020).

The Dev build one seems to always stomp the preview one.

  • Is this because they share the same Verb string? This is easy to fix
  • Or maybe is this because they share the same ClsId? This would be annoying to fix.
Originally created by @zadjii-msft on GitHub (Jun 8, 2020). The Dev build one seems to always stomp the preview one. * Is this because they share the same `Verb` string? _This is easy to fix_ * Or maybe is this because they share the same ClsId? _This would be annoying to fix_.
claunia commented 2026-01-31 01:41:22 +00:00
Author
Owner
Copy Link

@KUTlime commented on GitHub (Oct 17, 2020):

@zadjii-msft Maybe you could solve this problem prior to Terminal v2.0 by OpenHere module.

@KUTlime commented on GitHub (Oct 17, 2020): @zadjii-msft Maybe you could solve this problem prior to [Terminal v2.0](https://github.com/microsoft/terminal/milestone/22) by [OpenHere](https://github.com/KUTlime/PowerShell-Open-Here-Module) module.
claunia commented 2026-01-31 01:41:22 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 17, 2020):

image

Yea pretty sure I can't look at that, sorry. I'm not a expert in software licensing, but I know I can't look at GPL code.

@zadjii-msft commented on GitHub (Oct 17, 2020): ![image](https://user-images.githubusercontent.com/18356694/96349631-6a44a100-1076-11eb-9de5-24d6cfb96eee.png) Yea pretty sure I can't look at that, sorry. I'm not a expert in software licensing, but I know I can't look at GPL code.
claunia commented 2026-01-31 01:41:22 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 18, 2020):

Regardless of how other shell extensions do it, if they’re not packaged applications (appx/msix) they will not be encountering or have had to work around this issue and will therefore not be a good model for how to fix it.

This is a limitation in the windows platform with regards to shell extensions in packaged applications.

@DHowett commented on GitHub (Oct 18, 2020): Regardless of how other shell extensions do it, if they’re not packaged applications (appx/msix) they will not be encountering or have had to work around this issue and will therefore not be a good model for how to fix it. This is a limitation in the windows platform with regards to shell extensions _in packaged applications_.
claunia commented 2026-01-31 01:41:22 +00:00
Author
Owner
Copy Link

@KUTlime commented on GitHub (Oct 18, 2020):

@zadjii-msft You got it all wrong. The module will not fix the problem for Windows Terminal as an application, it will solve the problem for you as a user of Windows Terminal.

@KUTlime commented on GitHub (Oct 18, 2020): @zadjii-msft You got it all wrong. The module will not fix the problem for Windows Terminal as an application, it will solve the problem for you as a user of Windows Terminal.
claunia commented 2026-01-31 01:41:23 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 18, 2020):

@KUTlime Ah, thanks for the clarification. As one of the maintainers of the Terminal, I'm actually less concerned about using this myself, but more just implementing the fix for the Terminal so this bug won't affect other users ☺️

@zadjii-msft commented on GitHub (Oct 18, 2020): @KUTlime Ah, thanks for the clarification. As one of the maintainers of the Terminal, I'm actually less concerned about using this myself, but more just implementing the fix for the Terminal so this bug won't affect _other users_ ☺️
claunia commented 2026-01-31 01:41:23 +00:00
Author
Owner
Copy Link

@KUTlime commented on GitHub (Oct 18, 2020):

@zadjii-msft Sure, no problem. Maybe my advice help someone else. 😉

@KUTlime commented on GitHub (Oct 18, 2020): @zadjii-msft Sure, no problem. Maybe my advice help someone else. 😉
claunia commented 2026-01-31 01:41:23 +00:00
Author
Owner
Copy Link

@KalleOlaviNiemitalo commented on GitHub (Feb 3, 2021):

I have Windows Terminal 1.4.3243.0 and Windows Terminal Preview 1.6.10272.0, and when I choose "Open in Windows Terminal" from a directory or from the background of a directory, it starts Windows Terminal 1.4.3243.0. Is that the same issue?

At HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\ClassIndex\{9F156763-7844-4DC4-B2B1-901F640F5155}, there are two subkeys:

  • Microsoft.WindowsTerminal_1.4.3243.0_x64__8wekyb3d8bbwe
  • Microsoft.WindowsTerminalPreview_1.6.10272.0_x64__8wekyb3d8bbwe

At HKEY_CURRENT_USER\SOFTWARE\Classes\PackagedCom\Package, there are identically named subkeys, and a few others besides. Here, each subkey has a REG_DWORD default value that may indicate the order in which the apps were installed; Windows Terminal Preview has 19 and Windows Terminal has 20. If I change the Windows Terminal value to 2 and restart Explorer, then "Open in Windows Terminal" starts Windows Terminal Preview. I think it means Packaged COM prefers the package that was installed last.

@KalleOlaviNiemitalo commented on GitHub (Feb 3, 2021): I have Windows Terminal 1.4.3243.0 and Windows Terminal Preview 1.6.10272.0, and when I choose "Open in Windows Terminal" from a directory or from the background of a directory, it starts Windows Terminal 1.4.3243.0. Is that the same issue? At `HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PackagedCom\ClassIndex\{9F156763-7844-4DC4-B2B1-901F640F5155}`, there are two subkeys: * Microsoft.WindowsTerminal_1.4.3243.0_x64__8wekyb3d8bbwe * Microsoft.WindowsTerminalPreview_1.6.10272.0_x64__8wekyb3d8bbwe At `HKEY_CURRENT_USER\SOFTWARE\Classes\PackagedCom\Package`, there are identically named subkeys, and a few others besides. Here, each subkey has a REG_DWORD default value that may indicate the order in which the apps were installed; Windows Terminal Preview has 19 and Windows Terminal has 20. If I change the Windows Terminal value to 2 and restart Explorer, then "Open in Windows Terminal" starts Windows Terminal Preview. I think it means [Packaged COM](<https://blogs.windows.com/windowsdeveloper/2017/04/13/com-server-ole-document-support-desktop-bridge/> "COM Server and OLE Document support for the Desktop Bridge - Windows Developer Blog") prefers the package that was installed last.
claunia commented 2026-01-31 01:41:23 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 14, 2021):

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

Handy links:

@ghost commented on GitHub (Apr 14, 2021): :tada:This issue was addressed in #9510, which has now been successfully released as `Windows Terminal v1.7.1033.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.7.1033.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
claunia commented 2026-01-31 01:41:24 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 14, 2021):

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

Handy links:

@ghost commented on GitHub (Apr 14, 2021): :tada:This issue was addressed in #9510, which has now been successfully released as `Windows Terminal Preview v1.8.1032.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.8.1032.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 Help Wanted Issue-Bug 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#8917
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?