| |||||||||||||
wlterm: the native Wayland terminal emulatorwlterm: the native Wayland terminal emulatorPosted Sep 27, 2012 15:30 UTC (Thu) by bkw1a (subscriber, #4101)Parent article: wlterm: the native Wayland terminal emulator
How does it do with "vttest"?:
(Log in to post comments)
wlterm: the native Wayland terminal emulator Posted Sep 27, 2012 16:00 UTC (Thu) by dvdhrm (subscriber, #85474) [Link]
wlterm actually uses TSM as terminal-emulator. It emerged out of kmscon while I was looking for a terminal-emulator-library that is independent of any graphics-libraries and which does not render anything but only does vt-emulation. I didn't find one so I started TSM which is developed in-tree with kmscon and wlterm.
vt220 is almost fully supported and many extended feature are also available, but it doesn't pass all vttest tests. Things like double-width/height lines are still missing, but these are also rarely used today. Main focus was on making vim/emacs/mc/etc. work correctly (which currently do) and now we try to get full compliance to nearly all xterm features. But vttest is used heavily for testing.
wlterm: the native Wayland terminal emulator Posted Sep 27, 2012 16:00 UTC (Thu) by Yorick (subscriber, #19241) [Link]
Isn't it time we stopped regarding vttest as the arbiter of terminal "emulator" correctness? It's in many ways an impressive and useful program, but its existence has caused much programming effort being wasted in the pursuit of a perfect vttest "score" — be it VT-52 mode, DEC line drawing characters, tab stop setting, double-wide characters, answerback messages, and other useless features. (I know, because I have been one of those programmers. I'm better now, thank you.)
Some of these "mandated" features are actually negative, as they make it too easy to get the terminal into a broken state, or can be outright security holes.
wlterm: the native Wayland terminal emulator Posted Sep 27, 2012 16:42 UTC (Thu) by butlerm (subscriber, #13312) [Link]
Personally, I would be happy if in our advanced state of civilization, we could simply get reliable handling of the backspace key. That seems to be a problem in a lot of circumstances. SSH from cygwin, for example.
wlterm: the native Wayland terminal emulator Posted Sep 29, 2012 7:07 UTC (Sat) by quanstro (guest, #77996) [Link]
i'd be happy if we stopped emulating terminals,
complete with baud rate and other anachronisms.
wlterm: the native Wayland terminal emulator Posted Sep 27, 2012 16:22 UTC (Thu) by mpr22 (subscriber, #60784) [Link] The second sentence of the first paragraph of the synopsis is sufficient to persuade me that even if vttest is a useful and effective program, it needs to be either replaced, or forked by someone who doesn't laud knowledge-hiding.
wlterm: the native Wayland terminal emulator Posted Sep 27, 2012 19:28 UTC (Thu) by josh (subscriber, #17465) [Link]
That sentence doesn't strike me as endorsing knowledge hiding, so much as not wanting to maintain a duplicate (and likely outdated) description of the tested functionality beyond that embodied in the source code. A quick look at the xterm ctlseqs document will typically provide enough information to fix a vttest failure.
wlterm: the native Wayland terminal emulator Posted Sep 27, 2012 19:43 UTC (Thu) by bkw1a (subscriber, #4101) [Link]
Thanks for pointing out the ctlseqs.txt document:
http://invisible-island.net/xterm/ctlseqs/ctlseqs.txt
If I ever knew about it, I'd forgotten. I think it's interesting that all of the tektronix and vt52 stuff is only the last 6% or so of this long file.
|
|||||||||||||