emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Joseph Vidal-Rosset <joseph.vidal.rosset@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: Thorsten Jolitz <tjolitz@gmail.com>,
	Alan Schmitt <alan.schmitt@polytechnique.org>,
	"Liste-emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
	John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: emails written in Org Mode
Date: Wed, 16 Jul 2014 19:02:14 +0200	[thread overview]
Message-ID: <CAD-VTcE3PZBBB-MWqP+0snOCSObokJvgr64sTxd1XxvJGJNsBQ@mail.gmail.com> (raw)
In-Reply-To: <87k37em2d1.fsf@ericabrahamsen.net>

[-- Attachment #1: Type: text/plain, Size: 3275 bytes --]

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>:

> Joseph Vidal-Rosset <joseph.vidal.rosset@gmail.com> 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 <tjolitz@gmail.com> 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
>

[-- Attachment #2: Type: text/html, Size: 4381 bytes --]

  reply	other threads:[~2014-07-16 17:02 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08 18:28 emails written in Org Mode Ken Mankoff
2014-07-09  5:06 ` Joseph Vidal-Rosset
     [not found]   ` <CAAjq1me3p_QPNf_UyXsbO2A4B7t_vVAAi-nL-k5wNsq0AU2J7w@mail.gmail.com>
2014-07-11  6:48     ` Joseph Vidal-Rosset
2014-07-09  7:49 ` Thorsten Jolitz
2014-07-10 12:57   ` Alan Schmitt
2014-07-10 13:27     ` Thorsten Jolitz
2014-07-11  9:32       ` Alan Schmitt
2014-07-09 19:14 ` John Kitchin
2014-07-09 20:03   ` Nick Dokos
2014-07-09 20:14     ` Ken Mankoff
2014-07-10  8:28       ` Thorsten Jolitz
2014-07-10 10:41         ` Ken Mankoff
2014-07-10 11:29           ` Thorsten Jolitz
2014-07-09 22:33   ` Eric Abrahamsen
2014-07-10  0:33   ` Thorsten Jolitz
2014-07-10 21:15   ` Esben Stien
2014-07-14  1:05   ` Esben Stien
2014-07-14 13:34     ` Esben Stien
2014-07-14 22:49       ` John Kitchin
2014-07-15  0:41         ` Eric Abrahamsen
2014-07-15  0:57           ` Thorsten Jolitz
2014-07-15  1:52             ` Eric Abrahamsen
2014-07-15 14:11             ` Alan Schmitt
2014-07-15 14:16               ` Joseph Vidal-Rosset
2014-07-16  3:03                 ` Eric Abrahamsen
2014-07-16 17:02                   ` Joseph Vidal-Rosset [this message]
2014-07-16  3:08                 ` Eric Abrahamsen
2014-07-09 20:02 ` Noorul Islam K M
2014-07-10  0:44 ` Thorsten Jolitz

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=CAD-VTcE3PZBBB-MWqP+0snOCSObokJvgr64sTxd1XxvJGJNsBQ@mail.gmail.com \
    --to=joseph.vidal.rosset@gmail.com \
    --cc=alan.schmitt@polytechnique.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=eric@ericabrahamsen.net \
    --cc=jkitchin@andrew.cmu.edu \
    --cc=tjolitz@gmail.com \
    /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).