Using Linux SUSE Leap 42.2 Main menu bar, "Next" (down arrow icon) action set to "goto next Unread" When mail is received it is marked as "New" (red envelope marker) In this case the next unread operation works, clicking goes to the next "New" message. If the messages are unread (blue envelope) rather than "new" then Next unread does not move onto the next unread message, the cursor just sits at the last message read / clicked on. Additionally: If you move out of the folder and into another folder in the tree, then click on next, it moves to the folder with the unread messages in it, and selects and displays the next unread. However it then reverts to not moving to the next unread if there are any. The operation seems to be even more confusing if there are unread messages in the folders below. It then seems to switch between the folders selecting first one unread in one folder then jumps to the previous folder and displays the first unread there. It appears that Next unread is not detecting that there are more unread in the current folder, but will detect that there are unread when it moves to a new folder then moves to the first unread there. Then it loses count and does not move to any more unread in that folder, after that it rescans the folders, finds unread in previous folders and jumps to the first unread there. This happens until there are no other unread messages in other folders when next unread stops working unless you manually select another folder.
'next unread' means the NEXT in the sequential list, it does not mean PREVIOUS. Use 'go to previous unread' for that.
This is most certainly happening here, and I think I've spotted what triggers it. (I noticed it in a newsgroup listing first, but it applies to normal mail folders as well) For some reason. probably due to me searching for something, the dates in the folder was set to be today at the top, older dates to the bottom. This seems to be the key to the problem. Claws seems to be associating the unread (blue envelope) with the date. It seems to assume that there are no more unread if the current message date is older than the newest (or today) Flip the date column to be oldest at the top and today at the bottom, and the next unread works as expected. Andy
(In reply to comment #1) > 'next unread' means the NEXT in the sequential list, it does not mean > PREVIOUS. Use 'go to previous unread' for that. Paul, apologies if I've not use bugzilla correctly (first time I've ever used it) , I reopened the bug and added some comments in the comment box there, I missed the little reply button on your response which I'm using now. I added a prev button to the tool bar and with the dates in reverse order they are indeed selected. (Talking about in the same folder here) This may be working as designed, but it does strike me as a little odd still. There might also be a danger of someone missing a mail as they would assume that there were no more unread if the indication did not move to another message. It was only because I saw more unread in the list that I noticed that no other messages were being selected. I then scanned through the folders looking for bold text indicating that there were unread and found quite a few. Fortunately they were all newsfeeds so on no great importance. To my thinking a next unread function should simply go the then next unread message in the list and disregard the sorting order on the dates, at least certainly within a folder. I can see the use of a next previous if someone reads one or two messages in a folder then skips to another folder and reads a few there, it's not the way I work, but it still seems risky in terms of missing something. Perhaps what is needed is a next (which disregards sorted orders, next forward and next previous. Again apologies if I've got hold of the wrong end of the stick on this. Andy
Even if you want to see it working differently that doesn't make it a bug. Familiarise yourself with the /View/Sort/... menu and the 'Message List' options on the /Configuration/Preferences/Display/Summaries page. If you want to discuss this further please use the users' mailing list. You can subscribe here: http://lists.claws-mail.org/cgi-bin/mailman/listinfo/users