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 in windows terminal' cant show in Directory Opuss context menu #12838

New Issue
Closed
opened 2026-01-31 03:26:15 +00:00 by claunia · 6 comments
claunia commented 2026-01-31 03:26:15 +00:00
Owner
Copy Link

Originally created by @codeime on GitHub (Mar 3, 2021).

image

Originally created by @codeime on GitHub (Mar 3, 2021). ![image](https://user-images.githubusercontent.com/22333388/109806079-3baf1780-7c5f-11eb-9c71-2b159526fe6c.png)
claunia commented 2026-01-31 03:26:16 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 3, 2021):

I don't have any idea how Directory Opus is populating that context menu. I know that when I was first working on the context menu for explorer, I'd often have to hard-restart explorer.exe to have it reload the context menu entries. Perhaps you could try doing that with Directory Opus?

Otherwise I'm not really sure what we could do here - this sounds like a bug to file on Directory Opus.

@zadjii-msft commented on GitHub (Mar 3, 2021): I don't have any idea how Directory Opus is populating that context menu. I know that when I was first working on the context menu for explorer, I'd often have to hard-restart `explorer.exe` to have it reload the context menu entries. Perhaps you could try doing that with Directory Opus? Otherwise I'm not really sure what we could do here - this sounds like a bug to file on Directory Opus.
claunia commented 2026-01-31 03:26:16 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 3, 2021):

It looks like Directory Opus is not enumerating all shell extensions. I wonder if they are doing it manually?

@DHowett commented on GitHub (Mar 3, 2021): It looks like Directory Opus is not enumerating all shell extensions. I wonder if they are doing it manually?
claunia commented 2026-01-31 03:26:17 +00:00
Author
Owner
Copy Link

@Nirmal4G commented on GitHub (Mar 7, 2021):

Directory Opus enumerates only Basic Shell Extensions, entries only in Shell and not in ShellEx (i.e. without class ids CLSID). You have to ask the Directory Opus guys to extend this feature.

@Nirmal4G commented on GitHub (Mar 7, 2021): **Directory Opus** enumerates only Basic Shell Extensions, entries only in `Shell` and not in `ShellEx` (_i.e. without class ids `CLSID`_). You have to ask the **Directory Opus** guys to extend this feature.
claunia commented 2026-01-31 03:26:17 +00:00
Author
Owner
Copy Link

@LeoDavidson commented on GitHub (Mar 8, 2021):

Directory Opus enumerates only Basic Shell Extensions, entries only in Shell and not in ShellEx (i.e. without class ids CLSID). You have to ask the Directory Opus guys to extend this feature.

Opus developer here. I don't know where that idea comes from? Opus's own shell extensions use the ShellEx keys in places.

