From: Ruben Pollan <meskio@sindominio.net>
To: Arian Kuschki <arian.kuschki@googlemail.com>, notmuch@notmuchmail.org
Subject: Re: notmuch for mutt (was: vim client)
Date: Sun, 21 Feb 2010 12:42:42 +0100 [thread overview]
Message-ID: <20100221114242.GA28012@blackspot> (raw)
In-Reply-To: <20100221065658.GC23704@lapse.rw.madduck.net>
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
On 07:56, Sun 21 Feb 10, martin f krafft wrote:
> also sprach Ruben Pollan <meskio@sindominio.net> [2010.02.19.2112 +0100]:
> > > 1. will there be a usable ncurses or mutt version that supports
> > > notmuch anytime soon?
> >
> > I started to work on that I while ago. I didn't hack on it for
> > a while, but I hope I'll return to it soon. Anyway to create
> > a proper good client is a lot of work, I don't think I'll be able
> > to make something usable in months (if I ever make it).
>
> How would mutt support notmuch? Could you elaborate on the way you
> plan to integrate them?
Ups. I see I explained it wrong. I started to create a ncurses client. I
didn't think about mutt.
I'm not sure if notmuch can be well integrated on mutt. They have kind of
different approach. Maybe the best way to integrate it is the notmuch-fuse that
someone propose a while ago in this list.
--
Rubén Pollán | jabber:meskio@jabber.org
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-02-21 11:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 16:49 vim client Arian Kuschki
2010-02-19 20:12 ` Ruben Pollan
2010-02-21 6:56 ` notmuch for mutt (was: vim client) martin f krafft
2010-02-21 11:42 ` Ruben Pollan [this message]
2010-02-20 17:34 ` vim client Ben Gamari
2010-02-25 17:03 ` Arian Kuschki
2010-02-26 3:04 ` Ben Gamari
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=20100221114242.GA28012@blackspot \
--to=meskio@sindominio.net \
--cc=arian.kuschki@googlemail.com \
--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).