From: Rainer M Krug <R.M.Krug@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Naive email "referencing" using copy&paste
Date: Tue, 19 Feb 2013 08:59:13 +0100 [thread overview]
Message-ID: <512330D1.40703@gmail.com> (raw)
In-Reply-To: <2013-02-18T22-55-01@devnull.Karl-Voit.at>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 18/02/13 23:02, Karl Voit wrote:
> * Rainer M Krug <r.m.krug@gmail.com> wrote:
>>
>> Hi
>
> Hi!
>
>> I actually would prefer the source block approach, as the email would be physically in the
>> org document and foldable.
>>
>> Any suggestions how I could achieve this?
>
> In my case, MUA (mutt) and Org are on different hosts. I am accessing MUA through ssh/screen
> and copy relevant parts into blocks like this:
>
> #+BEGIN_VERSE Date: Mon, 18 Feb 2013 15:58:22 +0000 From: Kickstarter
> <no-reply@kickstarter.com> To: xxxxxxxxxxxxx From: Project Boss <boss@example.com> Subject:
> Project Update xxxxxxxxxxxxxxxxxx Message-ID: <513_6f6d48753ee22646e9@xxxxxxxxxxxxxxxxxx>
>
> Project deadline is re-schedults to May 2014 since external ressources are not available before
> autumn. #+END_VERSE
>
> Sometimes, I am using BEGIN_QUOTE instead of BEGIN_VERSE though.
>
> With copy&paste, it's not as quick as capture but this way I get the advantage to strip down
> the message to its relevant parts. With the Message-ID, I am able to locate the original email
> in my MUA very quickly.
Yes - I did something similar, but didn't think about the verse and quote blocks - thanks.
But I was looking for something more dynamic, i.e. when further comments come in the conversation,
I would like to have them accessible as well.
So a notmuch search based system (through links or through source blocks) is the ideal situation
in my case.
Thanks,
Rainer
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJRIzDRAAoJENvXNx4PUvmCS5oH/29cLZq6yULqxbsIYoYyz4n7
6Vi7g4XBuh6qLBtygvhhMv7V515MtaqYSDWDQZoFMKK5LQGZnjvhSB60bBGwDIGu
/I2t9CV7ZO2qF1KpR98FTBI+Ch1MbOzjHtV5OSihZAZJnAfyOYpBAYWzppmlvxi8
fSvGX23ob0Q0F6H7pe+b46W4o+EGA9birR0iU3kXPzqKGN2o4rmOlHc2ro9JPve6
dNt1XGisjGX/XojKoMRm7YJgMRcADkftH7Eli1ZUfqQSuWJL2DBy7u9r89YKoU/A
5nCBmF6C5jSLK3sNyNu3CcjHbxq33ttBV8tFXvcZlptp1cgN3wNdA/KhWwbhBgc=
=VWE1
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2013-02-19 7:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 13:49 Integration of notmuch email references in notes in org-mode Rainer M Krug
2013-02-18 15:12 ` Suvayu Ali
2013-02-18 15:33 ` Rainer M Krug
2013-02-18 21:41 ` Including linked emails during export (was Re: Integration of notmuch email references in notes in org-mode) Suvayu Ali
2013-02-19 8:12 ` Rainer M Krug
2013-02-27 13:35 ` Nicolas Goaziou
2013-02-27 13:47 ` Suvayu Ali
2013-02-18 22:02 ` Naive email "referencing" using copy&paste (was: " Karl Voit
2013-02-19 7:59 ` Rainer M Krug [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
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=512330D1.40703@gmail.com \
--to=r.m.krug@gmail.com \
--cc=emacs-orgmode@gnu.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.
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).