Bug 4245 - Allow sorting by thread number in addition to thread date
Summary: Allow sorting by thread number in addition to thread date
Status: NEW
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: UI/Message List (show other bugs)
Version: 3.17.5
Hardware: All All
: P3 enhancement
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2019-08-30 22:36 UTC by Alexander Harkness
Modified: 2019-09-19 13:28 UTC (History)
0 users

See Also:


Attachments
Patch to allow sorting by thread number in addition to thread date (7.15 KB, patch)
2019-08-30 22:36 UTC, Alexander Harkness
no flags Details | Diff
Patch to clean up summary comparison functions (11.22 KB, patch)
2019-08-30 22:39 UTC, Alexander Harkness
no flags Details | Diff

Description Alexander Harkness 2019-08-30 22:36:12 UTC
Created attachment 2006 [details]
Patch to allow sorting by thread number in addition to thread date

This allows effectively sorting by received-date of the last
message in each thread. Sorting by date leads to unexpected
behaviour sometimes, as some messages' Date headers are missing
or incorrect.
Comment 1 Alexander Harkness 2019-08-30 22:39:13 UTC
Created attachment 2007 [details]
Patch to clean up summary comparison functions

This is a patch that changes all summary comparison functions to have the requisite error checks and now behaviour is
consistent between the different comparison algorithms (unset is
now always counted as a maximal value for sorting). Comparison
functions never return 0 unless the two messages compared are in
fact the same.

This patch depends on the previous one, although trivially so. If I
should resubmit without the dependency, please let me know. Also, this
changes the existing behaviour of sorting by date - previously
messages (or threads) without date set were not placed in a well
defined position (although it would typically be at the bottom). Now,
such messages are placed at the top of the list to be consistent with
the other sorting methods.

Another thought I had about the sorting options - is sorting by date
really the right fallback option if comparison by the others fails.
If message ID is guaranteed to be present, sorting by it would
seem to be a better solution. Is that the case on all setups
though?

Note You need to log in before you can comment on or make changes to this bug.