![]() Registered Member ![]()
|
Is it possible to configure kmail such that it
- does not select (and load) another message after one deletes a message or set of messages? - does not change the selection (whether it be message or mailbox) when right-clicking on an item, for instance to delete a (big) message without downloading it first? AFAIK the IMAP protocol allows to do such things. - uses a focus concept for at least message list and message viewer panes, such that after one selects a given mailbox, one can navigate the messages therein with the cursor keys (and make extended selections holding the Shfit key)? Currently kmail selects/opens the last read message when I select a mailbox, and the cursor keys allow me to navigate that message. It is more efficient for me to be able to select messages of interest (and even more, select all NOT of interest to trash them) without having to use the trackpad. Would there be any interest in such features if they don't exist yet, and if so, how/where best to propose them? I'm not sure that diving into an undoubtedly highly complex and mature existing project would be a good way for me to get acquainted with KDE programming... |
![]() Administrator ![]()
|
You can at least configure the behavior partially, under Configure KMail > Misc, you can select a number of behaviors under "When opening a folder:".
I'm not sure if it's possible, but bear in mind that KMail does not handle the specifics of an account type or another, the underlying PIM subsystem does. It may be worth posting a wishlist on bugs.kde.org but bear in mind that the message view / list of KMail is one complex piece of code.
"Violence is the last refuge of the incompetent."
![]() Plasma FAQ maintainer - Plasma programming with Python |
![]() Registered Member ![]()
|
I didn't see an option NOT to select another message. I opted for selecting the previously selected message, but it happens that's a rather old one which causes the message list to scroll back so much one no longer sees the new messages.
PIM handles the specifics, but it's kmail that asks it what to do, no? Anyway, kmail is part of kdepim, so it shouldn't be a problem if a feature requires changes in code that's not part of kmail itself, right? ![]() |
Registered users: Baidu [Spider], Bing [Bot], Google [Bot]