| Age | Commit message (Collapse) | Author |
|---|
|
|
|
a1d139de ("lib: add sexp: prefix to Xapian (infix) query parser.",
2022-04-09) introduced sfsexp infix queries. This requires the infix
preprocessor to be built in in a way which does not require sfsexp when
notmuch is built without it.
Make the preprocessor throw a Xapian error in this case (and fix the
build).
Signed-off-by: Michael J Gruber <git@grubix.eu>
|
|
The tarballs were requested by some distro-packagers, and this
automation will hopefully reduce the number of errors from the current
manual process.
|
|
The main change is to move the signatures to releases/ when invoking
the pre-release target; also stash the debian symlink for the release
target.
|
|
|
|
|
|
|
|
This is analogous to the "infix" prefix provided by the s-expression
based query parser.
|
|
Previously only singled stemmed terms were tested.
|
|
The previous source was renamed and a new binary generated in
commit 8723e707c15f7b435f07f5d5ea693496bb9769bb.
|
|
The test is fixed now.
|
|
The extra machinery to check for the actual output format is justified
by the possibility that distros may patch this newer output format
into older versions of gmime.
Amended-by: Michael J Gruber <git@grubix.eu>
Signed-off-by: Michael J Gruber <git@grubix.eu>
Amended-again-by: db
|
|
The goal is to generalize this to also check the output format of
g_mime_certificate_get_email.
|
|
|
|
We should fix this flaky test upstream, but for now, fix the build.
|
|
The some of the tests (and the library functions they exercise) that
rely on XDG_CONFIG_HOME also check XDG_DATA_HOME and MAILDIR.
|
|
Since Xapian does not preserve quotes when passing the subquery to a
field processor, we have to make a guess as to what the user
intended. Here the added assumption is that a string surrounded by
parens is not intended to be a phrase.
|
|
The heuristics in the field processor currently incorrectly trigger
phrase parsing.
|
|
Changing the width of a column requires rewriting all the rows.
|
|
This messes up whitespace, which will require a global change to fix.
|
|
The double remap is a bit ugly, but it seems better than adding
another layer of keymaps for those modes where notmuch-tag-undo makes
sense.
|
|
Keybindings are deferred to a future commit.
|
|
This buffer local list will be used to provide an undo facility for
tagging operations. Keeping history can be disabled with the new
OMIT-HIST option.
|
|
It is no slower (according to T06-emacs) to use batch for everything,
and it simplifies the code.
|
|
Time tag operations, to see if it is worthwhile keeping both the
batch and the non-batch calls to notmuch tag.
|
|
test_require_external prereq has to move to test-lib-common.sh, and
the new shell functions print_emacs_header and time_emacs are provided.
The somewhat indirect way of printing the output is to avoid the extra
"" present on string values from emacsclient.
|
|
T310-emacs is one of the largest and longest running sets of
tests. Splitting out the tagging operations will help maintainability
as well as potentially improve the parallel running time of the test
suite. Some slowdown in running the tests sequentially may result
since there is repeated setup.
|
|
This allows sharing more variable settings between the (correctness)
tests and the performance-tests. Unfortunately it seems a bit tricky
to move settings to test-lib-common.sh, as that is sourced late in
test-lib.sh, and moving it earlier breaks things.
|
|
If nothing else it means the mode is discoverable by browsing the
documentation, and also provides a target for links when enumerating
modes.
|
|
Originally contributed by Brian Sniffen [1]. Quite a few unpublished
fixes from Daniel Kahn Gilmour. We've been running it a few years now
as the "official" archive of the notmuch mailing list. There also a
few fixes from myself and Austin Ray. Finally I converted it to the
new python bindings.
This commit squashes the several years of development history and
moves it under devel, in recognition of the now established role it
plays in the project infrastructure.
[1]: id:87tvyvp4f2.fsf@istari.evenmere.org
|
|
In most cases used printf %s ... instead.
echo -n > file lines to create empty / truncate files were
changed to : > file lines, like done in in test-lib-emacs.sh
And one echo -n " " replaced with use of sed "s/^/ /" in next line.
|
|
The tradeoff is no bold/italic in the man pages to get actual
hyperlinks in the html output.
|
|
This is partially redudant given some existing cross references, but
it is useful to have all of the config keys listed in one place, to
help keep track of them if nothing else.
|
|
Increase discoverability.
|
|
Originally (I think) these were in the order generated by notmuch
setup. As the number of options grows, and several are not in the
initial setup generated file, the original order becomes less useful
for users. This commit alphabetizes the keys to help users
search. There is only one content change, an added cross-reference
from user.other_email to user.primary_email.
|
|
The idea is to do as little parsing and modification of the delivered
message as possible. Luckily the position of the "envelope header"
lets us escape it by replacing the first 5 characters of the stream
with a regular header name (with ':').
|
|
This helps maintainability and enables code-reuse of our home-brewed
buffered-write code.
This commit is mostly code movement.
|
|
It seems reasonable that notmuch should try to avoid delivering
messages in formats it cannot index.
|
|
This particular message is not recognized by notmuch as mail, but is
fine according to e.g. mutt. The trigger for this bad behaviour seems
to be a second "From " ocurring at the beginning of the line but
inside an attachment.
|
|
This returns all of the config keys with non-empty values, not just
those that happen to be stored in the database.
|
|
As of notmuch 0.34.2 [1], the python-cffi bindings make available the
configuration from both a config file and the database when accessing
Database.config like a dictionary. It is therefore confusing that the
iterator operations only work on the configuration information stored
in the database.
[1]: d7f95724132bf658fd151630185899737e2ed829
|
|
Prevent Emacs' mangling of quotes, which breaks the code sample.
|
|
Reduce chance of downstream packagers packing the wrong file.
|
|
Add the word "any" to the description of post-new hook description in
order to clarify that it is always run, even if there are no new
messages.
|
|
This is generated by configure and should not be committed.
|
|
|
|
|
|
|
|
These are my best guesses based on git commit messages.
|
|
|
