From: martin f krafft <madduck@madduck.net>
To: notmuch@notmuchmail.org
Subject: Re: Quick thoughts on a notmuch daemon
Date: Fri, 8 Jan 2010 15:56:20 +1300 [thread overview]
Message-ID: <20100108025620.GB28357@lapse.rw.madduck.net> (raw)
In-Reply-To: <874oo22blf.fsf@yoom.home.cworth.org>
[-- Attachment #1: Type: text/plain, Size: 2959 bytes --]
also sprach Carl Worth <cworth@cworth.org> [2009.12.08.2001 +1300]:
> One concept in notmuch (compared to sup) is to (eventually) avoid people
> having to go through that pain by their current mail client becoming
> "notmuch enabled". For me, I had always liked composing email in emacs,
> so I just have to add notmuch support to the existing emacs
> message-mode.
>
> Hopefully people working on other email interfaces will do similar
> things, (would be great to have Anjal and Thunderbird get some notmuch
> support for example).
>
> I definitely didn't like that with sup, to get all the global-search and
> tagging features one had to accept the curses UI as well.
I am a bit late to the party, but re: this thread [0], I would
suggest to go the way of a fuse filesystem. That's effectively
a daemon, but one which also bridges a chasm between notmuch and all
kinds of existing mail tools, including IMAP servers, by way of the
standard filesystem interface.
0. http://notmuchmail.org/pipermail/notmuch/2009/000782.html
I don't want to harp on this too much right now for I have not yet
fully understood notmuch, but the basic idea would be that you'd
have ~/mail provided by notmuch-fuse-daemon, and there'd be a tool
like notmuch-fuse-cli with which you can add virtual folders, e.g.
notmuch-fuse-cli new debianmail 'from:debian OR to:debian'
and that would create ~/mail/debianmail with mode 555 (since you
cannot write the results of a search) containing a Maildir with all
messages matching the query.
The benefit of this would be that I could use mutt, evolution, or an
IMAP server, or vi and shell tools to manipulate my mail without any
modifications to those tools.
There could be a separate hierarchy for tags, e.g. ~/mail/TAGS/foo
and ~/mail/TAGS/bar/baz matching on explicit tags (and maybe
~/mail/TAGS/notmuch with mode 555 for implicit tags). Writing mail
to those directories effectively adds tags, unlinking removes them.
~/mail/TAGS/UNTAGGED holds untagged mail for easier reference.
In addition to all of this, fuse could be used to index new messages
directly as they are delivered into ~/mail, rather than running
'notmuch new' regularly.
These ideas are not new, and I've written about them before:
http://madduck.net/blog/2007.07.24:a-user-space-filesystem-for-mail-labeling/
notmuch seems an excellent base for implementing such a filesystem.
I will try to make time before LCA to get up to speed on fuse, then
maybe Carl and Micah and I (and whoever else will be in Wellington)
can hack this up in a few hours and over a few beers.
If this resonates, or you want to work on this too, let's hear from
you!
--
martin | http://madduck.net/ | http://two.sentenc.es/
"no problem is so formidable
that you can't just walk away from it."
-- c. schulz
spamtraps: madduck.bogus@madduck.net
[-- Attachment #2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-01-08 2:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 22:27 Quick thoughts on a notmuch daemon Carl Worth
2009-12-07 19:02 ` David Bremner
2009-12-07 22:55 ` Marten Veldthuis
2009-12-07 23:51 ` micah anderson
2009-12-08 7:01 ` Carl Worth
2010-01-08 2:56 ` martin f krafft [this message]
2010-01-08 8:06 ` Mike Hommey
2010-01-08 9:03 ` martin f krafft
2010-01-08 9:20 ` Mike Hommey
2010-01-08 10:26 ` martin f krafft
2010-01-09 5:51 ` Mike Hommey
2009-12-08 19:29 ` Michiel Buddingh'
2009-12-09 22:13 ` Ruben Pollan
2010-02-20 1:09 ` Ruben Pollan
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=20100108025620.GB28357@lapse.rw.madduck.net \
--to=madduck@madduck.net \
--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).