| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
Various typo fixes in documentation within the code that can be made
available to the user, (emacs function help strings, "notmuch help"
output, notmuch man page, etc.).
Signed-off-by: Pieter Praet <pieter@praet.org>
Edited-by: Carl Worth <cworth@cworth.org> Restricted to just
documentation and fixed fix of "comman" to "common" rather than
"command".
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This adds support for decrypting PGP/MIME-encrypted parts to
notmuch-show and notmuch-reply. The --decrypt option implies
--verify. Once decryption (and possibly signature verification) is
done, a new part_encstatus formatter is emitted, the part_sigstatus
formatter is emitted, and the entire multipart/encrypted part is
replaced by the contents of the encrypted part.
At the moment only a json part_encstatus formatting function is
available, even though decryption is done for all formats. Emacs
support to follow.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is primarily for notmuch-show, although the functionality is
added to show-message. Once signatures are processed a new
part_sigstatus formatter is emitted, and the entire multipart/signed
part is replaced with the contents of the signed part.
At the moment only a json part_sigstatus formatting function is
available. Emacs support to follow.
The original work for this patch was done by
Daniel Kahn Gillmor <dkg@fifthhorseman.net>
whose help with this functionality I greatly appreciate.
|
| |
|
|
|
|
|
| |
Manually turn off both filling and justification for the one
exceedingly-long URL which was blowing groff's mind. Also, adjust the
position of 'text' to not be at the beginning of a line so it is not
mistaken for a macro.
|
| |
|
|
|
|
|
|
| |
We recently made the --part option to "notmuch show" trigger a default
format of "raw", (since the previous default of "text" is not often
useful with a single part---especially a non-text part).
Here, we update the documentation to match.
|
| |
|
|
|
|
|
|
|
| |
Outputting of single MIME parts is moved to an option of notmuch show,
instead of being handled in it's own sub-command. The recent rework
of multipart mime allowed for this change but consolidating part
handling into a single recursive function (show_message_part) that
includes formatting. This allows for far simpler handling single
output of a single part, including formatting.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, notmuch show flattened all output, losing information
about the nesting of the MIME hierarchy. Now, the output is properly
nested, (both in the --format=text and --format=json output), so that
clients can analyze the original MIME structure.
Internally, this required splitting the final closing delimiter out of
the various show_part functions and putting it into a new
show_part_end function instead. Also, the show_part function now
accepts a new "first" argument that is set not only for the first MIME
part of a message, but also for each first MIME part within a series
of multipart parts. This "first" argument controls the omission of a
preceding comma when printing a part (for json).
Many thanks to David Edmondson <dme@dme.org> for originally
identifying the lack of nesting in the json output and submitting an
early implementation of this feature. Thanks as well to Jameson Graef
Rollins <jrollins@finestructure.net> for carefully shepherding David's
patches through a remarkably long review process, patiently explaining
them, and providing a cleaned up series that led to this final
implementation. Jameson also provided the new emacs code here.
|
| |
|
|
| |
Augmenting both the builtin help as well as the manual page.
|
| |
|
|
|
|
|
|
|
| |
This is part of an effort to avoid proliferation of excessive
top-level notmuch commands. Also, "raw" better captures the
functionality here, (as opposed to "cat" which is a fairly oblique
reference to a bad Unix abbreviation whose metaphor doesn't work here
since "notmuch cat" operates only on a single message and hence cannot
"con'cat'enate" anything).
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This command outputs a raw message matched by search term to the
standard output. It allows MUAs to access the messages for piping,
attachment manipulation, etc. by running notmuch cat rather then
directly access the file. This will simplify the MUAs when they need
to operate on a remote database.
Edited-by: Carl Worth <cworth@cworth.org>: Remove trailing whitespace,
add missing "test_done" to new test script to avoid "Unexpected exit"
error.
|
| |
|
|
|
| |
As pointed out by Debian lintian, options with '-' might not be
copy/pastable if formatted with an unescaped '-' character.
|
| |
|
|
|
| |
This was inadvertently left off when --output=files was recently added
as a new option.
|
| |
|
|
| |
Yet another thing that will be extremely handy for scripts.
|
| |
|
|
|
| |
This can be handy for scripts which need to extract just a thread ID from
a search term, for example.
|
| |
|
|
|
|
| |
It is now possible to set configuration items from the command-line in
a manner quite similar to the support for querying configuration
items.
|
| |
|
|
|
| |
So far, we implement only "notmuch config get". It won't be too much
work from here to also implement "notmuch config set".
|
| |
|
|
|
| |
Shame on me for adding a feature without documenting it at the same
time.
|
| |
|
|
| |
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".
|
Pieter Praet
Jameson Graef Rollins
Carl Worth
Michal Sojka
David Edmondson
Scott Robinson
James Westby
Jed Brown
Alec Berryman
Keith Packard