I'm running under KDE and if I use konsole everything is fine and this problem doesn't exist (so I suspect this is an xterm bug). If I "ssh root@somehost" under xterm, the remote shell doesn't have stty erase set to ^H. So if I run 'cat' and I press backspace I see ^H instead of the proper behavior. running stty erase ^H manually after login fixes it. If I don't log as root, like if I run "ssh user@somehost" everything is fine. This is reproducible on x86 and amd64, and the remote host doesn't need to be a gentoo system (so the xterm client side again seems suspect, ssh is less suspect because with konsole the problem doesn't happen). user@host1 ~ $ ssh root@host2 Last login: Sun Mar 11 14:16:11 2007 from host1.domain host2 ~ # stty speed 38400 baud; line = 0; -brkint -imaxbel host2 ~ # logout Connection to host2 closed. user@host1 ~ $ ssh user@host2 Last login: Sun Mar 11 14:24:01 2007 from host1.domain user@host2 ~ $ stty speed 38400 baud; line = 0; erase = ^H; -brkint -imaxbel user@host2 ~ $ Can anybody else reproduce this with xterm or am I the only one? Reproducible: Always Steps to Reproduce: 1.start xterm 2.ssh root@somehost 3.run cat and then backspace Actual Results: ^H is printed instead of erase being processed. Expected Results: backspace should be processed instead of seeing ^H on the screen
I found a solution, if it's a workaround or a fix it's up to you to decide. XTerm.backarrowKeyIsErase: true XTerm.ptyInitialErase: true That avoids xterm to set erase to ^H in the first place, and so everything is ok when logging remotely as root the erase returns to ^?. If it's a fix perhaps it's good idea to add it to the xterm app defaults so it'll actually work without having to tweak things by hand (I tried unmasking the latest ~amd64 xterm and that didn't fix it either). thanks.
Yes, I can reproduce this using x11-terms/xterm-225. Not our bug, though. Reassigning to X11.
I'm glad it wasn't a screwup on my side. My current functional settings (deviating from the default) are: XTerm.backarrowKeyIsErase: true XTerm.ptyInitialErase: true XTerm.vt100.metaSendsEscape: true The metaSendsEscape:true is needed so that the ALT key works as expected (that's unrelated to the backspace problem reported previously). They probably should become the new defaults.
I just bumped to xterm 231, have a look-see.
How's it work in 234? I just added it.
(In reply to comment #5) > How's it work in 234? I just added it. > And I've just added #243 and there has been no feedback here, closing as TEST-REQ.
