On 30.12.2017 16:35, Greg Troxel wrote: > > Kamil Rytarowski <n54%gmx.com@localhost> writes: > >> How to setup correctly vt100 in a terminal? >> >> I've set exported TERM=vt100, called tset and stty and I keep observing >> artifacts. >> >> I was trying to run http://invisible-island.net/vttest/ and it does not >> work well. >> >> I've tested py-terminator and xterm with the same results. >> >> I'm working around the problems with vt100 with putty right now and this >> program works well. > > The VT100 had a specific series of escape sequences. Memory is fuzzy on > timing/ordering, but we ended up with an ANSI standard for terminal > escape sequences that is mostly the same as VT100. There are some DEC > things in vt100 but not ANSI, and later ANSI grew color support (VT100, > VT220, VT320 are monochrome) > > xterm tries to implement the ansi sequences, more or less. I am not > aware of a way to make it be exactly vt100. > Are the ANSI sequences conflicting with DEC VT100? > So if you want a true VT100 emulation, you will either have to tell > xterm to be faithful to vt100 (TERM=vt100 tells programs to generate > vt100 codes), or find some other terminal emulator which is switchable. > How to do it? I've tried to export TERM=vt100 without success. > What are you really trying to accomplish? Are you looking to see if > our xterm has bugs? > I'm attempting to login to OpenVMS and it's breaking the screen with vt100 sequences. Command line mostly works, but editors and other programs aren't usable. I've only managed to login to the machine and get sane output with putty, but it's not a convenient terminal of mine - I want to use py-terminator.
Attachment:
signature.asc
Description: OpenPGP digital signature