In article ,
"Tom Linden" writes:
>
> I use PuTTY v53.b from W2k to connect using SSH2 to a VMS7.3-2 machine
> and then
> DECnet to a VMS7.3-1 machine where I run emacs 19.22
>
> When I try to run emacs I get
>
>
> NORNS> emacs -nw FOO.TXT
> [Spawning a new Kept EMACS]
> emacs: Terminal type vt102-80 is not defined.
> If that is not the actual type of terminal you have,
> use the Bourne shell command `TERM=... export TERM' (C-shell:
> `setenv TERM ...') to specify the correct type. It may be necessary
> to do `unset TERMCAP' (C-shell: `unsetenv TERMCAP') as well.
> [Attached to DCL in directory $7$DKA0:[TOM]]
>
>
> Now in the TERM dir there is
>
> VT100.ELC;1 VT102.EL;1 VT125.EL;1 VT200.EL;1
> VT200.ELC;1 VT201.EL;1 VT220.EL;1 VT240.EL;1
>
> NORNS> type VT102.EL
> (load "term/vt100" nil t)
>
> Is the problem that the above lisp file is not byte compiled?
> Who is claiming that it is VT102-80, PuTTY?
>
> SHO TERM/FULL doesn't supply that form of designation.
>
> I also tried just copying VT102.EL to VT102-80.EL under the obvious theory
> to no avail.

Why not just type SET TERM/VT100

Works for me running VIM on VMS.

Or possibly change your "terminal type string" in Putty, but I have
never played witht that. I would guess the problem is that there is
really no such terminal type as VT102-80.

bill

--
Bill Gunshannon | de-moc-ra-cy (di mok' ra see) n. Three wolves
bill@cs.scranton.edu | and a sheep voting on what's for dinner.
University of Scranton |
Scranton, Pennsylvania | #include