Re: gnorb: minor and mayor suggestions

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Uwe Brauer <oub@mat.ucm.es> writes:

>>>> "Eric" == Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>     > Uwe Brauer <oub@mat.ucm.es> writes:
>     >> Hi
>     >> which is fine for the reply mails, but I would like to have something
>     >> similar for *composing messages*. So the idea would be to start from the
>     >> bbdb and then add a similar entry to TODO-email.org.
>
>     > I think `gnorb-gnus-outgoing-do-todo' is what you're after here. If you
>     > compose a message from scratch, you can call that command from the
>     > message buffer, and a new Org entry will be captured after sending the
>     > message. I've got this:
>
>     > (eval-after-load "message"
>     >   '(progn
>     >      (define-key message-mode-map (kbd "C-c t") 'gnorb-gnus-outgoing-do-todo)))
>
>     > (setq gnorb-gnus-new-todo-capture-key "O")
>
> Here I am confused. I used in a compose-message-buffer
> gnorb-gnus-outgoing-do-todo
> but then what? I did not notice that anything (template) has been saved
> to an org file.
>
>
>     > Then the "O" template will be used to capture the sent message.
>
> And this template I have define?

You do have to define this template, but if it's not defined Gnorb
should complain to you: did you see any messages in the echo area?

>     > Alternately, call `gnorb-gnus-outgoing-do-todo' with a prefix argument,
>     > and it will trigger todo state change on an existing Org heading instead
>     > of creating a new one.
>
>     > (And if you change your mind afterwards, call the command with a double
>     > prefix to reset everything.)
>
> I tried this as well but it did not work.

Does it at least say "message associations reset" or something like that?

[...]

>    > Sounds like you want `gnorb-org-email-subtree'. That will prompt you for
>    > an export backend, and then it composes an email with the exported text
>    > either in the body of the mail, or else attached as a file. The outgoing
>    > message is tracked as usual.
>
>
> Ok I got that to work, yes you were right, that was the functionality I
> was looking for!

Good!

>
>    >> Whats about replying email? The above functions will copy all the text
>    >> below the org header into a message-buffer.
>    >> 
>    >> I modified it so that if I already hit the reply button but switch to
>    >> the org buffer, then the modified function copies the content below the
>    >> org header in that reply buffer.
>    >> 
>    >> Could gnorb provide a similar functionality?
>
>    > I'm not 100% sure I know what you mean here. Are you starting the
>    > process from the Gnus *Summary* buffer? You want to start a reply to
>    > message, but then hop to the associated Org heading, have the text
>    > pasted into the body of the heading, then when you're done writing, jump
>    > back to the message reply buffer and insert the text of the message?
>
> Precisely! This would be a functionality I would very much appreciate!

Let me have a little think about how this would work. I can imagine it
getting very messy very easily, but there's definitely something pretty
useful in there...