unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Matthew Lear <matt@bubblegen.co.uk>
To: notmuch@notmuchmail.org
Subject: trouble searching with unix timestamps
Date: Mon, 29 Jan 2018 15:39:31 +0000	[thread overview]
Message-ID: <CAJFxaw-zfQFUZQtyM4PVoP6DCeNhXaFHzNBAUxevfRdqU+Qy-Q@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]

Hi. I've noticed that I'm unable to notmuch search using date with unix
timestamps (ie number of seconds since Jan 1st 1970 UTC). I get a xapian
error. The notmuch man pages state that searching using
'date:<initial-timestamp>..<final-timestamp>'
where "each timestamp is a number representing the number of seconds since
1970-01-01 00:00:00 UTC" is supported, so I'm wondering what's wrong with
my installation.

* notmuch config get built_with.field_processor
true
* xapian-config - xapian-core 1.4.4
* notmuch 0.26+8~ga727e7d

Here's an example:

# date +%s
1517238733

# date -d @1517238733
Mon Jan 29 15:12:13 GMT 2018

# date -d @1517152333
Sun Jan 28 15:12:13 GMT 2018


# notmuch search date:1517152333..1517238733
notmuch search: A Xapian exception occurred
A Xapian exception occurred parsing query: Didn't understand date
specification '1517152333..1517238733'
Query string was: date:1517152333..1517238733

Yet I can do:

# notmuch search date:yesterday..today
or
# notmuch search date:1/28/2018..1/29/2018
or
# notmuch search date:20180128..20180129

..and all show 216 results.

Any thoughts as to why Xapian doesn't like this type of query? Is it just
me? :-)

Thanks,
--  Matt

[-- Attachment #2: Type: text/html, Size: 2990 bytes --]

             reply	other threads:[~2018-01-29 15:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29 15:39 Matthew Lear [this message]
2018-01-29 16:03 ` trouble searching with unix timestamps Jani Nikula
2018-01-29 16:13   ` Matthew Lear
2018-01-31  3:04     ` Daniel Kahn Gillmor
2018-02-01 20:54       ` Matthew Lear

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=CAJFxaw-zfQFUZQtyM4PVoP6DCeNhXaFHzNBAUxevfRdqU+Qy-Q@mail.gmail.com \
    --to=matt@bubblegen.co.uk \
    --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).