Summary: | On Mailbox with various folders with unread mail "next unread" jumps to next folder with unread mail | ||
---|---|---|---|
Product: | Claws Mail (Windows) | Reporter: | tschweikle |
Component: | default | Assignee: | users |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | tschweikle |
Priority: | P3 | ||
Version: | 3.15.0 | ||
Hardware: | PC | ||
OS: | Windows 7 |
Description
tschweikle
2017-04-28 13:16:18 UTC
'next' is next, 'previous' is previous. You did not understand what I was writing?! Following: - three folders with unread mail. I'll call them A,B,C Now: A -- Unread 1 Unread 2 Unread 3 B -- Unread 1 Unread 2 Unread 3 C -- Unread 1 Unread 2 Unread 3 First time pressing "next unread" A -- read 1 unread 2 unread 3 B -- unread 1 unread 2 unread 3 C -- unread 1 unread 2 unread 3 Second time pressing "next unread" A -- read 1 unread 2 unread 3 B -- read 1 unread 2 unread 3 C -- unread 1 unread 2 unread 3 Third time pressing "next unread" A -- read 1 unread 2 unread 3 B -- read 1 unread 2 unread 3 C -- read 1 unread 2 unread 3 Fourth time pressing "next unread" A -- read 1 read 2 unread 3 B -- read 1 unread 2 unread 3 C -- read 1 unread 2 unread 3 Fifth time pressing "next unread" A -- read 1 read 2 unread 3 B -- read 1 read 2 unread 3 C -- read 1 unread 2 unread 3 ... Next is next. But I'd have had the intention going thru unread mail in folder A, then B, then C, not A1, B1, C1, A2, B2, C2, A3, B3, C3. When you say 'Selecting "next unread" will jump to next unread mail.' in comment #1, what menu item is it that you are a "selecting" Any chance you're sorting descending? Because then I would argue that 'next' is previous (by way of the infamous "sort order awareness"), and since there's no previous unread mail claws then continues to another folder... Hence my proposal[1] for an option to disable such "awareness" some time ago... [1] http://lists.claws-mail.org/pipermail/users/2017-March/018931.html Menu-item selected: "Ansicht -> Gehe zu ... -> Nächste ungelesene Nachricht" (View -> Go to ... -> Next unread message") And as one stated: Sort order: by date, descending It is right: setting sort order to "ascending" makes it behave as i am awaiting: going through all unread messages of one folder, then, after none are left going to the next folder with unread messages, starting at the first unread message (the oldest in this case). setting sort order to "descending" makes it behave as I never would think of: it jumps to the latest message in sort order, not the oldest unread, then I have to use "previous unread message" to jump to the next message, telling me no unread messages are left if I reach the last unread message within this folder and no other folder upwards has unread messages. To move to the next folder with unread messages I have to use "next unread message", within the folder I have to switch to "previous unread message" to scan through all messages within this folder. In my opinion "next unread message" should behave intuitively in all cases: * sort order "ascending": going to the top unread message in list, descending downward until no more unread messages are left, then continuing with the next folder in folder pane with unread messages. * sort order "descending": going to the last unread message in list, ascending upward until no more unread messages are left, then continuing with the next folder in folder pane with unread messages. For "previous unread message" the same: * sort order "ascending": going to the last unread message in list, ascending upward until no more unread messages are left, then continuing with the previous folder in folder pane with unread messages. * sort order "descending": going to the top unread message in list, descending downward until no more unread messages are left, then continuing with the previous folder in folder pane with unread messages. In short: - "next" in all cases means "next", as you would expect it. - "previous" in all cases means "previous", as you would expect it. regardless of displaying lists sorted "ascending" or "descending". As it is now, "next" and "previous" change meaning if you change sort order, because "next" doesn't do what would be correct in such cases: jump to the downmost message and not to the top message. As does "previous": jump to the downmost message, instead to the top one if sort order is descending. This could be overcome, if not using displaylist, but the sorted list to find the "next" or "previous" unread messages. BTW: "previous unread message" doesn't jump to the previous folder, if no more unread messages are in the current folder. "next unread message" does jump to the next folder if no more unread messages are in the current folder. (In reply to comment #5) > setting sort order to "descending" makes it behave as I never would think > of: it jumps to the latest message in sort order, not the oldest unread, > then I have to use "previous unread message" to jump to the next message, That's been fixed in GIT since the last release. |