[notmuch] Quick thoughts on a notmuch daemon

I started to code something base on your idea of a notmuch daemon. You can find it on: git://gitorious.org/notsomuch/notmuch.git On the server branch. The idea is to use unix named sockets to intercomunicate between the daemon and the client. And threads on the server to handle every request.

[notmuch] Quick thoughts on a notmuch daemon

On Fri, Jan 08, 2010 at 11:26:31PM +1300, martin f krafft wrote: > also sprach Mike Hommey [2010.01.08.2220 +1300]: > > FYI, I have a good experience writing fuse filesystems, both with > > high-level and low-level APIs. I'd avise to use the low-level API, > > which

[notmuch] Quick thoughts on a notmuch daemon

also sprach Mike Hommey [2010.01.08.2220 +1300]: > FYI, I have a good experience writing fuse filesystems, both with > high-level and low-level APIs. I'd avise to use the low-level API, > which allows for better performance. I don't have any experience with FUSE yet,

[notmuch] Quick thoughts on a notmuch daemon

also sprach Mike Hommey [2010.01.08.2106 +1300]: > I'm in \o_ (though I won't be in Wellington). I've been thinking > about a fuse filesystem on top of notmuch for a while. Grand news to see you interested! A FUSE filesystem is <25 functions to implement, and each

[notmuch] Quick thoughts on a notmuch daemon

also sprach Carl Worth [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] Quick thoughts on a notmuch daemon

On Fri, Jan 08, 2010 at 10:03:21PM +1300, martin f krafft wrote: > also sprach Mike Hommey [2010.01.08.2106 +1300]: > > I'm in \o_ (though I won't be in Wellington). I've been thinking > > about a fuse filesystem on top of notmuch for a while. > > Grand news to see

[notmuch] Quick thoughts on a notmuch daemon

On Fri, Jan 08, 2010 at 03:56:20PM +1300, martin f krafft wrote: > 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

[notmuch] Quick thoughts on a notmuch daemon

On 14:27, Thu 03 Dec 09, Carl Worth wrote: > A simple solution would be a notmuch daemon that can accept commands on > stdin, (in basically the exact same form as the current notmuch > command-line interface). If the daemon does the job of periodically > incorporating new mail, then the only

Re: [notmuch] Quick thoughts on a notmuch daemon

On 14:27, Thu 03 Dec 09, Carl Worth wrote: A simple solution would be a notmuch daemon that can accept commands on stdin, (in basically the exact same form as the current notmuch command-line interface). If the daemon does the job of periodically incorporating new mail, then the only command

[notmuch] Quick thoughts on a notmuch daemon

On Thu, 03 Dec 2009 14:27:05 -0800, Carl Worth wrote: > A simple solution would be a notmuch daemon that can accept commands on > stdin, (in basically the exact same form as the current notmuch > command-line interface). If the daemon does the job of periodically > incorporating new mail, then

[notmuch] Quick thoughts on a notmuch daemon

On Mon, 07 Dec 2009 15:02:03 -0400, David Bremner wrote: > > On Thu, 03 Dec 2009 14:27:05 -0800, Carl Worth wrote: > It might be a bit blue sky, but if this daemon could (optionally) talk > IMAP and translate tags into folders on the fly, this would be very > useful for people who need imap

[notmuch] Quick thoughts on a notmuch daemon

On Mon, 07 Dec 2009 18:51:58 -0500, micah anderson wrote: > I've switched mail clients enough over the past few years to know that > switching itself is a major pain. Absolutely. One concept in notmuch (compared to sup) is to (eventually) avoid people having to go through that pain by their

[notmuch] Quick thoughts on a notmuch daemon

Excerpts from Marten Veldthuis's message of Mon Dec 07 17:55:24 -0500 2009: > On Mon, 07 Dec 2009 15:02:03 -0400, David Bremner > wrote: > > > > On Thu, 03 Dec 2009 14:27:05 -0800, Carl Worth wrote: > > It might be a bit blue sky, but if this daemon could (optionally) talk > > IMAP and

[notmuch] Quick thoughts on a notmuch daemon

On Thu, 03 Dec 2009 14:27:05 -0800, Carl Worth wrote: > But with the other commands in place, (such as search and show), then > this could operate over ssh and all that would be necessary is one > additional command not in the current command line, (for "give me this > file"). And then the

Re: [notmuch] Quick thoughts on a notmuch daemon

On Mon, 07 Dec 2009 15:02:03 -0400, David Bremner da...@tethera.net wrote: On Thu, 03 Dec 2009 14:27:05 -0800, Carl Worth cwo...@cworth.org wrote: It might be a bit blue sky, but if this daemon could (optionally) talk IMAP and translate tags into folders on the fly, this would be very useful

Re: [notmuch] Quick thoughts on a notmuch daemon

Excerpts from Marten Veldthuis's message of Mon Dec 07 17:55:24 -0500 2009: On Mon, 07 Dec 2009 15:02:03 -0400, David Bremner da...@tethera.net wrote: On Thu, 03 Dec 2009 14:27:05 -0800, Carl Worth cwo...@cworth.org wrote: It might be a bit blue sky, but if this daemon could (optionally)

Re: [notmuch] Quick thoughts on a notmuch daemon

On Mon, 07 Dec 2009 18:51:58 -0500, micah anderson mi...@riseup.net wrote: I've switched mail clients enough over the past few years to know that switching itself is a major pain. Absolutely. One concept in notmuch (compared to sup) is to (eventually) avoid people having to go through that

[notmuch] Quick thoughts on a notmuch daemon

Here's a little idea in case someone wants to write some code before I get around to it. Two current problems: 1. You can't read mail (updating tags, etc.) at the same time new mail is being incorporated to the database. So if you have "notmuch new" as a cron job, then you will