Skip to content
  • rswindell's avatar
    b2d98bb2
    Bug-fix: when using Telnet, we would *always* send the terminal type · b2d98bb2
    rswindell authored
    (if the server supported the option), as "ANSI". Now, if the current cterm
    emualation is PETASCII [sic], or ATASCII, send "PETSCII" or "ATASCII"
    instead.
    
    Now this brings up a couple of discussion points:
    1. Should that default Telnet term-type be "ANSI-BBS" (or "ansi-bbs") instead?
    2. Similarlly, RLogin connections *always* send the term-type as "ansi-bbs" -
       I think a similar change is needed in rlogin.c to be technically correct,
       but we should probably be consistent about how SyncTERM in ANSI-BBS emulation
       mode identifies itself ("ANSI", "ANSI-BBS", or "ansi-bbs").
    3. If there is terminal type advertised via SSH, that probably needs addressing
       as well.
    b2d98bb2
    Bug-fix: when using Telnet, we would *always* send the terminal type
    rswindell authored
    (if the server supported the option), as "ANSI". Now, if the current cterm
    emualation is PETASCII [sic], or ATASCII, send "PETSCII" or "ATASCII"
    instead.
    
    Now this brings up a couple of discussion points:
    1. Should that default Telnet term-type be "ANSI-BBS" (or "ansi-bbs") instead?
    2. Similarlly, RLogin connections *always* send the term-type as "ansi-bbs" -
       I think a similar change is needed in rlogin.c to be technically correct,
       but we should probably be consistent about how SyncTERM in ANSI-BBS emulation
       mode identifies itself ("ANSI", "ANSI-BBS", or "ansi-bbs").
    3. If there is terminal type advertised via SSH, that probably needs addressing
       as well.
Loading