Looking at Terminal, it does not appear to register its shell extension against the folder or directory type anywhere in the registry. (Please correct me if I'm wrong.)

It seems to be using C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.6.10571.0_x64__8wekyb3d8bbwe\AppManifest.xml. (Below the wonderful WindowsApps folder that is permissioned so you cannot list its contents, because that's super helpful.)

        <desktop4:Extension Category="windows.fileExplorerContextMenus">
          <desktop4:FileExplorerContextMenus>
            <desktop5:ItemType Type="Directory">
              <desktop5:Verb Id="Command1" Clsid="9f156763-7844-4dc4-b2b1-901f640f5155" />
            </desktop5:ItemType>
            <desktop5:ItemType Type="Directory\Background">
              <desktop5:Verb Id="Command2" Clsid="9f156763-7844-4dc4-b2b1-901f640f5155" />
            </desktop5:ItemType>
          </desktop4:FileExplorerContextMenus>
        </desktop4:Extension>

We support that kind of registration for preview handlers, but not for context menus. AFAIK there is no API for querying them, and finding them means searching the registry for every component under the PackagedCom registry key, and then loading and parsing each individual component's AppxManifest.xml file to see if it happens to add something to the type we're interested in.

We may look at adding support for this, but it seems like it could be bad for performance, with right-click menus being slow enough already due to all the shell extensions, unless there is a better way to do the query, e.g. an API. Especially when there are so few components using this method, with Terminal being the only one I'm aware of that is itself worth using.

Maybe there is a better way to query the XML registration that we aren't aware of? Documentation on this stuff is severely lacking, especially for people needing to query it from the Win32 side of things, unless things have improved in the last year or so.

(After the work we did on preview handler support for this kind of registration, only for Microsoft to then break and abandon their 3D Object Viewer preview handler and make that work a complete waste of time, I'm also a little reluctant to commit time to this for another Microsoft project.)

OTOH, if Terminal registers itself centrally in registry in the standard Win32 way, it would work automatically. Why Metro/Windows Store/whatever-they're-called-this-week-style apps don't/can't just do that, like every normal app on Windows has since Windows 95, rather than scatter settings around hundreds of xml files, I do not know.

@LeoDavidson commented on GitHub (Mar 8, 2021): > **Directory Opus** enumerates only Basic Shell Extensions, entries only in `Shell` and not in `ShellEx` (_i.e. without class ids `CLSID`_). You have to ask the **Directory Opus** guys to extend this feature. Opus developer here. I don't know where that idea comes from? Opus's own shell extensions use the ShellEx keys in places. Looking at Terminal, it does not appear to register its shell extension against the folder or directory type anywhere in the registry. (Please correct me if I'm wrong.) It seems to be using `C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.6.10571.0_x64__8wekyb3d8bbwe\AppManifest.xml`. (Below the wonderful WindowsApps folder that is permissioned so you cannot list its contents, because that's super helpful.) ``` <desktop4:Extension Category="windows.fileExplorerContextMenus"> <desktop4:FileExplorerContextMenus> <desktop5:ItemType Type="Directory"> <desktop5:Verb Id="Command1" Clsid="9f156763-7844-4dc4-b2b1-901f640f5155" /> </desktop5:ItemType> <desktop5:ItemType Type="Directory\Background"> <desktop5:Verb Id="Command2" Clsid="9f156763-7844-4dc4-b2b1-901f640f5155" /> </desktop5:ItemType> </desktop4:FileExplorerContextMenus> </desktop4:Extension> ``` We support that kind of registration for preview handlers, but not for context menus. AFAIK there is no API for querying them, and finding them means searching the registry for every component under the PackagedCom registry key, and then loading and parsing each individual component's AppxManifest.xml file to see if it happens to add something to the type we're interested in. We may look at adding support for this, but it seems like it could be bad for performance, with right-click menus being slow enough already due to all the shell extensions, unless there is a better way to do the query, e.g. an API. Especially when there are so few components using this method, with Terminal being the only one I'm aware of that is itself worth using. Maybe there is a better way to query the XML registration that we aren't aware of? Documentation on this stuff is severely lacking, especially for people needing to query it from the Win32 side of things, unless things have improved in the last year or so. (After the work we did on preview handler support for this kind of registration, only for Microsoft to then break and abandon their 3D Object Viewer preview handler and make that work a complete waste of time, I'm also a little reluctant to commit time to this for another Microsoft project.) OTOH, if Terminal registers itself centrally in registry in the standard Win32 way, it would work automatically. Why Metro/Windows Store/whatever-they're-called-this-week-style apps don't/can't just do that, like every normal app on Windows has since Windows 95, rather than scatter settings around hundreds of xml files, I do not know.
claunia commented 2026-01-31 03:26:17 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 12, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Mar 12, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 03:26:17 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 15, 2021):

OTOH, if Terminal registers itself centrally in registry in the standard Win32 way, it would work automatically. Why Metro/Windows Store/whatever-they're-called-this-week-style apps don't/can't just do that, like every normal app on Windows has since Windows 95, rather than scatter settings around hundreds of xml files, I do not know.

I wish I knew. I really do. ☹️

@DHowett commented on GitHub (Mar 15, 2021): > OTOH, if Terminal registers itself centrally in registry in the standard Win32 way, it would work automatically. Why Metro/Windows Store/whatever-they're-called-this-week-style apps don't/can't just do that, like every normal app on Windows has since Windows 95, rather than scatter settings around hundreds of xml files, I do not know. I wish I knew. I really do. ☹️
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 Needs-Author-Feedback 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#12838
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?