From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joseph Vidal-Rosset Subject: Re: emails written in Org Mode Date: Wed, 16 Jul 2014 19:02:14 +0200 Message-ID: References: <87r41uwdiy.fsf@andrew.cmu.edu> <87pph8n40m.fsf@quasar.esben-stien.name> <87mwcckqru.fsf@quasar.esben-stien.name> <87mwcb36aj.fsf@andrew.cmu.edu> <874myjqwqn.fsf@ericabrahamsen.net> <87r41nh20m.fsf@gmail.com> <87k37em2d1.fsf@ericabrahamsen.net> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=bcaec547cbcb99763e04fe527d13 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34924) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X7SbF-0006Zr-9N for emacs-orgmode@gnu.org; Wed, 16 Jul 2014 13:02:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1X7SbD-00045h-Lg for emacs-orgmode@gnu.org; Wed, 16 Jul 2014 13:02:37 -0400 Received: from mail-vc0-x22c.google.com ([2607:f8b0:400c:c03::22c]:40623) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X7SbD-00045Y-G4 for emacs-orgmode@gnu.org; Wed, 16 Jul 2014 13:02:35 -0400 Received: by mail-vc0-f172.google.com with SMTP id im17so2250645vcb.17 for ; Wed, 16 Jul 2014 10:02:34 -0700 (PDT) In-Reply-To: <87k37em2d1.fsf@ericabrahamsen.net> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Eric Abrahamsen Cc: Thorsten Jolitz , Alan Schmitt , "Liste-emacs-orgmode@gnu.org" , John Kitchin --bcaec547cbcb99763e04fe527d13 Content-Type: text/plain; charset=UTF-8 Many thanks for this effort, Eric. I will try to test Gnorb as soon as possible. Best wishes Jo. 2014-07-16 5:03 GMT+02:00 Eric Abrahamsen : > Joseph Vidal-Rosset writes: > > > Hello, > > > > This is very interesting indeed. But is there somewhere a good > > tutorial to read or video to see ? It would be helpful for people who > > want to use Gnus + Org-mode in optimal way. > > Someone asked me about a screencast recently, around the same time that > I realized the README isn't actually very readable! Part of getting the > package Elpa-ready will also be writing a proper Info manual. > > For the time being, the very basics of email tracking (though Gnorb does > a lot more) would look like this: > > 1. Start by making a TODO which represents a message that you have to > send. That could be using plain old capture on an incoming message > you want to reply to. Or using gnorb-gnus-outgoing-do-todo on a > message while you're composing it. Or just typing out a TODO. One way > or the other, you want a TODO heading that contains a mailto link, or > a bbdb link, or a gnus message link (or some combination thereof). > > 2. Call gnorb-org-handle-mail on that heading. You'll end up composing a > message of some sort. > > 3. Send the message. You'll be taken back to the original TODO heading, > and prompted to take a note or change the TODO state. For example, > from EMAIL to WAIT. It's useful to enable state-change logging. > > 4. Wait for a reply. When you get it, Gnorb will know (I hope) that the > reply is relevant to the original TODO, and will prompt you to call > gnorb-gnus-incoming-do-todo on the message. Do that. > > 5. Again you'll be taken back to the TODO, and prompted to take a note > or change the TODO state -- for example, from WAIT to REPLY. A link > to the received message can (and should) be inserted into the > state-change drawer. > > 6. Go back to step two, and repeat until your email conversation is > done. > > What it boils down to is calling gnorb-org-handle-mail on your TODO > heading, and gnorb-gnus-incoming-do-todo on received messages. > Everything else is gravy. (But there's a lot of gravy!) > > The moment something doesn't work the way you like it, look at the > customization options. > > Maybe what I need here is a diagram... > > Eric > > > 2014-07-15 16:11 GMT+02:00 Alan Schmitt < > > alan.schmitt@polytechnique.org>: > > > > On 2014-07-15 02:57, Thorsten Jolitz writes: > > > > > Hadn't have the time to try Gnorb, but the combination of gnus& > > org is > > > definitely interesting for me. > > > > I highly recommend this library. I haven't scratched the surface, > > but > > one great "aha" moment was when I was reading in email in gnus > > and saw > > a message in the minibuffer about a relevant task from my todo > > list. > > > > I mostly use it to track "waiting for" sent email: after sending > > an > > email, with one keystroke I can create a waiting for task with a > > link to > > the sent email. I also use it to create "reply to" tasks. > > > > Alan > > > > -- > > OpenPGP Key ID : 040D0A3B4ED2E5C7 > --bcaec547cbcb99763e04fe527d13 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Many thanks for this effort, Eric. I will try to test= Gnorb as soon as possible.

Best wishes

Jo.
=


2014-07-16 5:= 03 GMT+02:00 Eric Abrahamsen <eric@ericabrahamsen.net>= :
Someone asked me about a screencast recently, around the same time th= at
I realized the README isn't actually very readable! Part of getting the=
package Elpa-ready will also be writing a proper Info manual.

For the time being, the very basics of email tracking (though Gnorb does a lot more) would look like this:

1. Start by making a TODO which represents a message that you have to
=C2=A0 =C2=A0send. That could be using plain old capture on an incoming mes= sage
=C2=A0 =C2=A0you want to reply to. Or using gnorb-gnus-outgoing-do-todo on = a
=C2=A0 =C2=A0message while you're composing it. Or just typing out a TO= DO. One way
=C2=A0 =C2=A0or the other, you want a TODO heading that contains a mailto l= ink, or
=C2=A0 =C2=A0a bbdb link, or a gnus message link (or some combination there= of).

2. Call gnorb-org-handle-mail on that heading. You'll end up composing = a
=C2=A0 =C2=A0message of some sort.

3. Send the message. You'll be taken back to the original TODO heading,=
=C2=A0 =C2=A0and prompted to take a note or change the TODO state. For exam= ple,
=C2=A0 =C2=A0from EMAIL to WAIT. It's useful to enable state-change log= ging.

4. Wait for a reply. When you get it, Gnorb will know (I hope) that the
=C2=A0 =C2=A0reply is relevant to the original TODO, and will prompt you to= call
=C2=A0 =C2=A0gnorb-gnus-incoming-do-todo on the message. Do that.

5. Again you'll be taken back to the TODO, and prompted to take a note<= br> =C2=A0 =C2=A0or change the TODO state -- for example, from WAIT to REPLY. A= link
=C2=A0 =C2=A0to the received message can (and should) be inserted into the<= br> =C2=A0 =C2=A0state-change drawer.

6. Go back to step two, and repeat until your email conversation is
=C2=A0 =C2=A0done.

What it boils down to is calling gnorb-org-handle-mail on your TODO
heading, and gnorb-gnus-incoming-do-todo on received messages.
Everything else is gravy. (But there's a lot of gravy!)

The moment something doesn't work the way you like it, look at the
customization options.

Maybe what I need here is a diagram...

Eric

> 2014-07-15 16:11 GMT+02:00 Alan Schmitt <
>
alan.schmitt@polytec= hnique.org>:
>
> =C2=A0 =C2=A0 On 2014-07-15 02:57, Thorsten Jolitz <tjolitz@gmail.com> writes:
>
> =C2=A0 =C2=A0 > Hadn't have the time to try Gnorb, but the comb= ination of gnus&
> =C2=A0 =C2=A0 org is
> =C2=A0 =C2=A0 > definitely interesting for me.
>
> =C2=A0 =C2=A0 I highly recommend this library. I haven't scratched= the surface,
> =C2=A0 =C2=A0 but
> =C2=A0 =C2=A0 one great "aha" moment was when I was reading = in email in gnus
> =C2=A0 =C2=A0 and saw
> =C2=A0 =C2=A0 a message in the minibuffer about a relevant task from m= y todo
> =C2=A0 =C2=A0 list.
>
> =C2=A0 =C2=A0 I mostly use it to track "waiting for" sent em= ail: after sending
> =C2=A0 =C2=A0 an
> =C2=A0 =C2=A0 email, with one keystroke I can create a waiting for tas= k with a
> =C2=A0 =C2=A0 link to
> =C2=A0 =C2=A0 the sent email. I also use it to create "reply to&q= uot; tasks.
>
> =C2=A0 =C2=A0 Alan
>
> =C2=A0 =C2=A0 --
> =C2=A0 =C2=A0 OpenPGP Key ID : 040D0A3B4ED2E5C7

--bcaec547cbcb99763e04fe527d13--