Version: 2.4.1 (using KDE KDE 3.4.3) Installed from: SuSE RPMs OS: Linux This seems to be related to 62644, but that's been closed since 2003... Bug is very easy to reproduce: go to Settings -> Configure Kate... -> Shortcuts dialog. Scroll down and click on Select To Previous Line, click in widget that says Shift+Up to invoke Configure Shortcut dialog. Press and hold Shift key, note that Shortcut displays as Shift+. While continuing to hold Shift key down, press up/8 on the numeric keypad (with NumLock disabled). Symptom: the shortcut display clears, there is a brief pause, then the Configure Shortcut dialog closes and the Select to Previous Line action now has no shortcut associated with it. Other weirdness that seems related: when moving the cursor in the edit pane, the numeric keypad buttons work as expected (e.g. 8 causes the cursor to move up 1 line). But when shift is held down, pressing any key on the numeric keypad causes the corresponding digit to be inserted at the cursor. Shift+numeric key should not insert a digit! That's what numlock is for.
If no one else is seeing this behavior, maybe it's my hardware? I'm running on an ancient P3-500 Compaq system. The keyboard is a Microsoft Internet model of fairly recent vintage.
Guess I submitted this before I was done thinking about it. :) My claim that "that's what numlock is for" may be too strong. Truthfully, I don't know what numlock is for...data entry I suppose. Whatever the default behavior of shift+num key however, it should be customizable by the user. I just checked the version of jedit on my system and it works correctly in this regard.
I experience the same odd behavior. I don't see how it can be a problem in kate though, we just process the key events we receive. And the texarea in konqueror into which i type this comment behaves similar, as does the kmail composer window. But I'm not really sure where to reassign to. Kdelibs I guess... Or is it a problem with Qt?
Could be an X issue if your mapping isn't really correct. Shift+Up in xev generates a KP_8 symbol here.
I'm an X-ignoramus so I can't say if it's an X issue or not. But I did install SuSE 10.0 on a second computer and the behavior is the same - and that's without doing any custom X configuration whatsoever. I selected KDE desktop during installation then let it run its course. Also, again note that jedit works correctly which indicates that whatever the problem is it's unlikely to be in any layer low enough to be shared between jedit and kate.
(In reply to Mike McAulay from comment #0) > Bug is very easy to reproduce: go to Settings -> Configure Kate... -> > Shortcuts dialog. Scroll down and click on Select To Previous Line, click > in widget that says Shift+Up to invoke Configure Shortcut dialog. Press and > hold Shift key, note that Shortcut displays as Shift+. While continuing to > hold Shift key down, press up/8 on the numeric keypad (with NumLock > disabled). > > Symptom: the shortcut display clears, there is a brief pause, then the > Configure Shortcut dialog closes and the Select to Previous Line action now > has no shortcut associated with it. I've tried to reproduce this with the latest kdelibs from git master and I cannot. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!