Bug 160354
| Summary: | backspace key in vim running from xterm returns ^? | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tom Mount <tmount> | ||||
| Component: | xterm | Assignee: | X/OpenGL Maintenance List <xgl-maint> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 4 | CC: | ccradu, covex, ctilburg, hdegoede, jsutton1027, mstevens, njl, noa, ra, spacewar, zing | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i686 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2005-09-24 10:36:50 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Tom Mount
2005-06-14 16:37:14 UTC
I verified this problem with a clean install of FC4. In addition, the problem also exists when ssh'ing into a different box and running vi. For example, I'm on a FC4 box, with an xterm open, and I ssh user.foo, and I start editing a doc in vi, the same problem exists. Same problem here, with a fresh new install. Sounds like an inputrc problem. cheers You can add the following line to the file .Xdefaults *ttyModes: erase ... or wait for someone to fix bug 155538 Adding to .Xdefaults didn't work for me. Nevertheless, this is working here :
add
*ttyModes: erase ^?
to
/usr/X11R6/lib{,64}/X11/app-defaults/XTerm
(as explained in 155538. Thank you Nick.
adding that line as referenced in the previous post also fixed the problem here too (both at the machine, and over ssh). Perhaps this should be patched, and an update for xterm should be released. (In reply to comment #5) > Adding to .Xdefaults didn't work for me. Nevertheless, this is working here : > add .Xdefaults hasn't been supported by XFree86 or Xorg for 5 years or so. The correct file is ~/.Xresources HTH This is also problem in man find function (/). In vim :help fixdel is how to fix that either for vim only or this note: "Note about Linux: By default the backspace key produces CTRL-?, which is wrong. You can fix it by putting this line in your rc.local: > echo "keycode 14 = BackSpace" | loadkeys" Created attachment 116272 [details]
patched XTerm file
Comment on attachment 116272 [details]
patched XTerm file
path should be /usr/X11R6/lib/X11/app-defaults/
*** Bug 162549 has been marked as a duplicate of this bug. *** I'm also seeing this bug on a FC3->FC4 upgrade. The xterm*ttyModes: erase ^? workaround fixes it. I'm also seeing this bug on a FC3->FC4 upgrade. The xterm*ttyModes: erase ^? workaround fixes it. *** Bug 163812 has been marked as a duplicate of this bug. *** The problem is NOT xterm, is that the /etc/termcap entry for xterm is not synchronized with terminfo entry (look at the "kb" value). The fix is to replace "kb=^H" with "kb=^?" in /etc/termcap, for the "xterm-basic" entry (which is included by xterm, through xterm-old). To verify: "infocmp xterm | grep kbs" displays "kbs=\177". Probably this bug should be assigned to the termcap maintainer. (Please make sure that the xterm-256color entry is also fixed) To comment #15: Yes, you are right. This is a bug in termcap. I have received this as Bug #166702. Fixed in termcap 5.4 Rel.5. Petr Raszyk *** This bug has been marked as a duplicate of 155538 *** I think this actually was a dup of Bug #166702 (termcap) and not Bug #155538 The new package from #166702 has completely resolved the issue for me on fc4. From User-Agent: XML-RPC xterm-205-1.FC4 has been pushed for FC4, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report. From User-Agent: XML-RPC xterm-205-1.FC4 has been pushed for FC4, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report. |