Re: gnorb: minor and mayor suggestions

[Eric Abrahamsen <eric@ericabrahamsen.net>]

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

> Hi
>
> First of all thanks to Eric for providing that package.[1] I thought of
> sending him a private mail with some questions/suggestions but may be this
> newsgroup is the better place.

Here's a fine place! I think that everything you're asking for is
already implemented, but let's make sure.

> Now I have 1 minor and two mayor suggestions (maybe they are already
> implemented and I failed to find them).
>
> * minor: right now my org template looks like
> ("r" "Reply" entry (file+headline "~/Mail/TODO-email.org" "Emails")
> 	 "** REPLY %a %?" :gnus-attachments t)
>
> 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")

Then the "O" template will be used to capture the sent message.

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.)

It's all a bit confusing to explain, but once you've tried it, it should
make sense.

> * mayor: editing emails in an org buffer and later send them.
>
>   For some emails it turns out to be better to edit them in an
>   org mode buffer, for example if I would like to edit a table and
>   orgtbl-mode in message would not be enough. Right now I start editing
>   those message in an org-file and then use the following function 

[...]

> Could gnorb provide a similar functionality?

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.

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

Anyway let me know exactly what workflow you have in mind, and I'd be
happy to try to accommodate in gnorb.

Yours,
Eric