unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Michal Sojka <sojkam1@fel.cvut.cz>
To: Jani Nikula <jani@nikula.org>, notmuch@notmuchmail.org
Cc: Tomi Ollila <tomi.ollila@iki.fi>
Subject: Re: [PATCH v6 0/9] notmuch search date:since..until query support
Date: Fri, 02 Nov 2012 18:40:26 +0100	[thread overview]
Message-ID: <87hap76gz9.fsf@steelpick.2x.cz> (raw)
In-Reply-To: <87r4oejstw.fsf@zancas.localnet>

Hi all,

On Wed, Oct 31 2012, David Bremner wrote:
> Jani Nikula <jani@nikula.org> writes:
>
>> Hi all, v6 of [1] with plenty of small changes addressing Austin's
>> review [2], [3], [4], and [5]. See my replies to Austin for what I've
>> agreed to change, and what I've chosen to ignore and why.
>>
>
> Pushed, (with patch 7 out of sequence, sorry about that).

Just pulled current HEAD and tried

$ notmuch search tag:notmuch and date:"this week"                                                                                                                                                                                                                                                              
thread:0000000000029c60   October 22 [1/21] Austin Clements| Jani Nikula, Tomi Ollila; [PATCH v5 2/9] parse-time-string: add a date/time parser to notmuch (inbox list notmuch unread)
thread:000000000002156c   2012-02-25 [1/8] Jani Nikula| Tomi Ollila, Mark Walters; [RFC PATCH 0/2] natural language date range search (inbox list notmuch notmuch::patch notmuch::wip unread watch)
thread:0000000000005191   2011-08-15 [2/8] Jani Nikula, Michal Sojka| Jason Woofenden, Tomi Ollila; [RFC PATCH 3/3] lib: add gnulib get_date() based date range search (list notmuch notmuch::patch notmuch::wip replied sent to-me watch)

Can somebody explain me the result? This is definitely not the mail from
this week.

Also the results below look strange to me.

notmuch search tag:notmuch and date:'"this week"'                                                                                                                                                                                                                                                            
thread:000000000002a102   Tue. 21:32 [2/13] Jani Nikula| Austin Clements, Tomi Ollila, David Bremner; [PATCH v6 4/9] test: add smoke tests for the date/time parser module (inbox list notmuch unread)
thread:000000000002156c   2012-02-25 [3/8] Jani Nikula, Tomi Ollila| Mark Walters; [RFC PATCH 0/2] natural language date range search (inbox list notmuch notmuch::patch notmuch::wip unread watch)
thread:0000000000005191   2011-08-15 [2/8] Jani Nikula, Michal Sojka| Jason Woofenden, Tomi Ollila; [RFC PATCH 3/3] lib: add gnulib get_date() based date range search (list notmuch notmuch::patch notmuch::wip replied sent to-me watch)
thread:0000000000012725   2011-01-28 [1/5] Carl Worth| Thomas Schwinge, Michal Sojka; [PATCH] Clarify usage of `additional_headers' in test/test-lib.sh:generate_message. (list notmuch unread)
thread:0000000000012ef1   2010-04-09 [1/7] Carl Worth| Anthony Towns, Mark Anderson, Sebastian Spaeth, Michal Sojka, Sandra Snan; Initial attempt at a "merge window" for notmuch (list notmuch unread)
thread:000000000000e973   2010-01-27 [2/12] Keith Packard, Sebastian Spaeth; [notmuch] [PATCH] Make the date parser nicer (list notmuch unread)

The following is also not very nice. I'm not sure whether notmuch can do
anything prevent this error. Double-quoting (like above) helps here.

$ notmuch search tag:notmuch and date:"this week.."                                                                                                                                                                                                                                                            
A Xapian exception occurred performing query: Unknown range operation
Query string was: tag:notmuch and date:this week..

I'm sorry to not have more time for debugging these problems.

Cheers,
-Michal

  reply	other threads:[~2012-11-02 17:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30 20:32 [PATCH v6 0/9] notmuch search date:since..until query support Jani Nikula
2012-10-30 20:32 ` [PATCH v6 1/9] build: drop the -Wswitch-enum warning Jani Nikula
2012-10-30 20:32 ` [PATCH v6 2/9] parse-time-string: add a date/time parser to notmuch Jani Nikula
2012-10-30 20:32 ` [PATCH v6 3/9] test: add new test tool parse-time for date/time parser Jani Nikula
2012-10-30 20:32 ` [PATCH v6 4/9] test: add smoke tests for the date/time parser module Jani Nikula
2012-10-30 20:32 ` [PATCH v6 5/9] build: build parse-time-string as part of the notmuch lib and static cli Jani Nikula
2012-10-30 20:32 ` [PATCH v6 6/9] lib: add date range query support Jani Nikula
2012-10-30 20:32 ` [PATCH v6 7/9] test: add tests for date:since..until range queries Jani Nikula
2012-10-30 20:32 ` [PATCH v6 8/9] man: document the " Jani Nikula
2012-10-30 20:32 ` [PATCH v6 9/9] NEWS: date range search support Jani Nikula
2012-10-31  3:17 ` [PATCH v6 0/9] notmuch search date:since..until query support Austin Clements
2012-10-31 11:35 ` Tomi Ollila
2012-10-31 20:21 ` David Bremner
2012-11-02 17:40   ` Michal Sojka [this message]
2012-11-02 18:53     ` Jani Nikula

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87hap76gz9.fsf@steelpick.2x.cz \
    --to=sojkam1@fel.cvut.cz \
    --cc=jani@nikula.org \
    --cc=notmuch@notmuchmail.org \
    --cc=tomi.ollila@iki.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).