Eric Abrahamsen <e...@ericabrahamsen.net> writes: > I'm writing two more functions to complement `gnorb-org-handle-mail'. In > the end there will be three: > > 1. A function that says "make an Org todo out of the email I'm sending > now" (to keep track of conversations that need following-up). > > 2. A function that says "this email I just received is relevant to some > Org heading, and should trigger a TODO state-change or a note on that > heading". It will be able to suggest the correct heading. > > 3. A function that says "send an email by reading the current Org > heading and doing what I what". That's `gnorb-org-handle-mail'. > > Everything else just depends on how you've set up your capture > templates, and how you like to structure your mail-related TODOs. I > don't want to enforce anything else, but I want those three functions to > be good at guessing how you do things, and I'll provide user options to > help them guess correctly. In particular, how `gnorb-org-handle-mail' > interprets the heading under point is important.
Okay, the above is basically up and working, modulo bugs. In an OCD fit I had to rename a couple of functions, I'm going to coder hell, I know it. gnorb-gnus-outgoing-make-todo is now gnorb-gnus-outgoing-do-todo, and gnorb-gnus-message-trigger-todo is now gnorb-gnus-incoming-do-todo. The readme at https://github.com/girzel/gnorb has a general description of how one might use this for email tracking. E
