From: Jani Nikula Date: Sat, 13 Oct 2012 22:09:54 +0000 (+0300) Subject: [PATCH v4 8/9] man: document the date:since..until range queries X-Git-Url: http://git.tremily.us/gitweb.cgi?a=commitdiff_plain;h=bacc4d3bc37d38cd1835df80300f30213c99dba0;p=notmuch-archives.git [PATCH v4 8/9] man: document the date:since..until range queries --- diff --git a/40/1873812cf241568dc9b4c883e85eacb7b5eb4b b/40/1873812cf241568dc9b4c883e85eacb7b5eb4b new file mode 100644 index 000000000..6a80c0643 --- /dev/null +++ b/40/1873812cf241568dc9b4c883e85eacb7b5eb4b @@ -0,0 +1,249 @@ +Return-Path: +X-Original-To: notmuch@notmuchmail.org +Delivered-To: notmuch@notmuchmail.org +Received: from localhost (localhost [127.0.0.1]) + by olra.theworths.org (Postfix) with ESMTP id 6C65C431FAE + for ; Sat, 13 Oct 2012 15:10:25 -0700 (PDT) +X-Virus-Scanned: Debian amavisd-new at olra.theworths.org +X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "References" +X-Spam-Flag: NO +X-Spam-Score: -0.7 +X-Spam-Level: +X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 + tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled +Received: from olra.theworths.org ([127.0.0.1]) + by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) + with ESMTP id NU5z8hxFWKYb for ; + Sat, 13 Oct 2012 15:10:24 -0700 (PDT) +Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com + [209.85.217.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) + (No client certificate requested) + by olra.theworths.org (Postfix) with ESMTPS id 8A756431FBC + for ; Sat, 13 Oct 2012 15:10:24 -0700 (PDT) +Received: by mail-lb0-f181.google.com with SMTP id gg6so2988019lbb.26 + for ; Sat, 13 Oct 2012 15:10:24 -0700 (PDT) +X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; + d=google.com; s=20120113; + h=from:to:cc:subject:date:message-id:x-mailer:in-reply-to:references + :in-reply-to:references:x-gm-message-state; + bh=N1Ae/7X67HxGxXBlS8P8uxrKB4pxOubrwB6OBuBQiC0=; + b=LJ7biLFPbznqsDPy8roEof/uufppmy9RgJhjLwLvPKm64IJx+EzrFk/BwY21a6qbXI + j9AZaMNZ6chC+06sYsuRGBkhewl6OQ8nASMJAaiNA4GgtVZvWe3REdjwTPYppZQOS11b + zdk0eevLDxL+LhxACbjlwZiYthIaASYmPiJEPNuSTZAyZiDtw5B8gMSpi6FUJypYTwYz + 7AgYjkB3GAhiBrw5Af5VV5yZHfrNVECKxKsP3xDY2l5mk5WVh8vhW+nqmxat6R22j7Ki + lrWYNAWmu9RRypSybAm+pfleJ+9F+wRPW+RH16SJzET/jf3r+wm1Ko9ao1zDjD+Iu1bb + 45Vw== +Received: by 10.112.82.6 with SMTP id e6mr2914836lby.93.1350166224159; + Sat, 13 Oct 2012 15:10:24 -0700 (PDT) +Received: from localhost (dsl-hkibrasgw4-fe51df00-27.dhcp.inet.fi. + [80.223.81.27]) + by mx.google.com with ESMTPS id r8sm3272537lba.15.2012.10.13.15.10.22 + (version=SSLv3 cipher=OTHER); Sat, 13 Oct 2012 15:10:23 -0700 (PDT) +From: Jani Nikula +To: notmuch@notmuchmail.org +Subject: [PATCH v4 8/9] man: document the date:since..until range queries +Date: Sun, 14 Oct 2012 01:09:54 +0300 +Message-Id: + +X-Mailer: git-send-email 1.7.9.5 +In-Reply-To: +References: +In-Reply-To: +References: +X-Gm-Message-State: + ALoCoQkzaNgZiXj2vVWR4yWg5igaVU0WiBr/ovu5zoGN3SmmtwJgnV77UFVeE2enHZLvP1gvB4Rj +X-BeenThere: notmuch@notmuchmail.org +X-Mailman-Version: 2.1.13 +Precedence: list +List-Id: "Use and development of the notmuch mail system." + +List-Unsubscribe: , + +List-Archive: +List-Post: +List-Help: +List-Subscribe: , + +X-List-Received-Date: Sat, 13 Oct 2012 22:10:25 -0000 + +--- + man/man7/notmuch-search-terms.7 | 147 +++++++++++++++++++++++++++++++++++---- + 1 file changed, 135 insertions(+), 12 deletions(-) + +diff --git a/man/man7/notmuch-search-terms.7 b/man/man7/notmuch-search-terms.7 +index 17a109e..fbd3ee7 100644 +--- a/man/man7/notmuch-search-terms.7 ++++ b/man/man7/notmuch-search-terms.7 +@@ -54,6 +54,8 @@ terms to match against specific portions of an email, (where + + folder: + ++ date:.. ++ + The + .B from: + prefix is used to match the name or address of the sender of an email +@@ -104,6 +106,26 @@ contained within particular directories within the mail store. Only + the directory components below the top-level mail database path are + available to be searched. + ++The ++.B date: ++prefix can be used to restrict the results to only messages within a ++particular time range (based on the Date: header) with a range syntax ++of: ++ ++ date:.. ++ ++See \fBDATE AND TIME SEARCH\fR below for details on the range ++expression, and supported syntax for and date and time ++expressions. ++ ++The time range can also be specified using timestamps with a syntax ++of: ++ ++ .. ++ ++Each timestamp is a number representing the number of seconds since ++1970\-01\-01 00:00:00 UTC. ++ + In addition to individual terms, multiple terms can be + combined with Boolean operators ( + .BR and ", " or ", " not +@@ -117,20 +139,121 @@ 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: ++.SH DATE AND TIME SEARCH + +- .. ++This is a non-exhaustive description of the date and time search with ++some pseudo notation. Most of the constructs can be mixed freely, and ++in any order, but the same absolute date or time can't be expressed ++twice. + +-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) ++.RS 4 ++.TP 4 ++.B The range expression ++ ++date:.. ++ ++The above expression restricts the results to only messages from ++ to , based on the Date: header. ++ ++If or describes time at an accuracy of days or less, ++the date/time is rounded, towards past for and towards future ++for , to be inclusive. For example, date:january..february ++matches from the beginning of January until the end of ++February. Similarly, date:yesterday..yesterday matches from the ++beginning of yesterday until the end of yesterday. ++ ++Open-ended ranges are supported (since Xapian 1.2.1), i.e. it's ++possible to specify date:.. or date:.. to not limit the ++start or end time, respectively. Unfortunately, pre-1.2.1 Xapian does ++not report an error on open ended ranges, but it does not work as ++expected either. ++ ++Xapian does not support spaces in range expressions. You can replace ++the spaces with '_', or (in most cases) '-', or (in some cases) leave ++the spaces out altogether. ++ ++Entering date:expr without ".." (for example date:yesterday) won't ++work, as it's not interpreted as a range expression at all. You can ++achieve the expected result by duplicating the expr both sides of ".." ++(for example date:yesterday..yesterday). ++.RE ++ ++.RS 4 ++.TP 4 ++.B Relative date and time ++[N|number] (years|months|weeks|days|hours|hrs|minutes|mins|seconds|secs) [...] ++ ++All refer to past, can be repeated and will be accumulated. ++ ++Units can be abbreviated to any length, with the otherwise ambiguous ++single m being m for minutes and M for months. ++ ++Number multiplier can also be written out one, two, ..., ten, dozen, ++hundred. As special cases last means one ("last week") and this means ++zero ("this month"). ++ ++When combined with absolute date and time, the relative date and time ++specification will be relative from the specified absolute date and ++time. ++ ++Examples: 5M2d, two weeks ++.RE ++ ++.RS 4 ++.TP 4 ++.B Supported time formats ++H[H]:MM[:SS] [(am|a.m.|pm|p.m.)] ++ ++H[H] (am|a.m.|pm|p.m.) ++ ++HHMMSS ++ ++now ++ ++noon ++ ++midnight ++ ++Examples: 17:05, 5pm ++.RE ++ ++.RS 4 ++.TP 4 ++.B Supported date formats ++YYYY-MM[-DD] ++ ++DD-MM[-[YY]YY] ++ ++MM-YYYY ++ ++M[M]/D[D][/[YY]YY] ++ ++M[M]/YYYY ++ ++D[D].M[M][.[YY]YY] ++ ++D[D][(st|nd|rd|th)] Mon[thname] [YYYY] ++ ++Mon[thname] D[D][(st|nd|rd|th)] [YYYY] ++ ++Wee[kday] ++ ++Month names can be abbreviated at three or more characters. ++ ++Weekday names can be abbreviated at three or more characters. ++ ++Examples: 2012-07-31, 31-07-2012, 7/31/2012, August 3 ++.RE ++ ++.RS 4 ++.TP 4 ++.B Time zones ++(+|-)HH:MM ++ ++(+|-)HH[MM] ++ ++Some time zone codes, e.g. UTC, EET. ++.RE + + .SH SEE ALSO + +-- +1.7.9.5 +