home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.protocols.tcp-ip:5894 comp.protocols.tcp-ip.ibmpc:7318
- Newsgroups: comp.protocols.tcp-ip,comp.protocols.tcp-ip.ibmpc
- Path: sparky!uunet!eco.twg.com!twg.com!nntp-server.twg.com!frank
- From: frank@twg.com (Frank McConnell)
- Subject: Re: TELNET terminal types
- In-Reply-To: jcmorris@mwunix.mitre.org's message of Sat, 9 Jan 1993 18:10:02 GMT
- Message-ID: <FRANK.93Jan9155902@sundance.twg.com>
- Sender: news@twg.com (USENET News System)
- Organization: The Wollongong Group, Palo Alto, CA (USA)
- References: <jcmorris.726603002@mwunix>
- Date: Sat, 9 Jan 1993 23:59:02 GMT
- Lines: 23
-
- I find the following workaround helpful in dealing with mismatches
- between the terminal types listed in the Assigned Numbers RFC and
- those that appear in termcap or terminfo databases:
-
- eval `tset -s -m 'dec-vt100:vt100' -m 'network:?vt100'`
-
- This appears in my .login on most of the Suns that I work with.
-
- The "-m 'dec-vt100:vt100'" instructs tset to map a terminal type of
- "dec-vt100" to "vt100", and the "-s" instructs tset to issue commands
- to reset the terminal type in the environment. (The later
- "-m 'network:?vt100'" instructs tset to prompt for a terminal type if the
- terminal type is initially set to "network", but to assume a default
- value of "vt100". This covers cases where the TELNET client I'm using
- at the time isn't reporting a terminal type; in some of those cases,
- I'm TELNET-ing in from an HP terminal that is not like a VT100 and so
- want to be able to specify a type of "hp".)
-
- Hope this helps! If you need additional help with this, feel free to
- e-mail me.
-
- -Frank McConnell, Product Engineering, The Wollongong Group
- <frank@twg.com>
-