From: Anthony Towns <aj@erisian.com.au>
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: [PATCH] notmuch new --new-tags=tags...
Date: Tue, 13 Apr 2010 03:15:28 +1000 [thread overview]
Message-ID: <w2j87b3a4191004121015y180e79e6n8e2a55cdb9a65107@mail.gmail.com> (raw)
In-Reply-To: <87ljcsekc4.fsf@servo.finestructure.net>
On Tue, Apr 13, 2010 at 01:55, Jameson Rollins
<jrollins@finestructure.net> wrote:
> On Mon, 12 Apr 2010 17:11:24 +0200, Michal Sojka <sojkam1@fel.cvut.cz> wrote:
>> The problem I see with this approach is, that all notmuch searches are
>> build around Xapian. ...
> This does sound like a potential issue. I definitely don't understand
> how new messages are added to the database. I was mostly suggesting a
> syntax for adding tag as new messages are added, though, not that an
> actual xapian search term. I don't know if they can be decoupled,
> though.
If you say "they're just notmuch tag commands applied at new time" you
expect to have the same search behaviour as Xapian...
Maybe you could do that by temporarily inserting the mail into an
"inmemory" Xapian database, since you're only checking to see if that
particular one matches.
On the other hand, maybe having it be a separate syntax would be good
-- then you could justify using information notmuch doesn't usually
have -- like file/path names, Received or Delivered-To headers, and so
on.
On the gripping hand, maybe "notmuch tag" should simply be fast enough
that running a bunch of them after "notmuch new" isn't an issue.
Cheers,
aj
--
Anthony Towns <aj@erisian.com.au>
next prev parent reply other threads:[~2010-04-12 17:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-10 15:03 [PATCH] notmuch new --new-tags=tags Anthony Towns
2010-04-10 16:11 ` Dirk Hohndel
2010-04-12 8:00 ` Sebastian Spaeth
2010-04-12 11:59 ` Jameson Rollins
2010-04-12 12:25 ` Tomas Carnecky
2010-04-12 13:45 ` Scott Robinson
2010-04-12 15:11 ` Michal Sojka
2010-04-12 15:55 ` Jameson Rollins
2010-04-12 17:15 ` Anthony Towns [this message]
2010-04-12 18:03 ` Jameson Rollins
2010-04-23 17:49 ` Carl Worth
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=w2j87b3a4191004121015y180e79e6n8e2a55cdb9a65107@mail.gmail.com \
--to=aj@erisian.com.au \
--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).