notmuch/test, branch 0.28.2thread-based email index, search, and tagginghttps://git.notmuchmail.org/git/notmuch/atom?h=0.28.22018-09-28T23:22:42Zemacs: Call `notmuch-mua-send-hook' hooks when sending a message2018-09-28T23:22:42ZDavid Edmondsondme@dme.org2018-09-25T15:09:10Zurn:sha1:e8cb6b2cd63c9ea8a011cb9f672baf04b4c14f7b
Previously any hook functions attached to `notmuch-mua-send-hook' were
ignored.
test: Check that `notmuch-mua-send-hook' is called on sending a message2018-09-28T23:22:33ZDavid Edmondsondme@dme.org2018-09-25T15:09:09Zurn:sha1:4e213fe9b4332deb3f11f1dbc71cbdd47a8a1525test: make regexp test conditional on field processors2018-09-14T11:54:20ZDavid Bremnerdavid@tethera.net2018-09-10T01:36:17Zurn:sha1:c846e15ffee526b70a28b512710968b2db77b724
Normally we'd mark it broken, but perversely missing regexp support
actually makes the test pass.
test: mark thread subqueries broken without field processors2018-09-14T11:54:09ZDavid Bremnerdavid@tethera.net2018-09-10T01:36:16Zurn:sha1:c6ba5522a5c44312c140b5f61c5a0e011fdf94b2
Currently these tests just fail when notmuch is built against Xapian
1.2.x
test: Absolute and relative directory paths.2018-09-08T23:19:42ZDavid Edmondsondme@dme.org2018-09-08T11:49:41Zurn:sha1:4cd5a0a3d5416fd4601f2c14da0845fee5d9ede1lib: change parent strategy to use In-Reply-To if it looks sane2018-09-06T11:07:13ZDavid Bremnerdavid@tethera.net2018-08-30T11:29:15Zurn:sha1:87934c432c4bee9df09f268a3f05933c59c2caf1
As reported by Sean Whitton, there are mailers (in particular the
Debian Bug Tracking System) that have sensible In-Reply-To headers,
but un-useful-for-notmuch References (in particular with the BTS, the
oldest reference is last). I looked at a sample of about 200K
messages, and only about 0.5% these had something other than a single
message-id in In-Reply-To. On this basis, if we see a single
message-id in In-Reply-To, consider that as authoritative.
lib: add _notmuch_message_id_parse_strict2018-09-06T11:07:13ZDavid Bremnerdavid@tethera.net2018-08-30T11:29:14Zurn:sha1:b31e44c678bf3bfe81bcc5f159e627551f12700f
The idea is that if a message-id parses with this function, the MUA
generating it was probably sane, and in particular it's probably safe
to use the result as a parent from In-Reply-to.
test/thread-replies: mangle In-Reply-To's2018-09-06T11:07:13ZDavid Bremnerdavid@tethera.net2018-08-30T11:29:12Zurn:sha1:35053c2b9af0eb7ce5bd612c642163275490513a
In a future commit, we will start trusting In-Reply-To's when they
look sane (i.e. a single message-id). Modify these tests so they will
keep passing (i.e. keep choosing References) when that happens.
test: add known broken test for good In-Reply-To / bad References2018-09-06T11:07:13ZDavid Bremnerdavid@tethera.net2018-08-30T11:29:11Zurn:sha1:ea08032ae40119b24ef22c1c30aaf631cda02dd0
The current scheme of choosing the replyto (i.e. the default parent
for threading purposes) does not work well for mailers that put
the oldest Reference last.
lib/thread: change _resolve_thread_relationships to use depths2018-09-06T11:07:13ZDavid Bremnerdavid@tethera.net2018-08-30T11:29:10Zurn:sha1:46dce33abc82ea6ebd3be2e0887506af4185c739
We (finally) implement the XXX comment. It requires a bit of care not
to reparent all of the possible toplevel messages.
_notmuch_messages_has_next is not ready to be a public function yet,
since it punts on the mset case. We know in the one case it is called,
the notmuch_messages_t is just a regular list / iterator.