> If a user misconfigures what their current terminal is there isn't much that can be done. We aren't talking about people misconfiguring their terminal. We ar

> If a user misconfigures what their current terminal is there isn't much that can be done. We aren't talking about people misconfiguring their terminal. We are talking about application developers abusing the $TERM command to detect terminal functionality rather than using ANSI escape sequences to detect a terminals support. And thus people then need to spoof $TERM strings to retain the same functionality. This is why you often see $KITTY, $MXTERM and other env vars in addition to $TERM. source: I wrote my own terminal emulator. $TERM these days is garbage. > It's not like the list of new terminals is constantly growing. The list of terminals could be periodically synced if needed. New terminal emulators do. Plus we already have ANSI escape sequences for detecting terminal functionality and it was purposely designed for hardware terminals in mind. Just doing the kids school run but I can share a link to them when i return