Bug 325016

Summary: read mail message view scrolling with jk keys does not work anymore
Product: [Applications] kmail2 Reporter: Lyse <kdebugs>
Component: UIAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: minor    
Priority: NOR    
Version: 4.10.5   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Lyse 2013-09-17 18:55:47 UTC 
Previously (Debian Stable (Wheezy), KMail Version 4.4.11) I could focus the read mail message view and use the vim-like keys [j] or [k] to scroll down or up the message. If I remember correctly I remapped the default shortcut [j] for "jump into folder" to something else. This jk scrolling worked both in the read mail message view below the mail list and the extra read mail message window. In the current version 4.10.5 pressing [j] or [k] does not do anything at all.

I know I can use the cursor keys, mouse wheel or mouse cursor to drag the scrollbar to scroll, but I really got used to jk scrolling and really miss this feature. Looking through the available shortcuts in the configure shortcuts window does not show me anything related to this.

Reproducible: Always

Steps to Reproduce:
1. select a long mail in the mail list where scrolling in the read mail messge view is possible
2. focus the read mail message view
2. press [j] to scroll
Actual Results:  
nothing happens

Expected Results:  
the mail message is scrolled down

I use KMail with the German language pack. In other programs like Akregator and Okular jk scrolling still works as expected.
Comment 1 Denis Kurz 2016-09-24 18:13:59 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:06:16 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.