Johnny Billquist <bqt at softjar.se> writes: On 2013-03-05 21:33, Johnny Billquist wrote: On 2013-03-05 21:18, Brian Schenkenberger, VAXman- wrote: Clem Cole <clemc at ccc.com> writes: Yep. From the FAQ: The emulation level for xterm is set via the resource decTerminalID, *e.g.*, to 220 for a VT220. Once set, applications can set the emulation level up or down within that limit. DEC's terminals are configured in much the same way by a setup option. Yup... .Xresources has "decTerminalID: vt200" but that still doesn't excuse it for misbehaving as one. ;) It also doesn't do DECDWL or DECDHL when it's set for vt200. Note that the value should be set to "220", not "vt220", nor "vt200". And I should correct myself. Leading letters are ignored in decTerminalID, so vt220 works just as well as 220. However, vt200 will probably still not create the desired result. And you need the resource class or resource name in there as well, so just a plain decTerminalID in your x resources will not work right. I'll have to stop postin shorthand for you... XTerm.vt100.decTerminalID: vt200 -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG Well I speak to machines with the voice of humanity.