| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
It seems important to give the numeric return code for people writing
scripts. Hopefully deviations from this convention are rare.
|
|
We want to be able to query the properties directly, like:
notmuch count property:foo=bar
which should return a count of messages where the property with key
"foo" has value equal to "bar".
|
|
This somewhat mimics the config line parsing, except there can be
arbitrarily many key value pairs, so one more level of looping is
required.
|
|
Part of providing extensibility via properties is to make sure that user
data is not lost. Thus we need to be able to dump and restore
properties.
|
|
|
|
In particular add notmuch-compact(1) (Debian bug #825884)
|
|
To look the same as commit b8a136187a3b changed it in emacs MUA code.
|
|
sphinx-build emits a minor warning:
[...]doc/man7/notmuch-search-terms.rst:223: WARNING: Block quote ends without a blank line; unexpected unindent.
And the tabular representation of boolean or probabilistic prefixes
currently renders like this when i view it in man:
┌───────────────────────────┬────────────────────────────┐
│Boolean │ Probabilistic │
└───────────────────────────┴────────────────────────────┘
│ tag: id: │ from: to: │
│ │ │
│ thread: folder: │ subject: attach‐ │
│ path: │ ment: mimetype: │
└───────────────────────────┴────────────────────────────┘
This isn't just ugly: it's confusing, because it seems to imply that
some of the prefixes in the left-hand column are somehow related to
specific other prefixes in the right-hand column.
The Definition List representation introduced by this patch should be
simpler for readers to understand, and doesn't have the warning.
|
|
This was introduced with the libconfig changes, but not documented then.
|
|
Many of the external links found in the notmuch source can be resolved
using https instead of http. This changeset addresses as many as i
could find, without touching the e-mail corpus or expected outputs
found in tests.
|
|
Without this patch, i'm seeing sphinx-build emit:
[...]doc/man1/notmuch-emacs-mua.rst:: WARNING: document isn't included in any toctree
|
|
This relies on the optional presense of xapian field processors, and the
library config API.
|
|
Most of the infrastructure here is general, only the validation/dispatch
is hardcoded to a particular prefix.
A notable change in behaviour is that notmuch-config now opens the
database e.g. on every call to list, which fails with an error message
if the database doesn't exit yet.
|
|
The default to restore config data seems safest, especially since
currently we have no config data to mess up.
|
|
Note that it changes the default dump output format, but doesn't break
existing notmuch-restore. It might break user scripts though.
|
|
This is intentionally low tech; if we have more than two options it may
make sense to build up what infrastructure is provided.
|
|
This relies on the FieldProcessor API, which is only present in xapian
>= 1.3.
|
|
Yes, it is 2016
|
|
Current documentation and comments in the code do not correspond to
the actual code and tests in the test suite ("Un-munging Reply-To" in
T230-reply-to-sender.sh). Fix it.
|
|
<since> and <until> for the lastmod: prefix right below the date:
prefix description give the impression one could use last modified
dates to lastmod: which is not at all the case. Use
<initial-revision>..<final-revision> instead.
|
|
Now it is accurate and provides more information to the
reader of the documents.
|
|
Before this change with --auto-daemon but without --create-frame
emacs server was started but no clients stay connected to it
(in both graphical and terminal displays).
Note that this changes how --client --auto-daemon works on
graphical display; New emacs frame is now created for the
message (and message-exit-actions hook appended).
|
|
Make the default behaviour for --client the same as emacsclient
default: do not create a new frame. Add a new option --create-frame,
passing the same option to emacsclient to create a frame.
|
|
Automatically starting Emacs in daemon mode if the Emacs server is not
running is a matter of preference better not hard coded in
notmuch-emacs-mua. Add an option to control the behaviour.
|
|
Move --client description to a more suitable location, stylistic
changes.
|
|
The order of the results with --output=count and --deduplicate=address
are unspecified as they're based on a hash table traversal. This being
the case, optimize the query by explicitly requesting unsorted
results. Clarify the documentation accordingly.
|
|
Document the deduplication based on case insensitive address.
|
|
It doesn't seem likely we can support simple date:<expr> expanding to
date:<expr>..<expr> any time soon. (This can be done with a future
version of Xapian, or with a custom query query parser.) In the mean
time, provide shorthand date:<expr>..! to mean the same. This is
useful, as the expansion takes place before interpetation, and we can
use, for example, date:yesterday..! to match from beginning of
yesterday to end of yesterday.
Idea from Mark Walters <markwalters1009@gmail.com>.
|
|
Document the deduplication of results.
|
|
The implementation is essentially the same as the date range search
prior to Jani's fancy date parser.
|
|
The function notmuch_exit_if_unmatched_db_uuid is split from
notmuch_process_shared_options because it needs an open notmuch
database.
There are two exceptional cases in uuid handling.
1) notmuch config and notmuch setup don't currently open the database,
so it doesn't make sense to check the UUID.
2) notmuch compact opens the database inside the library, so we either
need to open the database just to check uuid, or change the API.
|
|
In the short term we need a way to get lastmod information e.g. for
the test suite. In the long term we probably want to add lastmod
information to at least the structured output for several other
clients (e.g. show, search).
|
|
This has been tested with gcc and clang.
|
|
This functionality seems to have been undocumented, if it ever
existed. Document it now.
|
|
replace leading spaces with tabs
|
|
Thanks to FreeBSD port maintainer Mikhail for report and the original
the original patch.
This is the right thing (TM) and also apparently fixes the build on
FreeBSD.
|
|
The example is a bit silly, but notmuch subcommand --help is actually
not equivalent to "notmuch --help subcommand".
|
|
Previously we set up a way for the top level notmuch command to choose
which gpg binary was invoked by libgmime. In this commit we add the
(mostly boilerplate) code to allow the notmuch-config command to read
and write this path, and use it in the appropriate struct.
Update tests for new default variable
|
|
It's emacsclient command, not comment. Document default values. While
at it, format the environment section similarly to other man pages.
|
|
Notmuch uses long options exclusively all around. The short options in
notmuch-emacs-mua are intentionally just a compatible subset of
mutt(1). Keep it this way, if only to make documenting the fact easy!
The Notmuch style --client long option remains, of course.
|
|
Add a tool to start composing an email in the Notmuch Emacs UI with
the specified subject, recipients, and message body.
|
|
'attachement' missed a colon, and 'mimetype' was not added to this table
at all.
|
|
|
|
More material borrowed from the wiki page on "searching"
|
|
This is lightly massaged from the searching page on the wiki.
|
|
Document all options for completeness.
|
|
Document all options for completeness.
|
|
Fix indentation of options. Move search terms description before
options. Fix synopsis.
|
