[Bug 415150] [NEW] NumLock mapping and KeyPad mode for VT420 emulation
seasoned_geek
roland at logikalsolutions.com
Tue Aug 18 00:56:12 UTC 2009
Public bug reported:
I guess this is really a "feature request" since it has been hanging out
there for a long time.
NumLock isn't correctly handled by konsole. When NumLock has been
mapped via keyboard mapping, like it should be in the VT420 keyboard
mapping, konsole must cease eating it as an "application mode toggle
key". All of the mechanics are now in the environment to map NumLock to
\EOP in the VT420 keypad layout. What is missing is the ability to tell
konsole that it must use a different key to toggle the keypad from
numeric to application mode. Indeed, when you are connected to an
actual OpenVMS system (what the VT series terminals where actually
created to work with) the OS sends the escape sequence to do the
switching, it cannot be done at the keyboard level. konsole correctly
consumes this escape sequence, but it doesn't have any logic inside of
it to say "if NumLock mapped don't use for toggle"
It would seem a reasonable solution to have that portion of the
application which loads the keyboard map set a flag indicating the
NumLock key has been mapped. At whatever place in the code where it
checks for NumLock key to do the toggle it should toggle only if NumLock
and !NumLockMapped
Description: Ubuntu karmic (development branch)
Release: 9.10
** Affects: kdebase (Ubuntu)
Importance: Undecided
Status: New
--
NumLock mapping and KeyPad mode for VT420 emulation
https://bugs.launchpad.net/bugs/415150
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase in ubuntu.
More information about the kubuntu-bugs
mailing list