Version: unspecified (using KDE 4.6.1) OS: Linux I don't suppose this would be easy to implement but: Wouldn't it be nice if the same keybindings that you use when working with bash in a terminal did the same things in desktop applications? It would certainly result in me opening a lot less print dialogues and new windows. Additionally, I would argue that the "ctrl+f,ctrl+b,ctrl+p,ctrl+n" keybindings are superior than the standard "T-arrow" keys since they can be used without moving your hands out of standard typing position. The vi-navigation keys "hjkl" are also superior to the arrow keys, in my opinion. Arguably they're better than the emacs-style bash defaults, but for some reason I'm more comfortable with them emacs-style keys. Other keybinding that I'm a fan of include: ctrl+k/ctrl+y kill/paste (i could see ctrl+x staying in as "cut" which is different that "kill-line") ctrl+a "go to the end of the line" ctrl+e "go the beginning of the line" ctrl+s "search" ctrl+r "search-backwords" I'm sure other heavy terminal users might have a few others. I would suggest that existing conflicting shortcuts could perhaps be moved to "super-L" or "meta-L" shortcuts. I suppose there will be demand for this feature to be optional, as not all KDE users are familiar with the bash-like keybdindings (and vi users will want vi keybindings instead) but I would think that there would be a large number of users who would appreciate this as an optional feature. Thanks. Reproducible: Didn't try
> I'm more comfortable with them emacs-style keys Every user has its own preferred set of keys. That's the reason why the KDE Platform is very strong when it comes to configuring shortcuts. If you do not like the defaults, change them. Most shortcuts can be configured globally (System Settings > Shortcuts and Gestures > Standard Keyboard Shortcuts), or per application (Settings menu > Configure Shortcuts). The Kate text editor, to mention an example, allows configuring the cursor movement keys to whatever you like. If there is a specific bug, for example where an application does not respect the configuration or doesn't allow changing the defaults in the first place, please report the problem for each application separately. Regarding default assignments, remember that when you are assigning shortcuts you cannot assume a particular keyboard layout. A Dvorak user might be highly confused why the "cursor movement" is assigned to, say, T,F,G,V keys, or H,J,K,L keys. Most default shortcuts in KDE are chosen either because they are historically established (think X,C,V), or are mnemonics of simple English words, e.g. Ctrl+A means "select All", not "begin of line". Many users however, never change their key bindings. Changing the defaults will confuse or even annoy any user that got accustomed to the current default bindings, so we usually do not change defaults without a strong justification. With this in mind, I would like to close this entry as WONTFIX, in the hope that it won't discourage you to continue reporting issues or request enhancements, but keep it open to collect further opinions.
Heh see also Bug 225625. I actually think this might be reasonable to do at the plasma-integration level.
>If you do not like the defaults, change them. Please try changing them and report back and what specifically doesn't work to provide the setup you prefer.
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!