[Info-vax] Some questions on software for VMS 7.3 VAX
Johnny Billquist
bqt at softjar.se
Mon Jan 25 10:15:16 EST 2016
On 2016-01-25 15:38, lists at openmailbox.org wrote:
> Falling back to using the baked-in directory name it gets further
>
> [Spawning a new Kept EMACS]
>
> but I get a message for various emulated terminals that they aren't
> supported. For example coming in through Putty's telnet I get:
>
> emacs: Terminal type vt102-132 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.
>
> Using xterm and telnet I get a similar message:
>
> emacs: Terminal type vt100-132 is not defined.
>
> So I used the default xterm size and it also failed similarly:
>
> emacs: Terminal type vt400-80 is not defined.
>
> Do you know how to resolve the terminal issue? Looks like it's fairly close
> but there would still be the issue of how to make it globally available
> since the directory structure and names are baked-in...
>
> Thanks a lot for the help.
Why are you having the terminal width encoded into the terminal type?
The terminal type is independent of the width. A terminal like "vt100",
"vt200", "vt220", "vt400", and so on would be expected.
Something like "vt100-80" is just weird.
As for the actual width, in Unix as well as VMS, that is information
kept in the terminal device structures. (See stty for Unix, and SHOW
TERMINAL for VMS.)
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
More information about the Info-vax
mailing list