From: Krzysztof Ilowiecki <k@ilowiecki.com>
To: notmuch@notmuchmail.org
Subject: [alot] Introducing myself, asking various questions
Date: Sun, 18 Dec 2011 19:59:28 +0100 [thread overview]
Message-ID: <CANcQd8POazwALwAodK=hnaD7OyxhJD_awJ+J-f0+Ek8_0yNEMA@mail.gmail.com> (raw)
Hello
summary: I'm new, would like to help, have lots of ideas, some time
and some python.
The list welcome message invites to introducing myself, so I shall
comply, even if this appears to be some configuration relic ;)
I'm using the [alot] tag as it looks to be what I'm most likely to
contribute to.
I'm sysadmin/programmer and a physics student. I've been writing
anything significant in Python for only a year now, but have
previous experience with C. I prefer to contribute in Python, though.
I've been a vim user for nearly eight years, though only recently did I
start using things like macros or global commands and writing functions.
My experience of email is that I hated it until I started using Gmail
in 2004. Since then I merely dislike it :) Or rather, I dislike the
MUAs.
notmuch has made a very good impression on me and I would like to
migrate to it away from gmail. I happen to have some time
available now.
I understand it is quite hard to provide an overview for newcomers of
the state of a rapidly developing project. Please correct me if the
following assertions are wrong:
* emacs frontend is the most mature, enough for quite some people
to use it as their primary MUA
* alot is second, but is rather ambitious and very far from '1.0'
* I could use it without a need to fall back to the emacs one
* vim frontend is interesting, quite a bit less complete, and stalled
* curses-notmuch is dead
I would like to try and help writing a python terminal vim-friendly
client. Alot seems like by far the bast candidate, however I have the
impression that it may be trying to do too much for my needs, which may
be peculiar. I have installed offlineimap+notmuch+alot on a slow laptop
running Debian wheezy. It is looking good with a testing account and I'm
considering connecting it to live accounts. How likely is it to mess
things up in IMAP?
I understand synchronisation across machines and with IMAP is something
of an issue so far. How bad would it be to use git for that - and for
'undo'? It would appear some people use git+maildir even instead of
IMAP, but I guess the notmuch's database may be completely unsuitable...
Does alot have some sort of the design documentation, sketched vision it
is heading towards? I think I should write down my ideas before I get
too entangled in the implementation details, it would be good to
know if something like this is already available.
Kris Iłowiecki
next reply other threads:[~2011-12-18 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-18 18:59 Krzysztof Ilowiecki [this message]
2011-12-18 19:32 ` [alot] Introducing myself, asking various questions Patrick Totzke
2011-12-18 23:02 ` Krzysztof Ilowiecki
2011-12-22 17:55 ` Felipe Contreras
2011-12-18 20:18 ` Tom Prince
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='CANcQd8POazwALwAodK=hnaD7OyxhJD_awJ+J-f0+Ek8_0yNEMA@mail.gmail.com' \
--to=k@ilowiecki.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).