Provide better documentation and samples for default terminal application implementation. #21395

Closed
opened 2026-01-31 07:43:26 +00:00 by claunia · 3 comments
Owner

Originally created by @mveril on GitHub (Mar 14, 2024).

Hello
I think it should be good to provide a better documentation for default application implementation. And it's also important in order to continue in this philosophy of openness that this project has had since the beginning. It should be cool for some third party terminal to implement it. for example it's a subject already evoqued in felixse/FluentTerminal/issues/965.
It should be also good to have a C++ and C# sample for it.
I searched and I not found any third party default terminal implementation. I think the "problem" come from this pont.
I studed how to do it by reading the code of Windows Terminal and I think because the implementation use AppExtension I think it's not possible to use it for a unpackaged app like vscode or wezterm can you confirm it. So it should be good to have a packaged and also an unpackaged sample for it.

Originally created by @mveril on GitHub (Mar 14, 2024). Hello I think it should be good to provide a better documentation for default application implementation. And it's also important in order to continue in this philosophy of openness that this project has had since the beginning. It should be cool for some third party terminal to implement it. for example it's a subject already evoqued in felixse/FluentTerminal/issues/965. It should be also good to have a C++ and C# sample for it. I searched and I not found any third party default terminal implementation. I think the "problem" come from this pont. I studed how to do it by reading the code of Windows Terminal and I think because the implementation use [AppExtension](https://learn.microsoft.com/en-us/windows/uwp/launch-resume/how-to-create-an-extension) I think it's not possible to use it for a unpackaged app like [vscode](https://github.com/microsoft/vscode/issues/171102) or [wezterm](https://github.com/wez/wezterm) can you confirm it. So it should be good to have a packaged and also an unpackaged sample for it.
claunia added the Resolution-DuplicateIssue-Docs labels 2026-01-31 07:43:26 +00:00
Author
Owner

@zadjii-msft commented on GitHub (Mar 14, 2024):

There's a bit more discussion of this over in #9462 - perhaps we should de-dupe these threads?

@zadjii-msft commented on GitHub (Mar 14, 2024): There's a bit more discussion of this over in #9462 - perhaps we should de-dupe these threads?
Author
Owner

@zadjii-msft commented on GitHub (Mar 18, 2024):

After thinking on it, yea we should fold this discussion into the thread over at /dup #9462. Thanks!

@zadjii-msft commented on GitHub (Mar 18, 2024): After thinking on it, yea we should fold this discussion into the thread over at /dup #9462. Thanks!
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Mar 18, 2024):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service[bot] commented on GitHub (Mar 18, 2024): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#21395