From: Ico <ico@pruts.nl>
To: notmuch@notmuchmail.org
Subject: Feature request: search for last N modified mails
Date: Fri, 02 Dec 2016 15:01:15 +0100 [thread overview]
Message-ID: <20161202140115.62194.22060@localhost.localdomain> (raw)
My normal mail workflow is to keep todo's in my inbox; these can be a few days
or weeks old if I'm lazy. Every now and then I find myself accidentally
removing things from the inbox, and I have a very hard time finding things
back. As discussed on #notmuch IRC today: I'd like to request a feature for
searching for the last N modified mails, as notmuch already has this info in
the database.
bremner suggested this could be implemented using with a query like
lastmod:-10
14:39 < Zevv> basically, I'd like to be able to search for the last 10 modified
mails. Where 'modified' would probably mean changing tags
14:41 < bremner> Zevv: you can get the current value from notmuch count --lastmod '*'
14:41 < bremner> then basically every tag change increments it
14:42 < bremner> so I guess subtract 10 and search?
14:44 < Zevv> Hm that would make it hard to use it as a simple query for in alot
14:45 < bremner> yes.
14:45 < bremner> I never thought about it before, but it would be possible to
impliment lastmod:-10
14:47 < Zevv> that would be extremely handy
--
:wq
^X^Cy^K^X^C^C^C^C
next reply other threads:[~2016-12-02 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 14:01 Ico [this message]
2016-12-03 13:22 ` Feature request: search for last N modified mails cesar mena
2022-08-08 11:50 ` [PATCH] WIP: provide relative lastmod sexp queries David Bremner
2022-08-09 11:25 ` [PATCH 2/3] WIP/lib: factor out lastmod range handling from sexp parser David Bremner
2022-08-09 11:25 ` [PATCH 3/3] WIP/lib: use common lastmod logic in infix parser David Bremner
2022-09-03 11:51 ` Feature request: search for last N modified mails David Bremner
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=20161202140115.62194.22060@localhost.localdomain \
--to=ico@pruts.nl \
--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).