| Age | Commit message (Collapse) | Author |
|
Parts that are not easy / useful to unit-test
|
|
Let's modernize a bit.
|
|
and improve logging.
|
|
|
|
|
|
Adapt to the new names / directory. Big commit, but mostly just very boring renaming.
|
|
|
|
Update all cc code using .clang-format; please do so as well for future PRs
etc.; emacs has a handy 'clang-format' mode to make this automatic.
For comparing old changes with git blame, we can disregard this one using
--ignore-rev
(see https://www.moxio.com/blog/43/ignoring-bulk-change-commits-with-git-blame )
|
|
compare subject from the *last* plus any spaces.
|
|
Should catch most cases.
Fixes: #2083.
|
|
Not only check for duplicate subjects in *siblings*, also recurse into
the children. This remove some clutter from deeply nested threads.
Fixes: #2078.
|
|
Calculate the thread subject, that is, the subject of the (sub)thread _or_
empty if it's the same as the previous subject.
This is for the UI feature of _not_ showing the subject when it's just
repeating from the previous.
|
|
And make it available in query_match, so we can expose it to elisp.
|
|
Even if a container has no query_match, it may still have children that need to
have flags applied.
This was broken by 6ff9829ce1e57e9f7fb4933d1389f4fd81dbd5dc.
Fixes: #1995
|
|
This avoid including unwanted messages in threaded results.
Also some cleanups.
|
|
Improve threaded sorting:
- rework the recursive algo (which should a crash noted earlier)
- sort by thread key (as in 1.5.7)
Fixes: #1923
Fixes: #1922
Fixes: #1911
Fixes: #1916
|
|
Ongoing... try to determine the thread-subject, to be used in mu4e
later.
|
|
And add some more tests.
|
|
Investigate this, seems to hit in the wild.
|
|
The assert failure was spotted in the wild... we need to investigate,
but we can ignore it now to avoid SIGABRT.
|
|
Rewrite the query machinery in c++:
- use an MSet decorator instead of the mu-msg-iter stuff
- use mu-query-decider to mark duplicates/unreadable/related messages
- use mu-query-threader to replace the older container/thread code
Algorithm did not substantially change, but the implementation details
did.
|