From: Matt Price <moptop99@gmail.com>
To: Org Mode <emacs-orgmode@gnu.org>
Subject: mail integration, advice?
Date: Thu, 26 Apr 2012 09:47:40 -0400 [thread overview]
Message-ID: <CAN_Dec-1Ju_G21VRLR=Rmcx2zCD23vTB4_gNgCfxc2y7j8bHsQ@mail.gmail.com> (raw)
I'd like to take one more shot at returning to text-based email within
emacs, mostly because I want to be able to integrate mail easily into
my org-mode workflow. The last time I tried this I used wanderlust,
and I'd be willing to give it a try again but a couple of things have
discouraged me in the past:
- wl causes emacs to freeze up when it checks or sends mail, and can
take quite a long while to complete these operations
- wl seems to have gone quasi-dormant, with very little activity on
the mailing list and no recent releases; it also relies on two other
packages, FLIM and APEL, with similarly dormant mailing lists
So, I'm wondering what solutions other org users have settled on. My
current hopes for this:
- allow me to continue using Thunderbird as a backup for e.g. images
and highly formatted mails -- thunderbird is currently set up w/ local
copies of IMAP folders for my current mail, plus local archives served
on by dovecot that can be accessed both by thunderbird and by e.g.
wanderlust.
- fast search and easy-to-manage virtual folders of some kind -- I see
mu and notmuch are very strong on both these fronts
- easy, stable harvesting of email-based data through org-capture (if
possible, this should allow me to archive a message and still be able
to find it when I follow an org message link)
- would be nice if configuration didn't require TONS of lisp code, a I
am a very slow coder and these kinds of configuration tasks can be
very daunting for me.
- shouldn't slow down my workflow too much -- I should be able to very
quickly check my email then return to an org buffer to continue
writing.
Thanks very much for your suggestions! best,
matt
next reply other threads:[~2012-04-26 13:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 13:47 Matt Price [this message]
2012-04-26 14:33 ` mail integration, advice? Carson Chittom
2012-04-26 15:38 ` Tassilo Horn
2012-04-26 16:06 ` Carson Chittom
2012-04-26 16:28 ` Rasmus
2012-04-26 17:23 ` Tassilo Horn
2012-04-28 8:25 ` Eric Fraga
2012-04-28 12:28 ` Rasmus
2012-04-28 14:59 ` Eric Fraga
2012-04-28 23:49 ` Myles English
2012-04-29 1:00 ` Neil Smithline
2012-04-26 20:03 ` Florian Friesdorf
2012-04-26 21:26 ` Myles English
2012-04-27 13:34 ` Eric Schulte
2012-04-27 20:08 ` Myles English
2012-04-27 18:16 ` Eric Schulte
2012-04-28 8:29 ` Eric Fraga
2012-04-28 15:51 ` RC
2012-04-28 16:54 ` Richard Riley
2012-04-28 11:46 ` Rasmus
2012-04-28 22:45 ` [OT] " Eric Schulte
2012-04-26 22:22 ` Charles Philip Chan
2012-04-27 4:29 ` Eric Abrahamsen
2012-04-27 12:09 ` Stephen Eglen
2012-04-28 8:35 ` Eric Fraga
2012-04-28 17:44 ` Dirk-Jan C. Binnema
2012-04-29 0:45 ` Neil Smithline
2012-04-29 9:00 ` Stephen Eglen
2012-04-29 9:41 ` Bastien
2012-04-29 18:41 ` Mikkel Kristiansen
2012-04-30 10:28 ` Richard Riley
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAN_Dec-1Ju_G21VRLR=Rmcx2zCD23vTB4_gNgCfxc2y7j8bHsQ@mail.gmail.com' \
--to=moptop99@gmail.com \
--cc=emacs-orgmode@gnu.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://git.savannah.gnu.org/cgit/emacs/org-mode.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).