On terminals like foot, which support some xterm protocols natively but don't report themselves as xterm, using telnet to connect to the kOS terminal breaks completely out of the box, but works if it reports itself as xterm. (In this case, server sided resizing doesn't work because it isn't supported by foot, but I think this is an acceptable tradeoff over not working at all...)
(To elaborate on not working, no input seems to work at all once it gets to the choose cpu to attach to stage.)
I considered directly adding "foot" and some others which supported xterm's "XTGETTCAP" to resolve to TerminalType.XTERM directly in TerminalUnicodeMapper.cs's GuessTypeId, but since they're technically not fully compliant I didn't feel comfortable adding it in, can any devs give some input on this?
On terminals like foot, which support some xterm protocols natively but don't report themselves as xterm, using telnet to connect to the kOS terminal breaks completely out of the box, but works if it reports itself as xterm. (In this case, server sided resizing doesn't work because it isn't supported by foot, but I think this is an acceptable tradeoff over not working at all...)
(To elaborate on not working, no input seems to work at all once it gets to the choose cpu to attach to stage.)
I considered directly adding "foot" and some others which supported xterm's "XTGETTCAP" to resolve to TerminalType.XTERM directly in TerminalUnicodeMapper.cs's GuessTypeId, but since they're technically not fully compliant I didn't feel comfortable adding it in, can any devs give some input on this?