Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

notmuch-mutt(1) [debian man page]

NOTMUCH-MUTT(1) 					User Contributed Perl Documentation					   NOTMUCH-MUTT(1)

NAME
notmuch-mutt - notmuch (of a) helper for Mutt SYNOPSIS
notmuch-mutt [OPTION]... search [SEARCH-TERM]... notmuch-mutt [OPTION]... thread < MAIL notmuch-mutt [OPTION]... tag [TAGS]... < MAIL DESCRIPTION
notmuch-mutt is a frontend to the notmuch mail indexer capable of populating a maildir with search results. OPTIONS
-o DIR --output-dir DIR Store search results as (symlink) messages under maildir DIR. Beware: DIR will be overwritten. (Default: ~/.cache/notmuch/mutt/results/) -p --prompt Instead of using command line search terms, prompt the user for them (only for "search"). -h --help Show usage information and exit. INTEGRATION WITH MUTT
notmuch-mutt can be used to integrate notmuch with the Mutt mail user agent (unsurprisingly, given the name). To that end, you should define macros like the following in your Mutt configuration (usually one of: ~/.muttrc, /etc/Muttrc, or a configuration snippet under /etc/Muttrc.d/): macro index <F8> "<enter-command>unset wait_key<enter><shell-escape>notmuch-mutt --prompt search<enter><change-folder-readonly>~/.cache/notmuch/mutt/results<enter>" "notmuch: search mail" macro index <F9> "<enter-command>unset wait_key<enter><pipe-message>notmuch-mutt thread<enter><change-folder-readonly>~/.cache/notmuch/mutt/results<enter><enter-command>set wait_key<enter>" "notmuch: reconstruct thread" macro index <F6> "<enter-command>unset wait_key<enter><pipe-message>notmuch-mutt tag -inbox<enter>" "notmuch: remove message from inbox" The first macro (activated by <F8>) prompts the user for notmuch search terms and then jump to a temporary maildir showing search results. The second macro (activated by <F9>) reconstructs the thread corresponding to the current mail and show it as search results. The third macro (activated by <F6>) removes the tag "inbox" from the current message; by changing "-inbox" this macro may be customised to add or remove tags appropriate to the users notmuch work-flow. To keep notmuch index current you should then periodically run "notmuch new". Depending on your local mail setup, you might want to do that via cron, as a hook triggered by mail retrieval, etc. SEE ALSO
mutt(1), notmuch(1) AUTHOR
Copyright: (C) 2011-2012 Stefano Zacchiroli <zack@upsilon.cc> License: GNU General Public License (GPL), version 3 or higher perl v5.14.2 2012-06-02 NOTMUCH-MUTT(1)

Check Out this Related Man Page

NOTMUCH-REPLY(1)					      General Commands Manual						  NOTMUCH-REPLY(1)

NAME
notmuch-reply - Constructs a reply template for a set of messages. SYNOPSIS
notmuch reply [options...] <search-term>... DESCRIPTION
Constructs a reply template for a set of messages. To make replying to email easier, notmuch reply takes an existing set of messages and constructs a suitable mail template. The Reply-to: header (if any, otherwise From:) is used for the To: address. Unless --reply-to=sender is specified, values from the To: and Cc: headers are copied, but not including any of the current user's email addresses (as configured in primary_mail or other_email in the .notmuch-con- fig file) in the recipient list. It also builds a suitable new subject, including Re: at the front (if not already present), and adding the message IDs of the messages being replied to to the References list and setting the In-Reply-To: field correctly. Finally, the original contents of the emails are quoted by prefixing each line with '> ' and included in the body. The resulting message template is output to stdout. Supported options for reply include --format=(default|json|headers-only) default Includes subject and quoted message body. json Produces JSON output containing headers for a reply message and the contents of the original message. This output can be used by a client to create a reply message intelligently. headers-only Only produces In-Reply-To, References, To, Cc, and Bcc headers. --reply-to=(all|sender) all (default) Replies to all addresses. sender Replies only to the sender. If replying to user's own message (Reply-to: or From: header is one of the user's configured email addresses), try To:, Cc:, and Bcc: headers in this order, and copy values from the first that contains something other than only the user's addresses. --decrypt Decrypt any MIME encrypted parts found in the selected content (ie. "multipart/encrypted" parts). Status of the decryption will be reported (currently only supported with --format=json) and the multipart/encrypted part will be replaced by the decrypted content. See notmuch-search-terms(7) for details of the supported syntax for <search-terms>. Note: It is most common to use notmuch reply with a search string matching a single message, (such as id:<message-id>), but it can be use- ful to reply to several messages at once. For example, when a series of patches are sent in a single thread, replying to the entire thread allows for the reply to comment on issues found in multiple patches. The default format supports replying to multiple messages at once, but the JSON format does not. SEE ALSO
notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1), notmuch-hooks(5), notmuch-new(1), notmuch-restore(1), notmuch-search(1), notmuch-search-terms(7), notmuch-show(1), notmuch-tag(1) Notmuch 0.13.2 2012-06-01 NOTMUCH-REPLY(1)
Man Page