Bug 990215
| Summary: | Xterm SHIFT function keys not working | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | sqlflex <gm> |
| Component: | xterm | Assignee: | Miroslav Lichvar <mlichvar> |
| Status: | CLOSED NOTABUG | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.4 | CC: | gm, tpelka |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: Resource map interpreter now ignores lines where there
is a leading colon before the Shift function key definition
Consequence: Ignores line
Fix: Remove leading colon
Result: Works
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-02-05 14:01:46 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
The problem has been fixed. Apparently, the leading colons on each Shift function key definition line causes the line to be ignored. THis was not the case in all prior versions. Thanks for the update. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate, in the next release of Red Hat Enterprise Linux. I've looked into this more. It seems the translations are handled by the libXt library and the syntax is described here http://lesstif.sourceforge.net/doc/super-ux/g1ae03e/part1/appb.html The colon modifier apparently means to apply "any standard modifiers", e.g. shift and lock. I'm not sure why it worked before and doesn't now, but it seems to me colon shouldn't be used in your translation entries as shift is already specified there. Please reopen if you think this is a real bug (possibly in libXt). |
Description of problem: When I press SHIFT Function keys 1 – 8, xterm sends the sequence for F1 – F8 to my program rather than the sequences for F11 – F18 as defined in my resource map. I have been using the traditional method for mapping function keys 11 - 18 for at least 12 years on all flavors of Linux without a problem until now. Recently, I started evaluating 6.4 Redhat beta release and the traditional method no longer works. Version-Release number of selected component (if applicable): Redhat 6.4 beta release downloaded 7/30/13 How reproducible: Below is the xterm command that no longer works for shifted function keys. The function key sequence returned to my program is the same as if the SHIFT key was not pressed. xterm -xrm \ 'xterm*VT100.Translations: #override \n\ :Shift<Key>F1: string(0x1b) string("[23~") \n\ :Shift<Key>F2: string(0x1b) string("[24~") \n\ :Shift<Key>F3: string(0x1b) string("[25~") \n\ :Shift<Key>F4: string(0x1b) string("[26~") \n\ :Shift<Key>F5: string(0x1b) string("[28~") \n\ :Shift<Key>F6: string(0x1b) string("[29~") \n\ :Shift<Key>F7: string(0x1b) string("[31~") \n\ :Shift<Key>F8: string(0x1b) string("[32~") \n\ :~Shift<Key>F1: string(0x1b) string("OP") \n\ :~Shift<Key>F2: string(0x1b) string("OQ) \n\ :~Shift<Key>F3: string(0x1b) string("OR") \n\ :~Shift<Key>F4: string(0x1b) string("OS") \n\ :~Shift<Key>F5: string(0x1b) string("[15~") \n\ :~Shift<Key>F6: string(0x1b) string("[17~") \n\ :~Shift<Key>F7: string(0x1b) string("[18~") \n\ :~Shift<Key>F8: string(0x1b) string("[19~") \n\ :~Shift<Key>F9: string(0x1b) string("[20~") \n\ :<Key>Prior: string(0x1b) string("[S")' \ -e actflex menu M & Steps to Reproduce: 1. Run xterm command above without the actflex application program 2. While in the xterm session, press function keys to determine which key sequence are sent to the terminal. 3. Actual results: Pressing SHIFT F4 outputs the key sequence 'ESC O S' Expected results: The sequence that should be outputted is 'ESC [ 2 6 ~' Additional info: