On 2013-03-05 22:19, Brian Schenkenberger, VAXman- wrote: Clem Cole <clemc at ccc.com> writes: try xterm.vt100.decTerminalID: 220 Which was my memory, I'd check to the sources for sure. Also, don't forget to restart X. The .Xresource stuff was always hokey and if things are not perfect, bad things happen. I've spent way more time than I want to think dealing with Xresource crap over the years (and b*tching at authors). Clem Doesn't make a bit of difference. Still doesn't give me DECDWL or DECDHL, and the debugger issue still persists. So, DECDWL and DECHDL are noted in the xterm documentation that it depends on your fonts. So unless you have an old version, or bad fonts, it should work. Does it work if you have it set to vt100? Not sure what the debugger issues were. Anyway, we might be beating on a dead horse here. It might that you're actually not that interested in getting this working, if you have another solution that do work for you. All I can say is that at my place, xterm do handle DECDWL and DECDHL just fine. 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