From: Gaute Hope <eg@gaute.vetsj.com>
To: Mark Walters <markwalters1009@gmail.com>,
Jani Nikula <jani@nikula.org>,
notmuch@notmuchmail.org
Subject: Re: [RFC] lib: add support for date:<query>..! to mean date:<query>..<query>
Date: Sun, 19 Apr 2015 08:39:38 +0000 [thread overview]
Message-ID: <1429432663-astroid-2-31s581p1zi-1230@strange> (raw)
In-Reply-To: <87a8y6fuqw.fsf@qmul.ac.uk>
Excerpts from Mark Walters's message of April 17, 2015 20:57:
>
> Hi
>
> On Sat, 07 Mar 2015, Jani Nikula <jani@nikula.org> wrote:
>> Up to debate:
>>
>> 1) Is something like this useful at all as an intermediate step before
>> we can have support for date:<query>? (This can be done with a future
>> version of Xapian, or with a custom query query parser.)
>
> This looks good to me. Yes it may not be needed in the future but the
> patch is very small. It passes all tests. +1 from me.
>
>> 2) If yes, are there better alternatives to "!" as the end point? (Or
>> should the special case be the start point?) Also "@" and "same" have
>> been suggested. Examples: date:yesterday..! date:today..@
>> date:@..monday date:january..same.
>
> I would be happy with any of these.
I am probably missing something, but why do you need the end
point?
date:2015-04-16 mean date:2015-04-16..2015-04-16?
date:<query> -> date:<query>..<query>
- gaute
next prev parent reply other threads:[~2015-04-19 8:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 12:55 [RFC] lib: add support for date:<query>..! to mean date:<query>..<query> Jani Nikula
2015-04-17 18:57 ` Mark Walters
2015-04-18 0:12 ` Suvayu Ali
2015-04-19 8:39 ` Gaute Hope [this message]
2015-04-19 11:54 ` David Bremner
2015-04-18 8:07 ` Tomi Ollila
2015-06-08 14:57 ` David Bremner
2015-08-15 11:25 ` [PATCH] lib: add support for date:<expr>..! to mean date:<expr>..<expr> Jani Nikula
2015-09-26 1:03 ` David Bremner
2015-09-26 13:55 ` Tomi Ollila
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=1429432663-astroid-2-31s581p1zi-1230@strange \
--to=eg@gaute.vetsj.com \
--cc=jani@nikula.org \
--cc=markwalters1009@gmail.com \
--cc=notmuch@notmuchmail.org \
/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).