From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: gnorb: minor and mayor suggestions
Date: Sat, 26 Mar 2016 16:23:16 +0000 [thread overview]
Message-ID: <878u152op7.fsf@mat.ucm.es> (raw)
In-Reply-To: <87egaxlu16.fsf@ericabrahamsen.net>
>>> "Eric" == Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Uwe Brauer <oub@mat.ucm.es> writes:
> Here's a fine place! I think that everything you're asking for is
> already implemented, but let's make sure.
> 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!
>> 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!
> Anyway let me know exactly what workflow you have in mind, and I'd be
> happy to try to accommodate in gnorb.
Uwe
prev parent reply other threads:[~2016-03-26 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 17:58 Uwe Brauer
2016-03-26 4:53 ` Eric Abrahamsen
2016-03-26 8:57 ` Uwe Brauer
2016-03-27 2:37 ` Eric Abrahamsen
2016-03-26 16:23 ` Uwe Brauer [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878u152op7.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=ding@gnus.org \
/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.
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 NNTP newsgroup(s).