Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
mveril opened this issue Mar 14, 2024 · 3 comments
Labels
Issue-Docs It's a documentation issue that really should be on MicrosoftDocs/Console-Docs Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@mveril
Copy link

mveril commented 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.

@mveril mveril added the Issue-Docs It's a documentation issue that really should be on MicrosoftDocs/Console-Docs label Mar 14, 2024
@mveril mveril changed the title Provide better documentation and samples for default application implementation. Provide better documentation and samples for default terminal application implementation. Mar 14, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Mar 14, 2024
@zadjii-msft
Copy link
Member

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

@zadjii-msft
Copy link
Member

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

@zadjii-msft zadjii-msft closed this as not planned Won't fix, can't repro, duplicate, stale Mar 18, 2024
Copy link
Contributor

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 microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Docs It's a documentation issue that really should be on MicrosoftDocs/Console-Docs Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants