| Summary: | keyboard accelaration for 'move to folder' needs a confirmation step | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Tony Garland <tony3> |
| Component: | folder list | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WAITINGFORINFO | ||
| Severity: | wishlist | CC: | luigi.toscano, sreejiththulaseedharan |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
I really don't understand the problem. You can move to different folders using the arrow keys. When the correct folder is selected, press into to move the message there. Let's try again :-) When you have the preview pane disabled, and you are viewing a message body (not the header--the message itself is open in its own window), then all the normal keyboard accelerators of menu access of the main window, including short-cuts (like 'm' for move to folder) no longer operate because the focus is now in the opened message window. The opened message window has no menu items for previous/next/move to folder/etc. So in order to deal with the message: move to the next message or file it to a folder, you have to first <ESCAPE> to close the window. Most modern email readers allow a message to be disposed of directly when it is open--move to the next or previous, delete it, move it to a folder, etc. So what I'm saying is those of us who don't like using a restricted preview and want to read email messages in a full window of their own now have to close each message before we can do anything with deciding upon its destiny or moving to another message. This is extra work which is unnecessary. Woops! My response above was incorrect--it was regarding a different bug... sorry for my mistake. Now, recognizing the context of *this* bug, what I was mentioning is that when you use the hierarchical menu for moving messages (without using 'm' shortcut, but rather by using "message... move...") then keyboard accelerators are too quick to operate. Many of us who deal with lots of messages and folders don't want to have to repeatedly use arrow keys all the time to walk a long menu. That's what the shortcuts are supposed to do: for example, pressing 'k' to automatically move the the folder beginning with a 'k'. My point is that not only does it move to the associated folder, it also immediately moves the message there and closes the move operation--even if you pressed 'k' once to get to the first of several folders beginning with 'k' at that level in the hierarcy. What I'd prefer is for the keys (shortcuts) to work like arrow keys in that they would only *navigate* the menu but never finalize and initiate the move itself. That would require an additional <return>--just like when you use arrow keys to manually walk the menu tree. Thank you for your feature request. Kmail1 is currently unmaintained so we are closing all wishes. Please feel free to reopen a feature request for Kmail2 if it has not already been implemented. Thank you for your understanding. Instead of creating a new feature request, please confirm here if the wishlist is still valid for kmail2 |
Version: (using KDE 3.5.8) Installed from: Ubuntu Packages OS: Linux When using the keyboard to navigate within a hierarchical 'move to folder' tree, it would be helpful to support a mode where the move didn't immediately take action on the first matching key. For example, if you have a folder hierarchy something like: A folder B folder C folder D folder E folder1 E folder2 Then typing 'B' then 'D' then 'E' immediately moves the message to "E folder1" but you may actually want to move the message to "E folder2". In a situation like this where the last level has two or more folders with the same initial letter, it would be helpful if the first 'E' selected "E folder1" but an additional <Return> was necessary to confirm the move. This would allow typing another 'E' to select 'E folder2' if one wanted to select the following folder (and then <Return>) to make the move. In general, I'd like to see an option which says something like: [x] confirm move operations with <return> which always requires a final <return> key to initiate the move. When a person has lots of folders and a complex hierarchy, it is simply too easy right now to misfile the message while trying to work down a hierarchy using the keyboard. This would prevent that and allow a more careful placement, breaking the process up into two stages: 1. Stage 1: use the keyboard to work down to the target folder 2. Stage 2: initiate the move by typing <return>