VT100 specification
VT100 specification
I want to make my tty driver vt100 compatible, but I can't seem to find the specification anywhere - does anyone (a) have it or (b) know where to find it apart from a google search?
Re: VT100 specification
Hi,
Also AFAIK, most software that says it supports "VT???" actually doesn't - it supports a subset of "VT???" and/or a superset of "VT???" (for e.g. things like alternate character sets, double width and underline often don't work even though they are part of VT100, and things like ANSI colour codes sometimes do work even though they aren't part of VT100).
In the end, you may need to choose between true VT100 compatability, or software that actually works.
A good test is to see if your software works with HyperTerminal (when HyperTerminal is set to "VT100"). This is a good test for 2 reasons - a lot of people will probably want to use HyperTerminal because it comes with Windows; but also because HyperTermal really does suck (if your software works with HyperTerminal then it'll probably work on anything else that claims to be "VT100 compatible")...
Cheers,
Brendan
AFAIK the "VT???" standards relate to model numbers used for virtual terminals made by one company (Digital Equipment Corporation). There's a fairly good list of the original information on this web site.JamesM wrote:I want to make my tty driver vt100 compatible, but I can't seem to find the specification anywhere - does anyone (a) have it or (b) know where to find it apart from a google search?
Also AFAIK, most software that says it supports "VT???" actually doesn't - it supports a subset of "VT???" and/or a superset of "VT???" (for e.g. things like alternate character sets, double width and underline often don't work even though they are part of VT100, and things like ANSI colour codes sometimes do work even though they aren't part of VT100).
In the end, you may need to choose between true VT100 compatability, or software that actually works.
A good test is to see if your software works with HyperTerminal (when HyperTerminal is set to "VT100"). This is a good test for 2 reasons - a lot of people will probably want to use HyperTerminal because it comes with Windows; but also because HyperTermal really does suck (if your software works with HyperTerminal then it'll probably work on anything else that claims to be "VT100 compatible")...
Cheers,
Brendan
For all things; perfection is, and will always remain, impossible to achieve in practice. However; by striving for perfection we create things that are as perfect as practically possible. Let the pursuit of perfection be our guide.
-
JackScott
- Member
- Posts: 1036
- Joined: Thu Dec 21, 2006 3:03 am
- Location: Hobart, Australia
- Mastodon: https://aus.social/@jackscottau
- Matrix: @JackScottAU:matrix.org
- GitHub: https://github.com/JackScottAU
- Contact:
http://www.termsys.demon.co.uk/vtansi.htm
I'm guessing to find a complete listing of VT100 escape codes requires a call to DEC.
I'm guessing to find a complete listing of VT100 escape codes requires a call to DEC.
Or, one checks Wikipedia, with a link to this excellent site: http://vt100.net with amongst others:Yayyak wrote:I'm guessing to find a complete listing of VT100 escape codes requires a call to DEC.
Seriously guys, it's not that hard...vt100.net wrote:VT100 User Guide (EK-VT100-UG). This book is essential reading for anyone who wants to construct a VT100 emulator. If you use this as the specification and test your implementation with vttest, you won’t go far wrong.
JAL
