Any considerations about setting TERM_PROGRAM environment variable or any other env name else?
Some terminal emulators set $TERM_PROGRAM
and $TERM_PROGRAM_VERSION
env var.
Maybe the env var can help cooperate with some of other tools.
btw, I selectively get some environment variables of some terminal emulators.
1.console
[ruby@fedora ~]$ env |grep TERM
COLORTERM=truecolor
TERM=xterm-256color
2.kitty
[ruby@fedora ~]$ env |grep TERM
COLORTERM=truecolor
TERMINFO=/usr/lib64/kitty/terminfo
TERM=xterm-kitty
3.gnome terminal
(py311) [ruby@fedora ~]$ env |grep TERM
COLORTERM=truecolor
GNOME_TERMINAL_SCREEN=/org/gnome/Terminal/screen/b8f7a470_ec48_4e3d_b718_d8d2f2b3f762
TERM=xterm-256color
GNOME_TERMINAL_SERVICE=:1.125
4.contour terminal
[ruby@fedora ~]$ env |grep TERM
COLORTERM=truecolor
TERMINAL_VERSION_STRING=0.3.8
TERMINAL_VERSION_TRIPLE=0.3.8
TERMINAL_NAME=contour
TERM=contour
5.wezterm
[ruby@fedora ~]$ env |grep TERM
COLORTERM=truecolor
TERM_PROGRAM_VERSION=20221219-152113-e020a9f6
WEZTERM_EXECUTABLE=/usr/bin/wezterm-gui
WEZTERM_UNIX_SOCKET=/run/user/1000/wezterm/gui-sock-3345442
TERM=xterm-256color
WEZTERM_PANE=0
TERM_PROGRAM=WezTerm
WEZTERM_EXECUTABLE_DIR=/usr/bin
6.alacritty
[ruby@fedora ~]$ env |grep TERM
COLORTERM=truecolor
TERM=alacritty
7.terminator
[ruby@fedora ~]$ env |grep TERM
COLORTERM=truecolor
TERMINATOR_DBUS_PATH=/net/tenshu/Terminator2
TERMINATOR_UUID=urn:uuid:721fda81-bca5-46f9-8382-0d16694c1425
TERMINATOR_DBUS_NAME=net.tenshu.Terminator25ef4b219e3b005583550f2b0f9f990c3
TERM=xterm-256color
8.tilix
[ruby@fedora ~]$ env |grep TERM
COLORTERM=truecolor
TERM=xterm-256color
https://github.com/Maximus5/ConEmu/issues/1837#issuecomment-469199525
https://github.com/alacritty/alacritty/pull/4717
https://github.com/alacritty/alacritty/issues/781