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

Recognizing the new terminal as an application #7995

Closed
Bios-Marcel opened this issue Oct 21, 2020 · 5 comments
Closed

Recognizing the new terminal as an application #7995

Bios-Marcel opened this issue Oct 21, 2020 · 5 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

@Bios-Marcel
Copy link

Depending on what feature set is a available on a terminal, an application might want to act differently. For example, using emojis and such should be avoided in the old windows terminal. Is there some easy way, that applications can use to know they are running on the new version of the windows terminal? Whether this is possible or not, it would be great to mention this somewhere in /doc I assume.

@Bios-Marcel Bios-Marcel added the Issue-Docs It's a documentation issue that really should be on MicrosoftDocs/Console-Docs label Oct 21, 2020
@ghost ghost 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 Oct 21, 2020
@Bios-Marcel
Copy link
Author

Somebody just hinted me that the variable introduced with #897 (WT_SESSION) could probably be used for this.

@DHowett
Copy link
Member

DHowett commented Oct 21, 2020

Applications should not attempt to detect whether they're running in WT. Any assumption they make will be invalidated with time. Any application that attempts to ascribe specific behavior to Windows Terminal will be wrong and cause unnecessary vendor lock-in when it inevitably fails to work on Hyper, Alacritty, Mintty, and ConEmu even though those terminals support all the same features.

For example, using emojis and such should be avoided in the old windows terminal.

This is only true today, and will not be true once the rendering engine in this repository converges with the one in Windows.

All of the code in this repository that pertains to the inbox console host eventually goes into Windows, and goes out into the "old" windows "terminal."

/dup #1060.

@ghost

This comment has been minimized.

@ghost ghost closed this as completed Oct 21, 2020
@ghost ghost 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 Oct 21, 2020
@DHowett
Copy link
Member

DHowett commented Oct 21, 2020

Sorry, I meant /dup #1040!

@ghost

This comment has been minimized.

This issue was closed.
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