Bug 309080 - Keyboard shortcuts for go-to different than in kmail and akregator.
Summary: Keyboard shortcuts for go-to different than in kmail and akregator.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: knode
Classification: Miscellaneous
Component: general (show other bugs)
Version: 4.11.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-27 09:22 UTC by Dirk Heinrichs
Modified: 2018-09-04 18:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Heinrichs 2012-10-27 09:22:00 UTC
Once upon a time, keyboard shortcuts for "go to" (for example "+" for "next unread") were the same in kmail, knode and akregator ("+"). Don't know exactly when this changed, but knode now uses other shortcuts. Please change those keyboard shortcuts back, so that they are consistant with kmail and akregator again.

Reproducible: Always

Steps to Reproduce:
1. kmail: Pressing + goes to next unread mail.
2. akregator: Pressing + goes to next unread article
3. knode: Pressing + goes to next group :(
Actual Results:  
Different behaviour in knode compared to kmail and akregator.

Expected Results:  
Same behaviour than kmail and akregator (as it was in the past).
Comment 1 Laurent Montel 2012-10-28 07:49:20 UTC
"Same behaviour than kmail and akregator (as it was in the past)." no was not changed in past.
I looked at code and it was it previous 2006 :)
Comment 2 Dirk Heinrichs 2012-10-28 07:59:45 UTC
(In reply to comment #1)
> "Same behaviour than kmail and akregator (as it was in the past)." no was
> not changed in past.
> I looked at code and it was it previous 2006 :)

OK, maybe I was wrong with that (but I could bet it once was the same :) ). But that doesn't change anything. Behaviour is inconsistant in knode compared to kmail and akregator, which is considered bad.
Comment 3 Andrew Crouthamel 2018-09-04 18:36:55 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I am closing this bug.