unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Tomi Ollila <tomi.ollila@iki.fi>
To: David Bremner <david@tethera.net>, Jani Nikula <jani@nikula.org>,
	notmuch@notmuchmail.org
Subject: Re: [PATCH] lib: add support for date:<expr>..! to mean date:<expr>..<expr>
Date: Sat, 26 Sep 2015 16:55:02 +0300	[thread overview]
Message-ID: <m2d1x5i8uh.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <87r3lm0z6m.fsf@zancas.localnet>

On Sat, Sep 26 2015, David Bremner <david@tethera.net> wrote:

> Jani Nikula <jani@nikula.org> writes:
>
>> It doesn't seem likely we can support simple date:<expr> expanding to
>> date:<expr>..<expr> any time soon. (This can be done with a future
>> version of Xapian, or with a custom query query parser.) In the mean
>> time, provide shorthand date:<expr>..! to mean the same. This is
>> useful, as the expansion takes place before interpetation, and we can
>> use, for example, date:yesterday..! to match from beginning of
>> yesterday to end of yesterday.
>
> pushed. At some point we probably want a NEWS item.

If it is in the NEWS, it is perpetual, otoh if only in documentation we
could theoretically deprecate and remove it easier in the future ... ;p

> d

Tomi

      reply	other threads:[~2015-09-26 13:55 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
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 [this message]

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=m2d1x5i8uh.fsf@guru.guru-group.fi \
    --to=tomi.ollila@iki.fi \
    --cc=david@tethera.net \
    --cc=jani@nikula.org \
    --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).