notmuch-config(1) [debian man page]
NOTMUCH-CONFIG(1) General Commands Manual NOTMUCH-CONFIG(1) NAME
notmuch-config - Access notmuch configuration file. SYNOPSIS
notmuch config get <section>.<item> notmuch config set <section>.<item> [value ...] notmuch config list DESCRIPTION
The config command can be used to get or set settings in the notmuch configuration file. get The value of the specified configuration item is printed to stdout. If the item has multiple values (it is a list), each value is separated by a newline character. set The specified configuration item is set to the given value. To specify a multiple-value item (a list), provide each value as a sep- arate command-line argument. If no values are provided, the specified configuration item will be removed from the configuration file. list Every configuration item is printed to stdout, each on a separate line of the form: section.item=value No additional whitespace surrounds the dot or equals sign characters. In a multiple-value item (a list), the values are separated by semicolon characters. The available configuration items are described below. database.path The top-level directory where your mail currently exists and to where mail will be delivered in the future. Files should be indi- vidual email messages. Notmuch will store its database within a sub-directory of the path configured here named .notmuch. user.name Your full name. user.primary_email Your primary email address. user.other_email A list of other email addresses at which you receive email. new.tags A list of tags that will be added to all messages incorporated by notmuch new. new.ignore A list of file and directory names, without path, that will not be searched for messages by notmuch new. All the files and direc- tories matching any of the names specified here will be ignored, regardless of the location in the mail store directory hierarchy. search.exclude_tags A list of tags that will be excluded from search results by default. Using an excluded tag in a query will override that exclusion. maildir.synchronize_flags If true, then the following maildir flags (in message filenames) will be synchronized with the corresponding notmuch tags: Flag Tag ---- ------- D draft F flagged P passed R replied S unread (added when 'S' flag is not present) The notmuch new command will notice flag changes in filenames and update tags, while the notmuch tag and notmuch restore commands will notice tag changes and update flags in filenames. If there have been any changes in the maildir (new messages added, old ones removed or renamed, maildir flags changed, etc.), it is advisable to run notmuch new before notmuch tag or notmuch restore commands to ensure the tag changes are properly synchronized to the maildir flags, as the commands expect the database and maildir to be in sync. ENVIRONMENT
The following environment variables can be used to control the behavior of notmuch. NOTMUCH_CONFIG Specifies the location of the notmuch configuration file. Notmuch will use ${HOME}/.notmuch-config if this variable is not set. SEE ALSO
notmuch(1), notmuch-count(1), notmuch-dump(1), notmuch-hooks(5), notmuch-new(1), notmuch-reply(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-CONFIG(1)
Check Out this Related Man Page
NOTMUCH-SEARCH-TERMS(7) Miscellaneous Information Manual NOTMUCH-SEARCH-TERMS(7) NAME
notmuch-search-terms - Syntax for notmuch queries SYNOPSIS
notmuch count [options...] <search-term>... notmuch dump [ <filename> ] [--] [ <search-term>...] notmuch search [options...] <search-term>... notmuch show [options...] <search-term>... notmuch tag +<tag>|-<tag> [...] [--] <search-term>... DESCRIPTION
Several notmuch commands accept a common syntax for search terms. The search terms can consist of free-form text (and quoted phrases) which will match all messages that contain all of the given terms/phrases in the body, the subject, or any of the sender or recipient headers. As a special case, a search string consisting of exactly a single asterisk ("*") will match all messages. In addition to free text, the following prefixes can be used to force terms to match against specific portions of an email, (where <brack- ets> indicate user-supplied values): from:<name-or-address> to:<name-or-address> subject:<word-or-quoted-phrase> attachment:<word> tag:<tag> (or is:<tag>) id:<message-id> thread:<thread-id> folder:<directory-path> The from: prefix is used to match the name or address of the sender of an email message. The to: prefix is used to match the names or addresses of any recipient of an email message, (whether To, Cc, or Bcc). Any term prefixed with subject: will match only text from the subject of an email. Searching for a phrase in the subject is supported by including quotation marks around the phrase, immediately following subject:. The attachment: prefix can be used to search for specific filenames (or extensions) of attachments to email messages. For tag: and is: valid tag values include inbox and unread by default for new messages added by notmuch new as well as any other tag values added manually with notmuch tag. For id:, message ID values are the literal contents of the Message-ID: header of email messages, but without the '<', '>' delimiters. The thread: prefix can be used with the thread ID values that are generated internally by notmuch (and do not appear in email messages). These thread ID values can be seen in the first column of output from notmuch search The folder: prefix can be used to search for email message files that are contained within particular directories within the mail store. Only the directory components below the top-level mail database path are available to be searched. In addition to individual terms, multiple terms can be combined with Boolean operators ( and, or, not , etc.). Each term in the query will be implicitly connected by a logical AND if no explicit operator is provided, (except that terms with a common prefix will be implicitly combined with OR until we get Xapian defect #402 fixed). Parentheses can also be used to control the combination of the Boolean operators, but will have to be protected from interpretation by the shell, (such as by putting quotation marks around any parenthesized expression). Finally, results can be restricted to only messages within a particular time range, (based on the Date: header) with a syntax of: <initial-timestamp>..<final-timestamp> Each timestamp is a number representing the number of seconds since 1970-01-01 00:00:00 UTC. This is not the most convenient means of expressing date ranges, but until notmuch is fixed to accept a more convenient form, one can use the date program to construct timestamps. For example, with the bash shell the following syntax would specify a date range to return messages from 2009-10-01 until the current time: $(date +%s -d 2009-10-01)..$(date +%s) SEE ALSO
notmuch(1), notmuch-config(1), notmuch-count(1), notmuch-dump(1), notmuch-hooks(5), notmuch-new(1), notmuch-reply(1), notmuch-restore(1), notmuch-search(1), notmuch-show(1), notmuch-tag(1) Notmuch 0.13.2 2012-06-01 NOTMUCH-SEARCH-TERMS(7)