From: marcus-sup@quintic.co.uk (Marcus Williams)
Subject: [sup-talk] [PATCH] Natural language date searches
Date: Fri, 26 Oct 2007 23:10:55 +0100 [thread overview]
Message-ID: <1193436327-sup-5753@tomsk> (raw)
With the help of the fantastic Chronic gem, this patch adds date based
searches to sup with natural language. So you can do
after:(1 week ago)
after:(yesterday at 22:00)
and
before:(today at 5:00)
and even combine them. For more examples see the Chronic docs at [1].
The brackets are important... watch the logs for oddities like:
after:(yesterday)
which probably wont do what you think as chronic sets a time of midday
on the converted date. Specify a time if you need to or use "24 hours
ago" or something.
Marcus
[1] http://chronic.rubyforge.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: date-search-diff
Type: application/octet-stream
Size: 912 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20071026/312f7611/attachment.obj
next reply other threads:[~2007-10-26 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 22:10 Marcus Williams [this message]
2007-10-27 21:10 ` Marcus Williams
2007-11-09 18:46 ` William Morgan
2007-11-09 20:29 ` Marcus Williams
2007-11-09 20:44 ` Marcus Williams
2007-11-09 21:20 ` Marcus Williams
2007-11-12 18:01 ` William Morgan
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1193436327-sup-5753@tomsk \
--to=marcus-sup@quintic.co.uk \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox