| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
In the common path, avoid building an unneeded std::string. This should
up in some profiles.
|
|
It's somewhat nice in some case, but not generally so; so let's not do
it.
|
|
Fix compiler warnings
|
|
Perform threading calculation on related set instead of entire result.
|
|
Without this commit clang++-7.0.1 whines
| CXX parser.lo
| parser.cc:138:15: warning: braces around scalar initializer [-Wbraced-scalar-init]
| return Tree({{Node::Type::Range},
| ^~~~~~~~~~~~~~~~~~~
|
|
Without this commit gcc-8.2.0 whines
| CC mu-msg-json.lo
| mu-msg-json.c: In function ‘get_temp_file_maybe’:
| mu-msg-json.c:254:14: warning: unused variable ‘tmpfile’ [-Wunused-variable]
| char *tmp, *tmpfile;
| ^~~~~~~
| mu-msg-json.c:254:8: warning: unused variable ‘tmp’ [-Wunused-variable]
| char *tmp, *tmpfile;
| ^~~
| mu-msg-json.c: In function ‘add_part_crypto’:
| mu-msg-json.c:276:21: warning: unused variable ‘s’ [-Wunused-variable]
| char *signers, *s;
| ^
| mu-msg-json.c:276:11: warning: unused variable ‘signers’ [-Wunused-variable]
| char *signers, *s;
| ^~~~~~~
| mu-msg-json.c: In function ‘each_part’:
| mu-msg-json.c:332:14: warning: variable ‘cid’ set but not used [-Wunused-but-set-variable]
| const char *cid;
| ^~~
and
| CC test-mu-str.o
| test-mu-str.c: In function ‘test_mu_str_subject_normalize’:
| test-mu-str.c:282:5: warning: initialization discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
| { "test123", "test123" },
| ^~~~~~~~~
| test-mu-str.c:282:16: warning: initialization discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
| { "test123", "test123" },
| ^~~~~~~~~
| test-mu-str.c:283:5: warning: initialization discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
| { "Re:test123", "test123" },
| ^~~~~~~~~~~~
| test-mu-str.c:283:19: warning: initialization discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
| { "Re:test123", "test123" },
| ^~~~~~~~~
| test-mu-str.c:284:5: warning: initialization discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
| { "Re: Fwd: test123", "test123" },
| ^~~~~~~~~~~~~~~~~~
| test-mu-str.c:284:25: warning: initialization discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
| { "Re: Fwd: test123", "test123" },
| ^~~~~~~~~
| test-mu-str.c:285:5: warning: initialization discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
| { "Re[3]: Fwd: test123", "test123" },
| ^~~~~~~~~~~~~~~~~~~~~
| test-mu-str.c:285:28: warning: initialization discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
| { "Re[3]: Fwd: test123", "test123" },
| ^~~~~~~~~
| test-mu-str.c:286:5: warning: initialization discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
| { "operation: mindcrime", "operation: mindcrime" }, /*...*/
| ^~~~~~~~~~~~~~~~~~~~~~
| test-mu-str.c:286:29: warning: initialization discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
| { "operation: mindcrime", "operation: mindcrime" }, /*...*/
| ^~~~~~~~~~~~~~~~~~~~~~
| test-mu-str.c:287:5: warning: initialization discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
| { "", "" }
| ^~
| test-mu-str.c:287:9: warning: initialization discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
| { "", "" }
| ^~
|
|
Consider all 'inline' text parts attachments too, unless they're
'text/plain' or something that looks like a signature.
It's a heuristic so we might get some new corner-cases.. let's see.
|
|
See #1261.
|
|
Follows mu_msg_to_sexp, but instead uses json as the output format,
using json-glib.
|
|
If it's available it will be used.
|
|
This makes it a bit easier to process the output.
|
|
Some mailing lists do _not_ set reply-to, see e.g.,
https://github.com/djcb/mu/pull/1278
In that case, use the 'List-Post' address instead, so the behavior is
the same (in mu4e) as for other mailing lists.
|
|
|
|
Fix a bunch of conflicts, tests.
|
|
Fixes #1292.
Note: does require rebuilding the mu database (--rebuild).
|
|
We got some errors when some of the key values exceeded the Xapian
maximum; in particular the message-id.
So make all the key-methods check, and truncate the message-id if
necessary.
|
|
The current threading algorithm is applied to the entire result of a query, even
if maxnum is specified, and then the result of the threading algorithm is
truncated to maxnum. The improves threading results by returning the entire
thread even when only a single message makes it into the top maxnum results.
This commit applies the threading algorithm to the related message set of the
maxnum-truncated query result instead of to the entire query result. For a given
set of messages, the set of messages which will share threads with any of the
original messages is exactly the related message sets. Put another way, either
any messages returned by the original query but removed by the maxnum truncation
will also be returned by the related message query, or they would not have been
needed anyway because they would not be members of any visible thread.
To maintain backward compatibility and allow threading to be used without
including related messages, the related message set is found for the threading
calculation, but any messages which would not have matched the original query
are then pruned, resulting in a superset of the truncated query, but a subset of
the untruncated query.
This does not improve (or degrade) the run time of a threading calculation when
maxnum is not set, but significant improves it when maxnum is set by making it
scale (roughly) linearly in terms of maxnum. On a maildir with ~200k messages
and maxnum set to 500 (the default), the run time of a threading calculation is
lowered from ~1m to ~0.1s.
Perform threading calculation on related set instead of entire result.
The current threading algorithm is applied to the entire result of a query, even
if maxnum is specified, and then the result of the threading algorithm is
truncated to maxnum. The improves threading results by returning the entire
thread even when only a single message makes it into the top maxnum results.
This commit applies the threading algorithm to the related message set of the
maxnum-truncated query result instead of to the entire query result. For a given
set of messages, the set of messages which will share threads with any of the
original messages is exactly the related message sets. Put another way, either
any messages returned by the original query but removed by the maxnum truncation
will also be returned by the related message query, or they would not have been
needed anyway because they would not be members of any visible thread.
To maintain backward compatibility and allow threading to be used without
including related messages, the related message set is found for the threading
calculation, but any messages which would not have matched the original query
are then pruned, resulting in a superset of the truncated query, but a subset of
the untruncated query.
This does not improve (or degrade) the run time of a threading calculation when
maxnum is not set, but significant improves it when maxnum is set by making it
scale (roughly) linearly in terms of maxnum. On a maildir with ~200k messages
and maxnum set to 500 (the default), the run time of a threading calculation is
lowered from ~1m to ~0.1s.
|
|
Ensure the resulting strings are \0-terminated.
|
|
It's not available for earlier versions.
|
|
We were transforming wild-card searches into regular-expression
searches; while that works, it's also significantly slower.
So, instead, special-case wildcards, and use the Xapian machinery for
wildcard queries.
|
|
With that flag it's possible to reconstruct the entire thread tree
structure in mu4e.
|
|
e.g. 21d / 2w are subject to DST; update the tolerance.
|
|
|
|
|
|
In the olden days, we stored dates like e.g. 20180131121234, and do a
lexicographical check. With that, we could use e.g. upper-limits
201802312359 for "all dates in Feb 2018", even if Feb doesn't have 31
days.
However, nowadays we use time_t values, and g_date_time_new_local raises
errors for non-existent days; easiest fix is to massage things a bit; so
let's do that.
Fixes issue #1197.
|
|
Attempt to restore building on Cygwin.
|
|
Allow for passing 'raw' queries to xapian, without any parsing.
|
|
Treat e.g. 'date:20170101' as 'date:20170101..20170101', just like
the Xapian parser does.
|
|
|
|
|
|
don't assume a 64-bit platform.
|
|
|
|
|
|
only match shortcuts when the field length was 1.
|
|
For now, don't treat "and not" specially; this gets us back into a
somewhat working state. At some point, we probably _do_ want to
special-case and_not though (since Xapian supports it).
|
|
|
|
Don't error out when asked for tickle docs.
|
|
This changed with the new parser.
|
|
casting error
|
|
add fast-path for (common) plain-ascii. fix silly static misuse.
should improve indexing with some single-digit percentage.
|
|
|
|
|
|
fix quoting issues with mu4e
|
|
|
|
don't require anything post c++14
|
|
Ensure there's no non-' ' whitespace, and no trailing/leading spaces.
|
|
|
|
|
