From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Cc: ding@gnus.org, bbdb-info@lists.sourceforge.net
Subject: [ANN] Gnorb: Glue code between Gnus, Org, and BBDB
Date: Tue, 06 May 2014 17:21:45 +0800 [thread overview]
Message-ID: <87oazbclee.fsf@ericabrahamsen.net> (raw)
Hello all,
I've spent the past couple weeks organizing various bits of code into a
proper package, called Gnorb, which I'm billing as "Glue code between
Gnus, Org, and BBDB". The main point is to reduce friction between these
three packages, making it easier to sling around emails, TODOs,
attachments, and the like, and providing multiple views on information.
https://github.com/girzel/gnorb
Most of these bits fall under the category of "things you could have
written yourself", but taken together I've found that they really smooth
out my daily work flow. Some features:
- Whang attachments from Gnus messages onto Org headings, using org-attach.
- Automate the above as part of the org capture process
- Email contents of org subtree under point (prompt for export routine)
- Single-keystroke Org links or email citations of BBDB contacts
- Initiate search of emails from contacts in open BBDB buffer
- Initiate Org agenda tag search from BBDB buffer
- Inverse of the above: pop up a BBDB buffer alongside an Org tags search
- Treat headings as email-related TODOs, and handle them DWIM-style
See the README.org for more. Most of these are single-use small
snippets, but the last I've found particularly useful. A typical flow
would go like this: you have a capture template that looks like:
("r" "Reply" entry (file+headline "~/org/notes.org" "Emails")
"** REPLY %a %?" :gnus-attachments t)
Use this template to capture from an email in the Gnus summary buffer.
You're prompted to attach the message attachments to the new heading,
and while you're there you decide to add BBDB links to people who should
also be in on the reply. You end up with this:
** REPLY [[gnus:link]] and also send to [[bbdb:bob]] and [[bbdb:jane]] :ATTACH:
:PROPERTIES: (attachments and all that)
Then call `gnorb-org-handle-mail' on this headline in an Org or Agenda
buffer. A reply is started to the Gnus message, Bob and Jane are added
to the To header, and you're prompted to attach the attachments to the
outgoing message (presumably you've edited them). When the message is
sent you're returned to the original Org buffer and prompted to mark the
TODO as done. Next email!
The current version of this thing is "Works on My Computer (Beta)". I
would love bug reports, but would love feature requests even more! I'm
currently working on getting BBDB to store links to the last N messages
from any given contact. Also, how best to model email conversations
using TODO state-changes, log entries, and links.
I'm sure there's plenty more fun to be had, though.
Eric
next reply other threads:[~2014-05-06 19:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 9:21 Eric Abrahamsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-07 1:23 [ANN] Gnorb: Glue code between Gnus, Org, and BBDB Eric Abrahamsen
2014-05-07 2:45 ` Thomas S. Dye
2014-05-07 3:14 ` Eric Abrahamsen
2014-05-09 11:15 ` Alan Schmitt
2014-05-10 10:32 ` Eric Abrahamsen
2014-05-10 13:34 ` Alan Schmitt
2014-05-10 16:36 ` Eric Abrahamsen
2014-05-10 18:01 ` Alan Schmitt
2014-05-26 9:09 ` Eric Abrahamsen
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=87oazbclee.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=bbdb-info@lists.sourceforge.net \
--cc=ding@gnus.org \
--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).