[Karmic] JED Home and End keys no longer work in CUA mode
Bug #445770 reported by
Roland Hughes
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| jed (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: jed
The CUA script says it is mapping Home and End keys to work appropriately, but they just don't work in Karmic Koala
roland@
2.6.31-11-generic
ProblemType: Bug
Architecture: i386
Date: Wed Oct 7 15:09:21 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelMo
Package: jed 1:0.99.18+dfsg.1-13
ProcEnviron:
LANGUAGE=
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: jed
Uname: Linux 2.6.31-11-generic i686
Revision history for this message
| Roland Hughes (original-seasoned-geek) wrote | #1 |
Revision history for this message
| Roland Hughes (original-seasoned-geek) wrote | #2 |
To post a comment you must log in.
I have tracked the problem back to one of the many device changes made with Karmic.
The default .jedrc file has the following lines in it:
#ifdef IBMPC_SYSTEM
LINENUMBERS = 2; % A value of zero means do NOT display line number on
#else % status line line. A value of 1, means to display
LINENUMBERS = 1; % the linenumber. A value greater than 1 will also
#endif % display column number information. I recommend a
% value of 2 only at high baud rates
When you run Jed under Karmic, you don't see the column numbers on the status line. That is because IBMPC_SYSTEM is not getting defined correctly during startup. All of the terminfo stuff doesn't appear to work. If IBMPC_SYSTEM was correctly defined, all of the keys would probably be correctly defined.