| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
Somehow this has been missing from our manual. Add it now.
|
| |
|
|
| |
This functionality came through a recent addition to the library.
|
| |
|
|
|
| |
With man pages we have to be careful or commands may not function
after copy-and-paste.
|
| |
|
|
|
|
|
|
|
|
|
| |
A new 'part' subcommand allows the user to extract a single part from
a MIME message. Usage:
notmuch part --part=<n> <search terms>
The search terms must match only a single message
(e.g. id:foo@bar.com). The part number specified refers to the part
identifiers output by `notmuch show'. The content of the part is
written the stdout with no formatting or identification marks. It is
not JSON formatted.
|
| |
|
|
|
| |
I like the readability of this, it provides compatibility with people
trained in this syntax by sup, and it even saves one character.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
notmuch-show.
In the case of notmuch-show, "--format=json" also implies
"--entire-thread" as the thread structure is implicit in the emitted
document tree.
As a coincidence to the implementation, multipart message ID numbers are
now incremented with each part printed. This changes the previous
semantics, which were unclear and not necessary related to the actual
ordering of the message parts.
|
| |
|
|
|
| |
This seems to be the standard method of formatting an environment
variable section within a man page.
|
| |
|
|
| |
Briefly describe the NOTMUCH_CONFIG variable there.
|
| |
|
|
|
|
|
| |
This was really the last thing keeping the initial run of "notmuch
new" being different from all other runs. And I'm taking a fresh
look at the performance of "notmuch new" anyway, so I think we can
safely drop this optimization.
|
| |
|
|
|
| |
This was added to "notmuch help" earlier, but not to the man page.
Add it there, and use consistent wording in both places.
|
| |
|
|
| |
Signed-off-by: Jed Brown <jed@59A2.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This was a poor workaround around the fact that the existing
notmuch_threads_t object is implemented poorly. It's got a fine
iterartor-based interface, but the implementation does all of the
work up-front in _create rather than doing the work incrementally
while iterating.
So to start fixing this, first get rid of all the hacks we had working
around this. This drops the --first and --max-threads options from the
search command, (but hopefully nobody was using them
anyway---notmuch.el certainly wasn't).
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The rudimentary aspect here is that the date ranges are specified with
UNIX timestamp values (number of seconds since 1970-01-01 UTC). One
thing that can help here is using the date program to determins
timestamps, such as:
$(date +%s -d 2009-10-01)..$(date +%s)
Long-term, we'll probably need to do our own query parsing to be able
to support directly-specified dates and also relative expressions like
"since:'2 months ago'".
|
| |
|
|
|
| |
If present, $NOTMUCH_CONFIG will be used as the configuration file
location.
|
| |
|
|
|
| |
Little things I noticed while using this text as reference for the
"notmuch help" documentation.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
I set out merely to add documentation for the recently-added options
for "notmuch search" (--first, --max-threads, and --sort), but ended
up revamping a lot. A significant change is a new SEARCH SYNTAX
section separate from "notmuch search" that is referred to in the
documentation of search, show, reply, and tag.
Also many sections were updated to reflect recent changes, (such as
the dropping of the NOTMUCH_BASE environment variable, the addition of
the .notmuch-config file, etc.)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reviewed-by: Carl Worth <cworth@cworth.org>
Keith wrote all the code here against notmuch before notmuch.c was
split up into multiple files. So I've pushed the code around in
various ways to match the new code structure, but have generally tried
to avoid making any changes to the behavior of the code.
I did fix one bug---a missing call to g_mime_stream_file_set_owner in
show_part which would cause "notmuch show" to go off into the weeds
when trying to show multiple messages, (since the first stream would
fclose stdout).
|
| |
|
|
|
| |
It would be nice to have this documentation live in a single place,
but for now, this is what we get.
|
|
|
By pulling content out of notmuch help, and also the messages
printed by "notmuch setup".
|
