| Age | Commit message (Collapse) | Author |
|---|
|
If the database path specified in the configuration file does *not*
start with a /, presume that it is relative to $HOME and modify the
path used to open the database accordingly.
|
|
[dgit --overwrite]
|
|
In current Debian sid / testing, emacs25 is a transitional package,
and emacs-gtk, emacs-lucid, and emacs-nox are the real packages.
Emacs 23 is not available in emacs after oldoldstable.
|
|
We should probably not git://, and it needs a branch to not confuse
e.g. vcswatch.
|
|
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.
|
|
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.
|
|
It's only few lines, but we already define the function, so make it
usable elsewhere
|
|
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.
|
|
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.
|
|
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.
|
|
This is part 1/2 of changing the reparenting of alleged toplevel
messages to use a "deep" reference rather than just the first one
found.
|
|
This will be used in reparenting messages without useful in-reply-to,
but with useful references
|
|
This is mainly to lay out the structure of the final code. The problem
isn't really solved yet, although some very simple cases are
better (hence the fixed test). We need two passes through the messages
because we need to be careful not to re-parent too many messages and
end up without any toplevel messages.
|
|
This is a review suggestion [1] of Tomi. I decided not to squash it
so that the code movement remains clear.
[1]: id:m2pnxxgf5q.fsf@guru.guru-group.fi
|
|
This is not a complete win in code-size, but it makes the code (which
is about to get more complicated) easier to follow.
|
|
There is no public notmuch_message_list_t public interface, so to this
is added to the private API. We use it immediately in thread.cc;
future commits will use it further.
|
|
This is analogous to DEBUG_DATABASE_SANITY, and is intended to help
debugging and to help users submit bug reports.
|
|
The plan is to use these in resolving threads.
|
|
For non-root messages, this should not should anything currently, as
the messages are already added in date order. In the future we will
add some non-root messages in a second pass out of order and the
sorting will be useful. It does fix the order of multiple
root-messages (although it is overkill for that).
|
|
This documents the bug discussed at
id:87efgmmysi.fsf@len.workgroup
The underlying issue is that the reply to a ghost (missing) message is
falsely classified as a root message in _resolve_thread_relationships.
There are two pairs of tests; in each case the the first test is
simpler / more robust, but also easier to fool.
|
|
There are 3 threads here, two synthetic, and one anonymized one using
data from Gregor. They test various aspects of thread
ordering/construction in the presence of replies to ghost messages.
|
|
This clarifies that the breakage seen with Xapian 1.4.6 does not have
to do with "funny" tags.
This test is "known broken", but only with xapian 1.4.6, and there's
curently no convenient way to mark that.
|
|
Use GMime functionality to detect mislabeled messages and apply the
correct (Windows) encoding instead.
|
|
Messages that contain Windows-1252 are frequently mislabeled as ISO
8859-1, which may result in non-printable characters when displaying
the message. The test asserts that such characters (in this case
curved quotes) are displayed correctly.
|
|
On some platforms (e.g. macOS), it is necessary to add a real sentinel
process for the error buffer used by `notmuch-start-notmuch' rather
than a no-op sentinel.
|
|
|
|
* Add texinfo as a build-dep, build info version of documentation.
[dgit import unpatched notmuch 0.27-2]
|
|
[dgit import tarball notmuch 0.27-2 notmuch_0.27-2.debian.tar.xz]
|
|
This is needed to provide a makeinfo binary, to build the info version
of the documentation.
|
|
Many of the manpages didn't treat literal text as literal text. I've
tried to normalize some of the restructured text to make it a bit more
regular.
several of the synopsis lines are still untouched by this cleanup, but
i'm not sure what the right way to represent those is in .rst,
actually.
In particular find that if i rebuild the manpages, sometimes i end up
with some of the synopsis lines showing – (U+2013 EN DASH) where they
should have -- (2 × U+002D HYPHEN-MINUS) in the generated nroff
output, though i have not tracked down the source of this error yet.
|
|
|
|
make the source slightly easier to read. no functional change.
|
|
Make printmimestructure work in python3 as well as python2.
|
|
As usual, one notices these *after* release(s).
|
|
notmuch 0.27 release
|
|
|
|
|
|
[dgit import orig notmuch_0.27.orig.tar.gz]
|
|
|
|
Help users find this new indexed-cleartext workflow.
|
|
notmuch 0.27~rc1 release
|
|
|
|
|
|
If e.g. /lib is a link to /usr/lib, then the latter may not show up in
the way we expect in the output of ldconfig. 'test foo -ef bar' checks
if foo and bar have the same device and inode numbers. Since (at least
in bash, dash, ksh, and zsh) the shell dereferences symlinks before
applying the test, this includes both the case where file1 is equal to
file2 and the case where one is a symlink to the other.
|
|
|
|
|
|
|
|
We want to give people some heads up before dropping support, since
removing a bunch of ifdefs will be a pain to revert.
|
|
add two new API symbols
|
|
No content yet.
|
