Non-standard OSC to get the terminal app

[trajano]

OSC 52 allows pasting assuming it is allowed by Windows Terminal so that at least gives prior work that shows OSC can be used to get data from the local machine.

I was wondering if it is possible to add something like a non-standard OSC code that would yield the name of the terminal app or allow querying the terminal app as using the WT_SESSION environment variable is won't work over SSH like in moor

https://github.com/walles/moor/blob/36e76c6caa17bc16ad0ebc6174c1fe2b2925fae9/twin/screen.go#L374

Something like OSC XX will force typing WindowsTerminal\0 by Windows terminal.

The querying would be

OSC XX WindowsTerminal;Hyper;; and force typing \1 if it matches. The only restriction that should be put in place is the escape sequence must be less than 80-characters,

[eamonburns]

I can't answer the question about OSC, but if you have control over the SSH server, you can allow it to accept certain environment variables (see AcceptEnv, SendEnv).

# Server configuration
AcceptEnv WT_SESSION

# Client configuration
Host server.local
    SendEnv WT_SESSION

(The AcceptEnv option can be insecure, based on which environment variables are accepted. It should be fine in the case of WT_SESSION)

[trajano]

Yeah I know about the SendEnv, AcceptEnv I was trying to avoid that one for cases where I don't control the SSH server itself.

[eamonburns]

Understandable

[eamonburns]

Would setting the environment variable $TERM suffice?

It looks like you check for other terminals as well. How did you get those to work over SSH?

[j4james]

@trajano I've replied with more details in the moor issue, but the gist of my response is that you should be using a capability query if you want to determine if a terminal supports a particular feature, rather than querying the terminal name and hardcoding the list of supported terminals. That list will inevitably be out of date and incomplete.

[trajano]

I presume Windows Terminal supports that query?

[j4james]

Yes it does.