Bug 58713
| Summary: | unexpected behaviour of Home and End keys in xterm | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Raw Hide | Reporter: | Leonid Kanter <leon> |
| Component: | XFree86 | Assignee: | Mike A. Harris <mharris> |
| Status: | CLOSED DUPLICATE | QA Contact: | David Lawrence <dkl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1.0 | CC: | ekanter |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2002-01-23 17:49:11 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: | |||
Description of Problem: Home and End keys produce wrong esc sequences in xterm Version-Release number of selected component (if applicable): 4.2.0-2.1 How Reproducible: always Steps to Reproduce: 1. open xterm and start mc in it 2. hit "Home" and than "End" buttons Actual Results: You'll see "H" and "F" characters in command line Expected Results: Pointer line must be moved to first and than to last line of file list in current mc panel. Additional Information: You can also type "cat /dev/tty", press Home and End and see wrong Esc sequenses ^[[H and ^[[F (must be ^[[1~ and ^[[4~). To fix the problem, following patch must be applied to XTerm app-defaults file: --- XTerm.orig Wed Jan 23 19:39:19 2002 +++ XTerm Wed Jan 23 19:39:33 2002 @@ -145,7 +145,7 @@ !This can be useful if you have an IntelliMouse. It maps the button !events generated by the wheel -*VT100*translations: #override \ +*VT100*Translations: #override \ <Key>Delete: string(0x1b) string("[3~") \n\ <Key>Home: string(0x1b) string("[1~") \n\ <Key>End: string(0x1b) string("[4~") \n\ see file attached to #49315 that fixes both current bug and #49315.