From: Michal Sojka <sojkam1@fel.cvut.cz>
To: Austin Clements <amdragon@mit.edu>
Cc: notmuch@notmuchmail.org
Subject: Re: Date ranges syntax (was: Xapian locking errors with custom query parser)
Date: Thu, 24 Mar 2011 14:50:21 +0100 [thread overview]
Message-ID: <87mxkksk4i.fsf@steelpick.2x.cz> (raw)
In-Reply-To: <AANLkTinzJrdA24V60LBUavUn1arMGQ14CM5ZGwCfGfcV@mail.gmail.com>
On Mon, 21 Mar 2011, Austin Clements wrote:
> On Fri, Mar 11, 2011 at 3:58 AM, Michal Sojka <sojkam1@fel.cvut.cz> wrote:
> > Additionally, I'd suggest to support value range queries for dates with
> > ".." syntax. Besides that some users may relay on this syntax, I use
> > date searches a lot and with custom query parser I have to type
> > "after:yesterday", which is unnecessarily long. I wish that
> > "yesterday..", which is much easier to type, would do the same.
> > Similarly, "mon..wed" would be easier to type than "after:mon
> > before:wed". What do you think?
>
> Personally, I just don't understand the .. range syntax, which is why
> I left it out (also, I was following the example in the TODO file).
> It's completely inconsistent with the rest of the query syntax and
> makes no indication of what it's a range over (what if you had other
> ordinal values to search over? what if you could search by the
> received date or the sent date?).
>
> What about something like "date:mon..wed"? That's consistent with the
> query syntax (the range part becomes part of the date syntax, not part
> of the top-level query syntax), it indicates the domain of the search
> term in a clean and extensible way, and it's succinct.
Yes, the date prefix with ranges in value sounds reasonable and the word
"date" is even shorter than "after" or "before".
-Michal
next prev parent reply other threads:[~2011-03-24 13:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 10:18 Xapian locking errors with custom query parser Michal Sojka
2011-01-28 16:35 ` Austin Clements
2011-01-29 2:26 ` Austin Clements
2011-03-11 2:21 ` Carl Worth
2011-03-11 2:47 ` Austin Clements
2011-03-11 5:26 ` Carl Worth
2011-03-11 8:58 ` Michal Sojka
2011-03-21 7:51 ` Austin Clements
2011-03-24 13:50 ` Michal Sojka [this message]
2011-03-21 7:41 ` Austin Clements
2011-03-11 2:55 ` Jameson Rollins
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=87mxkksk4i.fsf@steelpick.2x.cz \
--to=sojkam1@fel.cvut.cz \
--cc=amdragon@mit.edu \
--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).