Bug 90516 - shift key no longer recognized as modifier to function keys
Summary: shift key no longer recognized as modifier to function keys
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: xemacs
Version: 9
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jens Petersen
QA Contact: Jay Turner
URL:
Whiteboard:
: 112977 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-05-09 06:08 UTC by Ivo Gough Eschrich
Modified: 2015-01-08 00:05 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2003-10-17 12:38:33 UTC
Embargoed:


Attachments (Terms of Use)

Description Ivo Gough Eschrich 2003-05-09 06:08:45 UTC
Description of problem:
I use the shift key as modifier to certain function keys to access emacs
functions. The key combinations are defined in .emacs aka .xemacs/init.el for
example: (global-set-key '(shift f9) 'query-replace)
The xemacs version shipped with RedHat 9 does not register the shift key as
a modifier.

Version-Release number of selected component (if applicable):
XEmacs 21.4 (patch 12) "Portable Code" [Lucid] (i386-redhat-linux, Mule) of Thu
Feb 20 2003 on porky.devel.redhat.com

How reproducible:
always, even if global-set-key directive is absent.

Steps to Reproduce:
1. open xemacs
2. type 'Ctrl-h k' to invoke key function dictionary
3. type 'Shift-f9' etc
    
Actual results:
xemacs returns info for f9, not Shift-f9

Expected results:
should return info for Shift-f9

Additional info:
switching off default gnome desktop shortcuts did not make a difference.
.Xmodmap is loaded and respected. .Xdefaults is ignored, however that should
not make a difference in my case.
have not tried running under KDE.

Comment 1 Jens Petersen 2003-05-19 08:43:08 UTC
Reproduced.

Comment 2 Jens Petersen 2003-10-17 12:38:33 UTC
Still present in xemacs-21.4.14.

Comment 3 Jens Petersen 2004-01-15 05:22:32 UTC
*** Bug 112977 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.